housekeeping, ci: bump GitHub Actions to Node 24 runtimes#616
Merged
Conversation
Move Node-based actions off the deprecated Node 20 runtime (GitHub is force-mapping them to Node 24) by bumping each to the lowest major version that ships a Node 24 runtime: - actions/checkout v3 -> v5 - actions/setup-go v3 -> v6 - dorny/test-reporter v1 -> v3 - actions/upload-artifact v4 -> v6 - actions/download-artifact v4 -> v7 - EndBug/add-and-commit v9 -> v10 - nuget/setup-nuget v1 -> v3 - microsoft/setup-msbuild v1.1 -> v3 - OctopusDeploy/create-release-action v3 -> v4 - OctopusDeploy/create-zip-package-action v3 -> v4 - OctopusDeploy/push-package-action v3 -> v4 Left unchanged (no Node 24 release exists upstream yet; still node16/20 and force-mapped by GitHub at runtime): - goreleaser/goreleaser-action (latest v6 = node20) - crazy-max/ghaction-import-gpg (latest v6 = node20) - google-github-actions/release-please-action (latest v4 = node20) Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
setup-go@v6 sets GOTOOLCHAIN=local, which stops Go from auto-downloading a newer toolchain. The workflows pinned go-version: 1.21 while go.mod requires go 1.25.5, so `go build` failed with: go: go.mod requires go >= 1.25.5 (running go 1.21.13; GOTOOLCHAIN=local) Under setup-go@v3 (GOTOOLCHAIN=auto) the mismatch was masked by an automatic toolchain download. Point setup-go at go-version-file (go.mod, or cli/go.mod in generate-docs where the CLI is checked out to cli/) so the installed toolchain always matches the module requirement. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
APErebus
approved these changes
Jul 16, 2026
| uses: actions/setup-go@v6 | ||
| with: | ||
| go-version: 1.21 | ||
| go-version-file: cli/go.mod |
Contributor
There was a problem hiding this comment.
What's this change doing?
Contributor
Author
There was a problem hiding this comment.
avoids drift and maintaining version number in more places, it's the 2nd line in the go.mod file, and this mechanism gets it from there.
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
2 participants
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.
Move Node-based actions off the deprecated Node 20 runtime (GitHub is force-mapping them to Node 24) by bumping each to the lowest major version that ships a Node 24 runtime: