ci: Bump Node.js to v18 #183
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
nhynes
approved these changes
Sep 13, 2023
|
Seems I have bumped into nock/nock#2397. Added workaround... |
matevz
force-pushed
the
matevz/deps/node-v18
branch
from
7750be4
to
cdba175
Compare
matevz
force-pushed
the
matevz/deps/node-v18
branch
from
cdba175
to
9b4468d
Compare
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 PR bumps Node.js to v18.x. Since
nockused for unit tests ofsapphire-paratimejs client does not support Node.js v18.x yet (nock/nock#2397), the--no-experimental-fetchflag is added in the CI tests.