chore(node): add node 20 to ci #313
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
rwaskiewicz
requested review from
JessicaSachs,
alicewriteswrongs and
tanner-reits
tanner-reits
approved these changes
May 18, 2023
this commit updates the development dependencies for the project to use node v20. by updating the versions of node/npm that volta uses, the versioning changes are/will be automatically picked up by the ci workflow (as they pull from the volta key in `package.json`)
rwaskiewicz
force-pushed
the
rwaskiewicz/node-20
branch
from
4469940 to
f9fe4f7
Compare
alicewriteswrongs
approved these changes
Jun 2, 2023
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.
Pull request checklist
Please check if your PR fulfills the following requirements:
npm run build) was run locally and any changes were pushednpm test) were run locally and passednpm run prettier) was run locally and passedPull request type
Please check the type of change your PR introduces:
What is the current behavior?
We build/develop the project using Node 16
GitHub Issue Number: N/A
What is the new behavior?
this commit updates the development dependencies for the project to use node v20. by updating the versions of node/npm that volta uses, the versioning changes are/will be automatically picked up by the ci workflow (as they pull from the volta key in
package.json)Does this introduce a breaking change?
Testing
Unit tests continue to pass
Other information