Skip to content

Fail 3.3.x image builds on CRITICAL findings only - #2622

Open
kmcginnes wants to merge 1 commit into
3.3.xfrom
critical-only-image-scan-3.3.x
Open

kmcginnes wants to merge 1 commit into
3.3.xfrom
critical-only-image-scan-3.3.x

Conversation

@kmcginnes

Copy link
Copy Markdown
Collaborator

Summary

A release branch only takes a patch release for a fixable CRITICAL finding, so pull requests into 3.3.x now fail the image test build on fixable CRITICAL findings only. Findings with no fix are skipped, as on main.

           image-ref: test-image
-          severity: HIGH,CRITICAL
+          severity: CRITICAL
+          ignore-unfixed: true
           exit-code: 1

The test build workflow on 3.3.x is also changed by #2615. The two edit different lines.

Evidence

Verified: the workflow is valid YAML, formatted, and passes actionlint.

Merge Danger

Door: two-way

Impact: CI-only. Pull requests into 3.3.x stop failing on HIGH findings, and on findings with no fix.

Related


🤖 Written by an AI agent on my behalf.

A release branch only takes a patch for a CRITICAL finding, and findings with no fix are skipped, matching main.
@kmcginnes
kmcginnes marked this pull request as ready for review November 16, 2026 23:56

This branch has not been deployed

No deployments
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.

1 participant