Upgrade to setup-python@v4 and cache@v4 for GH actions #2041
Conversation
This file contains 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
andrew-platt
force-pushed
the
b/GHactions_node16_deprecate
branch
from
e26acf1
to
423ed81
Compare
deslaughter
approved these changes
Feb 19, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This should be ready to merge
Feature or improvement description
GitHub upgraded the actions to use node.js 20 instead of node.js 16. We were getting deprecation warnings like:
https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/
Fixing this requires updating two packages we use in testing:
actions/setup-python@v3-->actions/setup-python@v5actions/cache@v3-->actions/cache@v4For
actions/setup-python, version 5.0.0 uses the newnode 20(see actions/setup-python#735)Impacted areas of the software
Automated testing through GitHub actions only