ci(release): bump release workflow Go to 1.26.4#59
Merged
Conversation
go.mod requires go >= 1.26.4; the release workflow ran setup-go 1.26.3 with GOTOOLCHAIN=local, so 'Verify module' + the binary builds failed on v1.4.6. The module itself publishes via the tag (proxy has v1.4.6); this fixes the workflow so future releases verify + attach binaries. Completes the toolchain unification (ci.yml was already on 1.26.4).
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.
The release workflow pinned Go 1.26.3 while go.mod now requires 1.26.4 (
GOTOOLCHAIN=local), so v1.4.6'sVerify module+ binary-build jobs failed. The module published fine via the tag (proxy has v1.4.6, and probatorium cross-builds loadgen from source anyway), so nothing downstream is affected — this just makes future release runs green and finishes the Go-1.26.4 unification.