Skip to content

fix(ci): revert invalid goreleaser version pin#95

Merged
Patel230 merged 1 commit into
mainfrom
fix/goreleaser-version-pin
Jul 13, 2026
Merged

fix(ci): revert invalid goreleaser version pin#95
Patel230 merged 1 commit into
mainfrom
fix/goreleaser-version-pin

Conversation

@Patel230

Copy link
Copy Markdown
Contributor

Summary

  • .github/workflows/release.yml's goreleaser-action was pinned to version: "v6.3.0", which doesn't exist upstream (goreleaser tops out at v2.18.0)
  • Silent until now because no tag had been pushed since the pin was introduced — the v0.2.0 tag push was the first trigger, and the goreleaser job 404'd fetching the binary
  • Reverts to "~> v2", the constraint used before that change

Test plan

  • v0.2.0 release 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
  • Hosted CI green on this PR
  • Next tag push exercises the fixed pin end-to-end

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.
@Patel230 Patel230 merged commit 4880f39 into main Jul 13, 2026
19 checks passed
@Patel230 Patel230 deleted the fix/goreleaser-version-pin branch July 13, 2026 11:31
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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant