fix(ci): repin goreleaser + trufflehog at the template source#96
Merged
Conversation
…st the render 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 was referenced Jul 13, 2026
Patel230
added a commit
to GrayCodeAI/eyrie
that referenced
this pull request
Jul 13, 2026
The shared workflow template pinned trufflesecurity/trufflehog to a commit SHA labeled "main 2026-05-18" — a floating branch reference disguised as a pin, not an actual release. Repins to v3.95.9, the current real trufflehog release. Companion fix to GrayCodeAI/hawk#96, which fixes the same issue at the template source.
Patel230
added a commit
to GrayCodeAI/hawk-mcpkit
that referenced
this pull request
Jul 13, 2026
The shared workflow template pinned trufflesecurity/trufflehog to a commit SHA labeled "main 2026-05-18" — a floating branch reference disguised as a pin, not an actual release. Repins to v3.95.9, the current real trufflehog release. Companion fix to GrayCodeAI/hawk#96, which fixes the same issue at the template source.
Patel230
added a commit
to GrayCodeAI/hawk-core-contracts
that referenced
this pull request
Jul 13, 2026
The shared workflow template pinned trufflesecurity/trufflehog to a commit SHA labeled "main 2026-05-18" — a floating branch reference disguised as a pin, not an actual release. Repins to v3.95.9, the current real trufflehog release. Companion fix to GrayCodeAI/hawk#96, which fixes the same issue at the template source.
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
1 participant
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
release.yml's broken goreleaser pin (v6.3.0, nonexistent upstream) but left.shared-templates/workflows/go-release.yml.tmpl— the actual source of truth — with the same bug. Any future re-sync from the template would have reintroduced it. Both are now pinned tov2.17.0(matchingtok's already-correct exact-pin pattern instead of a floating~> v2constraint).trufflesecurity/trufflehogin bothgo-ci.yml.tmpland hawk's own renderedci.yml, from a commit SHA labeled# main 2026-05-18(a floating branch reference disguised as a pin) to its realv3.95.9release tag.Test plan
grep -rn "v6.3.0\|main 2026-05-18" .shared-templates .github/workflowsreturns nothingsecretsjob directly exercises the new trufflehog pin)