ci: update GitHub Actions to Node 24 before June 2 deadline#280
Closed
estebany-qd wants to merge 1 commit into
Closed
ci: update GitHub Actions to Node 24 before June 2 deadline#280estebany-qd wants to merge 1 commit into
estebany-qd wants to merge 1 commit into
Conversation
Contributor
Author
|
Closing: PR was based on master but this repo merges to dev. Will reopen targeting dev. |
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.
Summary
GitHub will force all JavaScript-based actions to run on Node 24 starting June 2, 2026.
Node 20 will be removed from runners entirely on September 16, 2026.
Actions pinned to older versions (v1-v4 for checkout, v2-v5 for setup-python, etc.) were
written for Node 12/16/20 and risk breaking when forced to Node 24.
This PR updates all
actions/*references to the latest Node 24-native versions.Changes
All target SHAs verified against their tags via the GitHub API.
All target versions confirmed running
node24in theiraction.yml.References