Skip to content

chore: disable fail-build on Anchore container scan#4285

Merged
lawrence-u10d merged 1 commit intomainfrom
ci/disable-anchore-fail-build
Mar 16, 2026
Merged

chore: disable fail-build on Anchore container scan#4285
lawrence-u10d merged 1 commit intomainfrom
ci/disable-anchore-fail-build

Conversation

@lawrence-u10d
Copy link
Copy Markdown
Contributor

@lawrence-u10d lawrence-u10d commented Mar 16, 2026

Summary

  • Sets fail-build: false on the Anchore scan-action@v3 step in the CI workflow
  • Critical vulnerability findings will still be reported in the scan output, but will no longer block the pipeline

Test plan

  • Verify CI pipeline runs and the Anchore scan step completes without failing the build
  • Confirm scan results are still visible in the workflow logs

🤖 Generated with Claude Code


Note

Low Risk
Low risk workflow-only change; CI will no longer block merges on critical vulnerability findings, which reduces enforcement rather than altering runtime behavior.

Overview
Updates the CI test_dockerfile job to set fail-build: false for the anchore/scan-action@v3 container scan.

Critical (fixed) vulnerabilities will still be reported in the scan output, but they will no longer fail the pipeline.

Written by Cursor Bugbot for commit b01f263. This will update automatically on new commits. Configure here.

Set `fail-build: false` on the Anchore scan-action step so critical
vulnerability findings are reported but no longer block the CI pipeline.

Co-Authored-By: Claude Opus 4.6 <[email protected]>
@lawrence-u10d lawrence-u10d merged commit 5585e98 into main Mar 16, 2026
23 of 26 checks passed
@lawrence-u10d lawrence-u10d deleted the ci/disable-anchore-fail-build branch March 16, 2026 15:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants