ci: pin flawd v0.15.0 so coverage_source takes effect - #73
Merged
Conversation
…posture takes effect v0.14.0 silently ignored the [docker] coverage_source = "image" key this repo's flawd.toml sets (the key shipped in v0.15.0), so container coverage on the scheduled Docker audits was still bind-mount sourced — the wrong-architecture-binaries hazard the key exists to close. v0.15.0 honors it; release notes: https://github.com/fixture-dev/flawd-releases/releases/tag/v0.15.0
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps the mutation workflow's flawd pin from v0.14.0 to v0.15.0.
The repo's flawd.toml sets
[docker] coverage_source = "image"(the Dockerfile embeds the source; bind-mount coverage delivers wrong-architecture host binaries to subprocess tests), but that key shipped in flawd v0.15.0 — v0.14.0 accepted and silently ignored it, so the scheduled Docker audits were still running with the hazard the key exists to close.v0.15.0 changelog highlights relevant here:
coverage_sourcesupport, test-diff scoping for CI runs, and the risk_level fix. Full notes: https://github.com/fixture-dev/flawd-releases/releases/tag/v0.15.0