CI: use actions that run on Node 24 - #158
Open
DTW-Thalion wants to merge 1 commit into
Open
Conversation
Every job warns that actions/checkout targets Node.js 20 and is being forced onto Node.js 24. checkout v5 and upload-artifact v6 are the releases that moved to node24. Both need runner 2.327.1 or newer, and the hosted runners are 2.336.0.
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.
Every job ends with a warning that actions/checkout targets Node.js 20 and is being forced onto Node.js 24. The runner no longer gives checkout the runtime it declares, and the compatibility shim is being withdrawn.
checkout v3 declares node16 and v4 declares node20. v5 is the release that moved checkout to node24. upload-artifact v4 and v5 both declare node20, and v6 is the release that moved it, so the two actions land on different major versions. These are the smallest bumps that remove the warning. checkout v6 stores credentials in a separate file and v7 blocks checking out a fork under pull_request_target and workflow_run, neither of which belongs here.
Both releases need runner 2.327.1 or newer. The runners these workflows get are 2.336.0.
Verified on the fork: both Linux jobs and the macOS job build and test green, and no job logs the deprecation warning.