ci: Update to Node20 actions #4571
Merged
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
richb-hanover
changed the title
|
Super, thanks a lot @richb-hanover ! |
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.
Rather than use my
richb-hanover/cargo(which will forever lag the proper versions), switch toclechasseur/rs-cargowhich seems to be in active maintenance. This clears up the lion's share of "Node 16 is deprecated..." warnings during builds.@clechasseur was also kind enough to update
rustsec/audit-check@v1to use Node 20 (it'sv1.4.1now). However, it appears that the upstream hasn't published that new action. There's an Issue in the repo requesting this.Once that's complete, it looks as if all the warnings during nightly builds will have been eliminated.