fix(ci): correct goreleaser-action version pin comment (v2.8.1 -> v6.2.1)#122
Merged
stevebeattie merged 1 commit intoJun 22, 2026
Conversation
…2.1) The goreleaser/goreleaser-action step in release.yaml is pinned to 90a3faa9d0182683851fbfa97ca1a2cb983bfca3, which resolves to v6.2.1 (verified against the upstream tags) — but the comment claimed `# v2.8.1`, understating the action by four major versions. Correct the comment to match the pinned commit. SHA unchanged; behavior unchanged (ref-version-mismatch / provenance accuracy only). Refs: PSEC-923 Co-Authored-By: Steve Beattie <steve.beattie@chainguard.dev>
egibs
approved these changes
Jun 22, 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
2 participants
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.
Correct goreleaser-action version pin comment
Refs: PSEC-923
Follow-up to the GitHub Actions hardening PR. The
goreleaser/goreleaser-actionstep in
release.yamlis pinned to commit90a3faa9d0182683851fbfa97ca1a2cb983bfca3, which resolves to v6.2.1(verified against the upstream tags), but the trailing comment claimed
# v2.8.1— understating the action by four major versions.This corrects the comment to
# v6.2.1. The pinned SHA is unchanged, so CIbehavior is unchanged; this is a provenance-accuracy fix so the comment no
longer misrepresents which version is actually running.