Chore: update dev dependencies and workflows to node16 #1066
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
There was a problem hiding this comment.
If you don't want to need to continually update so many spots for this, you could consider using the newer node-version-file parameter of actions/setup-node combined with a .node-version file. 🙃
https://github.com/actions/setup-node/blob/main/docs/advanced-usage.md#node-version-file
.node-version file is the entire 3-part SemVer version, e.g. 16.2.0, but the actions/setup-node code looks like it would still allow you to put a range like 16.x in it. 🤷🏻♂️
brcrista
approved these changes
Apr 29, 2022
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.
Node 12 is EOL soon, so lets go ahead and move to node 16