feat: add node 18.x support #155
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
mate-from-mattr
force-pushed
the
ma/prd-4316/nodejs-18
branch
from
a07953a
to
22962e7
Compare
mate-from-mattr
changed the title
mate-from-mattr
changed the title
mate-from-mattr
changed the title
afonsobarracha
approved these changes
Sep 18, 2023
kenhuang
approved these changes
Sep 18, 2023
Merged
8 tasks
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.
Description
@mattrglobal/node-bbs-signatures. This has the latest binaries that support Node 18.xTests for the changes have been added (for bug fixes / features)Motivation and Context
Part of the organisation-wide upgrade to Node 18.x.
Does this PR introduce a breaking change?
Which merge strategy will you use?