Update Node.js to v18 #60
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "renovate/node-18.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
16.15.0-bullseye->18.0.0-bullseyeRelease Notes
nodejs/node
v18.0.0Compare Source
Node.js 18 is here! Highlights include the update of the V8 JavaScript engine to 10.1, global fetch enabled by default, and a core test runner module.
Initially, Node.js 18 will replace Node.js 17 as our ‘Current’ release line. As per the release schedule, Node.js 18 will be the ‘Current’ release for the next 6 months and then promoted to Long-term Support (LTS) in October 2022. Once promoted to long-term support the release will be designated the codename ‘Hydrogen’. Node.js 18 will be supported until April 2025.
Notable Changes
Deprecations and Removals
fs.write,fs.writeFileSync(Livia Medeiros) #42607dns.lookupanddnsPromises.lookupoptions type coercion (Antoine du Hamel) #41431fetch (experimental)
An experimental fetch API is available on the global scope by default. The implementation is based upon undici, an HTTP/1.1 client written for Node.js by contributors to the project.
Through this addition, the following globals are made available:
fetch,FormData,Headers,Request,Response.Disable this API with the
--no-experimental-fetchcommand-line flag.Contributed by Michaël Zasso in #41811.
HTTP Timeouts
server.headersTimeoutwhich limits the amount of time the parser will wait to receive the complete HTTP headers is now set to60000(60 seconds) by default.server.requestTimeoutwhich sets the timeout value in milliseconds for receiving the entire request from the client is now set to300000(5 minutes) by default.If these timeouts expire, the server responds with status 408 without forwarding the request to the request listener and then closes the connection.
Both timeouts must be set to a non-zero value to protect against potential Denial-of-Service attacks in case the server is deployed without a reverse proxy in front.
Contributed by Paolo Insogna in #41263.
Test Runner module (experimental)
The
node:testmodule facilitates the creation of JavaScript tests that report results in TAP format. To access it:import test from 'node:test';This module is only available under the
node:scheme.The following is an example implementation of a parent test with two subtests:
Read more in https://nodejs.org/dist/latest-v18.x/docs/api/test.html.
Contributed by Colin Ihrig in #42325.
Toolchain and Compiler Upgrades
Prebuilt binaries for 32-bit Windows will initially not be available due to issues building the V8 dependency in Node.js. We hope to restore 32-bit Windows binaries for Node.js 18 with a future V8 update.
Node.js does not support running on operating systems that are no longer supported by their vendor. For operating systems where their vendor has planned to end support earlier than April 2025, such as Windows 8.1 (January 2023) and Windows Server 2012 R2 (October 2023), support for Node.js 18 will end at the earlier date.
Full details about the supported toolchains and compilers are documented in the Node.js BUILDING.md file.
Contributed by Richard Lau in #42292, #42604 and #42659,and Michaël Zasso in #42105 and #42666.
V8 10.1
The V8 engine is updated to version 10.1, which is part of Chromium 101. Compared to the version included in Node.js 17.9.0, the following new features are included:
findLastandfindLastIndexarray methods.Intl.LocaleAPI.Intl.supportedValuesOffunction.The data format returned by the serialization API (
v8.serialize(value)) has changed, and cannot be deserialized by earlier versions of Node.js. On the other hand, it is still possible to deserialize the previous format, as the API is backwards-compatible.Contributed by Michaël Zasso in #42657.
Web Streams API (experimental)
Node.js now exposes the experimental implementation of the Web Streams API on the global scope. This means the following APIs are now globally available:
ReadableStream,ReadableStreamDefaultReader,ReadableStreamBYOBReader,ReadableStreamBYOBRequest,ReadableByteStreamController,ReadableStreamDefaultController,TransformStream,TransformStreamDefaultController,WritableStream,WritableStreamDefaultWriter,WritableStreamDefaultController,ByteLengthQueuingStrategy,CountQueuingStrategy,TextEncoderStream,TextDecoderStream,CompressionStream,DecompressionStream.Contributed James Snell in #39062, and Antoine du Hamel in #42225.
Other Notable Changes
server.address()return an integer forfamily(Antoine du Hamel) #41431Semver-Major Commits
Semver-Minor Commits
Semver-Patch Commits
v17.9.0Compare Source
Notable Changes
Commits
v17.8.0Compare Source
Notable Changes
Commits
v17.7.2Compare Source
This is a security release.
Notable Changes
Update to OpenSSL 3.0.2, which addresses the following vulnerability:
BN_mod_sqrt()reachable when parsing certificates (High)(CVE-2022-0778)More details are available at https://www.openssl.org/news/secadv/20220315.txt
Commits
v17.7.1Compare Source
Notable Changes
Fixed regression in url.resolve()
This release fixes an issue introduced in Node.js v17.7.0 with some URLs
that contain
@. This issue affected yarn 1. This version reverts thechange that introduced the regression.
Commits
v17.6.0Compare Source
Notable Changes
Dependency Updates
New Collaborators
Commits
v17.5.0Compare Source
Notable Changes
Add fetch API
Adds experimental support to the fetch API. This adds a
--experimental-fetchflag that installs the
fetch,Request,ReponseandHeadersglobals.Add stream methods
Other Notable Changes
Commits
v17.4.0Compare Source
Notable Changes
Commits
v17.3.1Compare Source
This is a security release.
Notable changes
Improper handling of URI Subject Alternative Names (Medium)(CVE-2021-44531)
Accepting arbitrary Subject Alternative Name (SAN) types, unless a PKI is specifically defined to use a particular SAN type, can result in bypassing name-constrained intermediates. Node.js was accepting URI SAN types, which PKIs are often not defined to use. Additionally, when a protocol allows URI SANs, Node.js did not match the URI correctly.
Versions of Node.js with the fix for this disable the URI SAN type when checking a certificate against a hostname. This behavior can be reverted through the
--security-revertcommand-line option.More details will be available at CVE-2021-44531 after publication.
Certificate Verification Bypass via String Injection (Medium)(CVE-2021-44532)
Node.js converts SANs (Subject Alternative Names) to a string format. It uses this string to check peer certificates against hostnames when validating connections. The string format was subject to an injection vulnerability when name constraints were used within a certificate chain, allowing the bypass of these name constraints.
Versions of Node.js with the fix for this escape SANs containing the problematic characters in order to prevent the injection. This behavior can be reverted through the
--security-revertcommand-line option.More details will be available at CVE-2021-44532 after publication.
Incorrect handling of certificate subject and issuer fields (Medium)(CVE-2021-44533)
Node.js did not handle multi-value Relative Distinguished Names correctly. Attackers could craft certificate subjects containing a single-value Relative Distinguished Name that would be interpreted as a multi-value Relative Distinguished Name, for example, in order to inject a Common Name that would allow bypassing the certificate subject verification.
Affected versions of Node.js do not accept multi-value Relative Distinguished Names and are thus not vulnerable to such attacks themselves. However, third-party code that uses node's ambiguous presentation of certificate subjects may be vulnerable.
More details will be available at CVE-2021-44533 after publication.
Prototype pollution via
console.tableproperties (Low)(CVE-2022-21824)Due to the formatting logic of the
console.table()function it was not safe to allow user controlled input to be passed to thepropertiesparameter while simultaneously passing a plain object with at least one property as the first parameter, which could be__proto__. The prototype pollution has very limited control, in that it only allows an empty string to be assigned numerical keys of the object prototype.Versions of Node.js with the fix for this use a null protoype for the object these properties are being assigned to.
More details will be available at CVE-2022-21824 after publication.
Thanks to Patrik Oldsberg (rugvip) for reporting this vulnerability.
Commits
v17.3.0Compare Source
Notable changes
OpenSSL-3.0.1
OpenSSL-3.0.1 contains a fix for CVE-2021-4044: Invalid handling of X509_verify_cert() internal errors in libssl (Moderate). This is a vulnerability in OpenSSL that may be exploited through Node.js. More information can be read here: https://www.openssl.org/news/secadv/20211214.txt.
Contributed by Richard Lau #41177.
Other Notable Changes
getActiveResourcesInfo()(Darshan Sen) #40813Commits
v17.2.0Compare Source
Notable Changes
Commits
v17.1.0Compare Source
Notable Changes
Commits
v17.0.1Compare Source
Notable Changes
Fixed distribution for native addon builds
This release fixes an issue introduced in Node.js v17.0.0, where some V8 headers
were missing from the distributed tarball, making it impossible to build native
addons. These headers are now included. #40526
Fixed stream issues
stream.promises.pipeline, which was introduced in version16.10.0, is fixed. It is now possible again to pass an array of streams to the
function. #40193
stream.Duplex.from, which didn't work properly when an asyncgenerator function was passed to it. #40499
Commits
v17.0.0Compare Source
Notable Changes
Deprecations and Removals
OpenSSL 3.0
Node.js now includes OpenSSL 3.0, specifically quictls/openssl which provides QUIC support. With OpenSSL 3.0 FIPS support is again available using the new FIPS module. For details about how to build Node.js with FIPS support please see BUILDING.md.
While OpenSSL 3.0 APIs should be mostly compatible with those provided by OpenSSL 1.1.1, we do anticipate some ecosystem impact due to tightened restrictions on the allowed algorithms and key sizes.
If you hit an
ERR_OSSL_EVP_UNSUPPORTEDerror in your application with Node.js 17, it’s likely that your application or a module you’re using is attempting to use an algorithm or key size which is no longer allowed by default with OpenSSL 3.0. A command-line option,--openssl-legacy-provider, has been added to revert to the legacy provider as a temporary workaround for these tightened restrictions.For details about all the features in OpenSSL 3.0 please see the OpenSSL 3.0 release blog.
Contributed in https://github.com/nodejs/node/pull/38512, https://github.com/nodejs/node/pull/40478
V8 9.5
The V8 JavaScript engine is updated to V8 9.5. This release comes with additional supported types for the
Intl.DisplayNamesAPI and ExtendedtimeZoneNameoptions in theIntl.DateTimeFormatAPI.You can read more details in the V8 9.5 release post - https://v8.dev/blog/v8-release-95.
Contributed by Michaël Zasso - https://github.com/nodejs/node/pull/40178
Readline Promise API
The
readlinemodule provides an interface for reading data from a Readablestream (such as
process.stdin) one line at a time.The following simple example illustrates the basic use of the
readlinemodule:Contributed by Antoine du Hamel - https://github.com/nodejs/node/pull/37947
Other Notable Changes
Semver-Major Commits
Semver-Minor Commits
Semver-Patch Commits
Configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.
7868281570to4e2d4297104e2d429710toa70499f3d0a70499f3d0toc2fac9e713c2fac9e713to920e577c18920e577c18to715aedcd5a715aedcd5atobaefe4fb5fRenovate Ignore Notification
Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future
18.xreleases. But if you manually upgrade to18.xthen Renovate will re-enableminorandpatchupdates automatically.If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.
Pull request closed