Fix Node.js 20 deprecation warnings in release workflow - #6
Merged
Merged
Conversation
actions/upload-artifact@v4 and actions/download-artifact@v4 still declare node20 as their runtime, which GitHub now flags as deprecated (runs are force-upgraded to node24 for now). Bumping to v7/v8 respectively picks up versions that declare node24 natively; neither changes the inputs this workflow uses (name, path, if-no-files-found, merge-multiple). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01AKmYgyL2p8FVFu9Wx13t4K
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
actions/upload-artifact@v4andactions/download-artifact@v4still declarenode20as their runtime, which GitHub Actions now warns about (runs are being force-upgraded tonode24in the meantime, per the warnings on thev0.1.2release run).actions/upload-artifact@v7andactions/download-artifact@v8, both of which declarenode24natively. Neither changes the inputs this workflow relies on (name,path,if-no-files-foundfor upload;path,merge-multiplefor download), so this is a drop-in fix.Test plan
v7/v8action.yml input schemas againstv4— unchanged for the inputs this workflow uses.🤖 Generated with Claude Code
https://claude.ai/code/session_01AKmYgyL2p8FVFu9Wx13t4K