UID2-7011: gate zizmor scan on High-severity findings#252
Closed
swibi-ttd wants to merge 1 commit into
Closed
Conversation
Flip the dogfood caller from report-only (fail_severity: never) to blocking on High (fail_severity: high). The repo reached zero High-severity findings in PRs #249-#251 (95 template-injection findings fixed) and the fixed release path was verified end-to-end via a Snapshot canary on uid2-attestation-api, so a red check from here on means a genuine new High finding - a regression gate, per the UID2-7011 rollout plan. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Contributor
Author
|
Closing — superseded by #253: gating flips will go through the shared workflow's central default or per-repo ZIZMOR_FAIL_SEVERITY Actions variables rather than caller edits, and the flip itself is on hold until the org-wide rollout's High findings are fixed (see UID2-7011). |
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.
Flips the dogfood zizmor caller from report-only to blocking on High (
fail_severity: high), per the rollout plan on UID2-7011.Preconditions all met:
zizmor --min-severity highon main exits 0 (was 95 findings)This PR is also its own proof: the zizmor check on it now runs with the gate on and only stays green if the repo is clean at High. A red zizmor check from here on means a genuine new High-severity finding.
🤖 Generated with Claude Code