Move the actions to their Node 24 releases - #8
Merged
Conversation
The runners now default to Node 24 and warn on every step that the Node 20 actions are deprecated. Bumps all four to the current majors, which declare runs.using: node24: actions/checkout v4 -> v7 actions/setup-dotnet v4 -> v6 actions/upload-artifact v4 -> v7 actions/download-artifact v4 -> v8 Four majors is a wide jump, so the inputs the workflow depends on were checked rather than assumed: pattern and merge-multiple still exist on download-artifact, which the cross-job local feed assembly relies on, as do if-no-files-found on upload-artifact and dotnet-version on setup-dotnet. Co-Authored-By: Claude Opus 5 <[email protected]>
nanchen2483
approved these changes
Aug 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.
The runners now default to Node 24 and warn on every step that the Node 20 actions are deprecated. The workflow runs fine — this is noise, not breakage — but it will become breakage when Node 20 is removed.
runs.usingactions/checkoutnode24actions/setup-dotnetnode24actions/upload-artifactnode24actions/download-artifactnode24Four majors is a wide jump, so I checked the inputs this workflow actually depends on rather than assuming they survived:
patternandmerge-multipleondownload-artifact— these are load bearing, since thetest,managedandpublishjobs assemble a local NuGet feed from the artifacts the two native jobs upload.if-no-files-found: erroronupload-artifact, which is what makes a job that silently produced no packages fail.dotnet-versiononsetup-dotnet, including the multi-line form.All still present.
Off
mainand independent, so it can merge in any order relative to #6 and #7. #7 also edits thesetup-dotnetsteps, so whichever lands second may need a trivial rebase — mine to resolve.🤖 Generated with Claude Code