Repository navigation
Correct Docker login action version annotations - #197
Closed
ai-collaboration-app[bot] wants to merge 1 commit into
Closed
ai-collaboration-app[bot] wants to merge 1 commit into
ai-collaboration-app[bot] wants to merge 1 commit into
Conversation
The v4 tag advanced to v4.7.0 while our SHA still resolves to v4.6.0. Online Zizmor therefore stops CI before tests and publication. Record the exact pinned release without changing executable workflow content or loosening the audit.
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 pinned Docker login action is v4.6.0, but its comments say v4. After that tag advanced, online Zizmor stopped CI and skipped tests/publication. Correct the three annotations; workflow behavior and action SHAs stay identical.
Validation: online Zizmor 1.31.1 passes; parsed YAML before/after is identical. PR CI passes all five validation jobs. Stopped v3.9.4 run. The existing signed release tag remains unchanged. Retrying its original workflow still reads the old annotations; publication recovery must use the corrected workflow while building the existing tag.
Tracking: https://github.com/StackVista/cve-reporter/issues/101