Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: bump node to v18.16.0 (main) #37973

Merged
merged 19 commits into from
Apr 18, 2023
Merged

chore: bump node to v18.16.0 (main) #37973

merged 19 commits into from
Apr 18, 2023

Conversation

electron-roller[bot]
Copy link
Contributor

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.

@electron-roller electron-roller bot requested a review from a team as a code owner April 13, 2023 13:02
@electron-roller electron-roller bot added no-backport semver/patch backwards-compatible bug fixes labels Apr 13, 2023
@electron-cation electron-cation bot added new-pr 🌱 PR opened in the last 24 hours and removed new-pr 🌱 PR opened in the last 24 hours labels Apr 13, 2023
@codebytere codebytere requested a review from a team as a code owner April 14, 2023 13:26
@codebytere codebytere self-assigned this Apr 14, 2023
@codebytere codebytere force-pushed the roller/node/main branch 2 times, most recently from 03f68fc to 60b2a8f Compare April 16, 2023 17:55
@codebytere codebytere force-pushed the roller/node/main branch 3 times, most recently from 6b325be to bdb5238 Compare April 18, 2023 12:28
@codebytere codebytere merged commit de192c2 into main Apr 18, 2023
10 checks passed
@codebytere codebytere deleted the roller/node/main branch April 18, 2023 20:23
@release-clerk
Copy link

release-clerk bot commented Apr 18, 2023

Release Notes Persisted

Updated Node.js to v18.16.0.

// 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()) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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?

@baparham
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
no-backport semver/patch backwards-compatible bug fixes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants