Upgrade node infra from node16 -> node20. #444
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
The GitHub node16 CI infrastructure is going away this spring: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/ This includes upgrading actions we use in our own CI that currently warn due to this same issue of node16 going away in the spring. Fixes gabrielfalcao#443
|
Aha - I just found #434. Perhaps this does a bit better since it also includes upgrading CI to check against node 20 as well. It looks like CI is failing and the failure is pre-existing. I'll try this out over in the pex-tool org anyhow. |
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.
The GitHub node16 CI infrastructure is going away this spring:
https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/
This includes upgrading actions we use in our own CI that currently warn
due to this same issue of node16 going away in the spring.
Fixes #443