ci: bump actions/setup-go from v5 to v6#256
Merged
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.
actions/setup-go@v5runs on Node 20, which CI already warns about (Node.js 20 is deprecated ... being forced to run on Node.js 24). The other actions were bumped by Dependabot; setup-go was the last one left behind.The notable breaking change in v6 is that it sets
GOTOOLCHAIN=local, so agocommand errors out instead of silently downloading a newer toolchain. That does not apply here: every workflow installs Go viago-version-file: go.mod,go.moddeclaresgo 1.26.5and has notoolchaindirective, so the installed version already satisfies the requirement. CI on this PR exercises it — every job (unit, lint, vet, fmt, govulncheck, e2e) sets Go up through this action.