fix(ci): revert invalid goreleaser version pin#95
Merged
Conversation
release.yml pinned goreleaser-action to version "v6.3.0", which does not exist upstream (goreleaser's actual releases top out at v2.18.0). This went undetected because no tag was pushed since the pin was introduced; the v0.2.0 tag push was the first trigger and failed the goreleaser job with a 404 fetching the binary. Reverts to the "~> v2" constraint used before that change.
3 tasks
Patel230
added a commit
that referenced
this pull request
Jul 13, 2026
…st the render (#96) PR #95 fixed hawk's rendered release.yml but left the actual source of truth, .shared-templates/workflows/go-release.yml.tmpl, still pinned to the nonexistent goreleaser "v6.3.0" — any future template re-sync would have silently reintroduced the bug. Repins both the template and hawk's own rendered copy to the real, current v2.17.0 (matching tok's already- correct exact-pin pattern instead of a floating "~> v2" constraint). Also repins trufflehog from a commit SHA labeled "main 2026-05-18" (a floating branch reference, not a release) to its actual v3.95.9 release tag, in both go-ci.yml.tmpl and hawk's own rendered ci.yml.
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.
Summary
.github/workflows/release.yml's goreleaser-action was pinned toversion: "v6.3.0", which doesn't exist upstream (goreleaser tops out at v2.18.0)v0.2.0tag push was the first trigger, and the goreleaser job 404'd fetching the binary"~> v2", the constraint used before that changeTest plan
v0.2.0release artifacts (5 archives, source tarball, 5 SBOMs, checksums.txt) were built locally with the correct goreleaser version and uploaded to the existing GitHub Release as a stopgap