Update workflow actions to Node 24 majors - #2631
Merged
Merged
Conversation
Bump each action in the CI workflow to its latest major, all of which target the Node 24 runtime, clearing the Node 20 deprecation warning GitHub emits for the older majors. Covers checkout, setup-python, setup-dotnet, upload-artifact, download-artifact, github-script, setup-msbuild, and setup-nuget.
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.
GitHub Actions runners have deprecated Node 20, and the workflow's pinned action majors still target it, so every run prints the Node 20 deprecation warning while the actions are force-run on Node 24. This bumps each action to its latest major, all of which target the Node 24 runtime, so the declared runtime matches what the runner already uses and the warning clears.
Version bumps
actions/checkoutv4 to v7actions/setup-pythonv5 to v6actions/setup-dotnetv4 to v5actions/upload-artifactv4 to v7actions/download-artifactv4 to v8actions/github-scriptv7 to v9microsoft/setup-msbuildv2 to v3NuGet/setup-nugetv2 to v4Notes
The artifact actions and
github-scriptcross several majors, so this run is the real check that nothing in their newer majors changes how the workflow uses them; the checkout and setup bumps are largely runtime updates.actions/upload-artifactandactions/download-artifactare moved together to keep the upload and download pair compatible. The change is otherwise advisory, since the runner already forces these actions onto Node 24 today, so nothing was failing beforehand.