chore: bump node to v18.16.0 (main)#37973
Merged
codebytere merged 19 commits intomainfrom Apr 18, 2023
Merged
Conversation
03f68fc to
60b2a8f
Compare
6b325be to
bdb5238
Compare
64e54ff to
3e0eb41
Compare
VerteDinde
approved these changes
Apr 18, 2023
|
Release Notes Persisted
|
nornagon
reviewed
Apr 18, 2023
| // true to this function instead of the original string. Any other string | ||
| // value will be interpreted as custom DH parameters below. | ||
| +#ifndef OPENSSL_IS_BORINGSSL | ||
| if (args[0]->IsTrue()) { |
Contributor
There was a problem hiding this comment.
should we throw or otherwise fail more noisily here? if we don't implement the "auto" setting, but the client requests it, what do we do?
|
Is there a reason this is marked for no backport? This would be nice to have in electron 25 at least since this fixes some security vulnerabilities in c-ares. |
3 tasks
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
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.
Updating Node.js to v18.16.0.
See all changes in v18.15.0..v18.16.0
Notes: Updated Node.js to v18.16.0.