Repository navigation
Fix action version labels blocking CLI release - #196
Merged
Merged
Conversation
The floating v4 tag moved after main passed CI, making the v3.9.4 tag audit fail. Label the unchanged commit as v4.6.0 so online Zizmor audits use the exact release.
viliakov
approved these changes
Oct 27, 2026
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
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.
The v3.9.4 release stopped at Zizmor because Docker's floating
v4tag moved. Label the existing Docker login action SHA as its exactv4.6.0release in all three references; executable workflow content is unchanged.Validated with Zizmor 1.31.1 (no findings) and parsed YAML equality. After merge, release from the corrected commit using a fresh version; preserve the failed v3.9.4 tag.
Tracks https://github.com/StackVista/cve-reporter/issues/101.