Repository navigation
Unblock publication by correcting the pinned scan action label - #348
Merged
Merged
Conversation
The ec325c7 scan implementation has no release tag. Its main comment became false when image-pipeline advanced and online Zizmor then blocked master publication. Remove only that comment, retaining the verified action SHA and all workflow behavior.
LouisLotter
approved these changes
Oct 21, 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 merged build 39584770110 cannot publish because online Zizmor rejects the scan action's stale
mainlabel after the upstream branch moved. Remove that label while retaining the exact verified action SHA; image-pipeline has no release tag for this commit. No workflow behavior or scanner policy changes.Tracking: https://github.com/StackVista/cve-reporter/issues/27
Validation: online Zizmor 1.31.1 passes, parsed workflow content is identical, and candidate CI's Zizmor job passed. Native build/test and subsequent image checks are still running. The unchanged scanner implementation and product are already covered by PR347 CI.
Human merge after required CI passes is the next action. Its normal master build must publish before updating
nodeAgent.containers.processAgent.image.tagin helm-charts-internal's agent chart, bumping its chart version with the existing helper and regenerating docs. Process-agent reaches this chart directly; no stackstate-agent release is needed. The updater deliberately retains the current tag until the latest master image exists. Rebase chart adoption on then-current master to preserve the concurrent image updates.