🤖 release: resolve Go from go.mod instead of a stale '1.25' pin#435
Merged
Conversation
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.
Closes #434.
🐛 Problem
The v0.5.0 tag push failed the Release workflow in 16s:
go.modrequires go 1.25.11 (bumped by #406), butrelease.yml's hand-pinnedgo-version: '1.25'resolved to 1.25.10, and setup-go v6'sGOTOOLCHAIN=localblocks the auto-download — so GoReleaser's firstbeforehook died before building anything.🔧 Change
.github/workflows/release.yml:go-version: '1.25'→go-version-file: go.mod, matching all threeci.ymljobs. The release runner now always installs exactly what go.mod requires, so future toolchain bumps can't drift.✅ Verification
setup-go+go-version-filepattern on every push (green on this PR).🤖 Generated with Claude Code