Repository navigation
ci: pin pnpm version in goreleaser workflow - #86
Merged
Merged
Conversation
Same failure as the vet workflow: pnpm/action-setup reads the repo-root package.json for a packageManager pin, but ours lives in web/package.json, so tag releases died at "Set up pnpm". Pin pnpm explicitly and move setup-go/setup-node to current releases. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
barnabasbusa
approved these changes
Jun 10, 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 v1.0.0 tag release died at "Set up pnpm" — same root cause as the vet workflow fixed in #85:
pnpm/action-setup@v4reads the repo-rootpackage.jsonfor apackageManagerpin, but ours lives inweb/package.json, so the action finds no pnpm version.10.30.1explicitly on a SHA-pinnedpnpm/action-setupv4.2.0 (matching the vet workflow / wagie style)setup-go→ v5.6.0 andsetup-node→ v4.4.0 (SHA-pinned)After merging: the v1.0.0 tag still points at the commit with the broken workflow (tag pushes run the workflow file at the tag's commit), so the tag needs to be re-pointed at the fixed master head —
git tag -f v1.0.0 && git push -f origin v1.0.0— or cut a fresh tag.🤖 Generated with Claude Code