Update GitHub Actions to Node 24 - #357
Merged
Merged
Conversation
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
Root cause
The workflows pinned action majors whose bundled JavaScript targets Node.js
20. GitHub now forces those actions onto Node.js 24 and emits deprecation
annotations on every run.
The replacement majors are
actions/checkout@v7,actions/setup-python@v7,actions/cache@v6,actions/upload-artifact@v7, andactions/download-artifact@v8. Theseworkflows use only stable inputs and run on GitHub-hosted runners, which
satisfy the new runner requirement.
Verification
./lint.shpython -m pytest test/— 937 passedpython setup.py --version—2.3.0rc17git diff --checkCloses #355.