chore: complete Node 24 migration for GitHub Actions#996
Merged
Conversation
Bump the remaining actions still on the deprecated Node 20 runtime: - actions/setup-go v5.5.0 -> v6.4.0 (shared setup composite) - actions/cache v4.2.3 -> v5.0.5 (shared setup composite) - golang/govulncheck-action v1.0.4 -> master HEAD setup-go only moved to Node 24 in v6.2.0, so v5.5.0 was still Node 20. The govulncheck-action latest release (v1.0.4) internally pins actions/checkout@v4.1.1 and actions/setup-go@v5.0.0 (Node 20); its master branch already uses Node 24 actions but has not been tagged, so it is pinned to master HEAD with a TODO to re-pin once a release past v1.0.4 is cut. A previous pass only bumped actions/checkout, leaving these behind.
wolo-lab
approved these changes
Jun 10, 2026
wolo-lab
approved these changes
Jun 10, 2026
newtonnthiga
pushed a commit
to alis-exchange/adk-go
that referenced
this pull request
Jun 11, 2026
Bump the remaining actions still on the deprecated Node 20 runtime: - actions/setup-go v5.5.0 -> v6.4.0 (shared setup composite) - actions/cache v4.2.3 -> v5.0.5 (shared setup composite) - golang/govulncheck-action v1.0.4 -> master HEAD setup-go only moved to Node 24 in v6.2.0, so v5.5.0 was still Node 20. The govulncheck-action latest release (v1.0.4) internally pins actions/checkout@v4.1.1 and actions/setup-go@v5.0.0 (Node 20); its master branch already uses Node 24 actions but has not been tagged, so it is pinned to master HEAD with a TODO to re-pin once a release past v1.0.4 is cut. A previous pass only bumped actions/checkout, leaving these behind.
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.
Summary
Finishes migrating CI off the deprecated Node 20 actions runtime. GitHub forces JavaScript actions to Node 24 starting June 16, 2026 and removes Node 20 from runners on Sept 16, 2026, so anything still declaring Node 20 currently emits a deprecation warning and will eventually break.
An earlier pass bumped
actions/checkoutto v6, but three references were left on Node 20 — two of them indirect, which is why they were easy to miss:actions/setup-go.github/actions/setupcompositeactions/cache.github/actions/setupcompositegolang/govulncheck-actionnightly.ymlvulncheck jobNotes
actions/setup-goonly switched to Node 24 in v6.2.0 (v5.x and even v6.0.0/v6.1.0 are still Node 20), so the composite action affected every job that uses it (test,lint,nightlytest).golang/govulncheck-action's latest tagged release (v1.0.4) internally pinsactions/checkout@v4.1.1andactions/setup-go@v5.0.0(Node 20). Its default branch already uses Node 24 actions but hasn't been tagged, so it's pinned to the master commit with an inlineTODOto re-pin to a proper tag once upstream cuts a release past v1.0.4.Verification
using: node24in itsaction.yml(and that govulncheck-action's master uses checkout v6.0.2 + setup-go v6.2.0 internally).