ci: bump actions/checkout v4→v6 and setup-go v5→v6 (Node 24)#41
Merged
Conversation
GitHub Actions forces Node.js 20 actions to Node 24 on 2026-06-16. Both actions we use have v6 majors that run on Node 24 natively: - actions/checkout v6.0.0 (2025-08-26, v6.0.3 latest 2026-06-02): Node.js 24 support per the v6 release notes. - actions/setup-go v6.0.0 (2025-09-22, v6.4.0 latest 2026-03-30): Explicit "Upgrade Nodejs runtime from node20 to node 24" breaking change. Also requires runner v2.327.1+; GitHub-hosted ubuntu-latest is well past that. Our usage is the simple path (go-version-file: go.mod on setup-go, default checkout otherwise) so neither v6's other breaking changes apply here. Bumping ahead of the 2026-06-16 cutover so the release workflow keeps working through the transition without depending on the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24 or ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION escape hatches. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
jrennichjc
approved these changes
Jun 5, 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
3 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.
Summary
GitHub Actions forces Node.js 20 actions to Node 24 on 2026-06-16. The deprecation warning has been firing on every release run since 1.16.0. Both actions we use have v6 majors that run on Node 24 natively:
actions/checkout@v4@v6(latestv6.0.3, 2026-06-02)actions/setup-go@v5@v6(latestv6.4.0, 2026-03-30)Other v6 changes to be aware of
setup-go@v6also has a breaking-change toolchain-handling rework (Improve toolchain handling actions/setup-go#460). Our usage (go-version-file: go.mod) is the simple path and isn't affected.setup-go@v6requires runner v2.327.1+; GitHub-hostedubuntu-latestis well past that.Why now
Bumping ahead of the 2026-06-16 cutover so the release workflow keeps working through the transition without depending on the
FORCE_JAVASCRIPT_ACTIONS_TO_NODE24orACTIONS_ALLOW_USE_UNSECURE_NODE_VERSIONescape hatches.Test plan
.github/workflows/release.ymlpr-labels.ymldoesn't checkout)1.17.3cleanly🤖 Generated with Claude Code
Note
Low Risk
Two-line CI dependency bumps with unchanged inputs; no application or auth logic touched.
Overview
Updates the Release job in
.github/workflows/release.ymlso checkout and Go setup use Node 24–compatible action majors ahead of GitHub’s Node 20 deprecation.actions/checkoutmoves from @v4 to @v6, andactions/setup-gofrom @v5 to @v6. Step inputs are unchanged (merge_commit_sha,fetch-depth: 0, andgo-version-file: go.mod). This is the only workflow in the repo that references these actions.Reviewed by Cursor Bugbot for commit 33cfc80. Bugbot is set up for automated code reviews on this repo. Configure here.