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

Update Node.js to v20 - autoclosed #7731

Closed
wants to merge 1 commit into from
Closed

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 27, 2023

Mend Renovate

This PR contains the following updates:

Package Type Update Change Age Adoption Passing Confidence
node (source) engines major 16 -> 20 age adoption passing confidence
@types/node (source) devDependencies major 16.18.68 -> 20.14.12 age adoption passing confidence

Release Notes

nodejs/node (node)

v20.16.0

Compare Source

v20.15.1

Compare Source

v20.15.0: 2024-06-20, Version 20.15.0 'Iron' (LTS), @​marco-ippolito

Compare Source

test_runner: support test plans

It is now possible to count the number of assertions and subtests that are expected to run within a test. If the number of assertions and subtests that run does not match the expected count, the test will fail.

test('top level test', (t) => {
  t.plan(2);
  t.assert.ok('some relevant assertion here');
  t.subtest('subtest', () => {});
});

Contributed by Colin Ihrig in #​52860

inspector: introduce the --inspect-wait flag

This release introduces the --inspect-wait flag, which allows debugger to wait for attachement. This flag is useful when you want to debug the code from the beginning. Unlike --inspect-brk, which breaks on the first line, this flag waits for debugger to be connected and then runs the code as soon as a session is established.

Contributed by Kohei Ueno in #​52734

zlib: expose zlib.crc32()

This release exposes the crc32() function from zlib to user-land.

It computes a 32-bit Cyclic Redundancy Check checksum of data. If
value is specified, it is used as the starting value of the checksum,
otherwise, 0 is used as the starting value.

The CRC algorithm is designed to compute checksums and to detect error
in data transmission. It's not suitable for cryptographic authentication.

const zlib = require('node:zlib');
const { Buffer } = require('node:buffer');

let crc = zlib.crc32('hello');  // 907060870
crc = zlib.crc32('world', crc);  // 4192936109

crc = zlib.crc32(Buffer.from('hello', 'utf16le'));  // 1427272415
crc = zlib.crc32(Buffer.from('world', 'utf16le'), crc);  // 4150509955

Contributed by Joyee Cheung in #​52692

cli: allow running wasm in limited vmem with --disable-wasm-trap-handler

By default, Node.js enables trap-handler-based WebAssembly bound
checks. As a result, V8 does not need to insert inline bound checks
int the code compiled from WebAssembly which may speedup WebAssembly
execution significantly, but this optimization requires allocating
a big virtual memory cage (currently 10GB). If the Node.js process
does not have access to a large enough virtual memory address space
due to system configurations or hardware limitations, users won't
be able to run any WebAssembly that involves allocation in this
virtual memory cage and will see an out-of-memory error.

$ ulimit -v 5000000
$ node -p "new WebAssembly.Memory({ initial: 10, maximum: 100 });"
[eval]:1
new WebAssembly.Memory({ initial: 10, maximum: 100 });
^

RangeError: WebAssembly.Memory(): could not allocate memory
    at [eval]:1:1
    at runScriptInThisContext (node:internal/vm:209:10)
    at node:internal/process/execution:118:14
    at [eval]-wrapper:6:24
    at runScript (node:internal/process/execution:101:62)
    at evalScript (node:internal/process/execution:136:3)
    at node:internal/main/eval_string:49:3

--disable-wasm-trap-handler disables this optimization so that
users can at least run WebAssembly (with a less optimial performance)
when the virtual memory address space available to their Node.js
process is lower than what the V8 WebAssembly memory cage needs.

Contributed by Joyee Cheung in #​52766

Other Notable Changes
Commits

v20.14.0

Compare Source

v20.13.1: 2024-05-09, Version 20.13.1 'Iron' (LTS), @​marco-ippolito

Compare Source

2024-05-09, Version 20.13.1 'Iron' (LTS), @​marco-ippolito

Revert "tools: install npm PowerShell scripts on Windows"

Due to a regression in the npm installation on Windows, this commit reverts the change that installed npm PowerShell scripts on Windows.

Commits
  • [b7d80802cc] - Revert "tools: install npm PowerShell scripts on Windows" (marco-ippolito) #​52897

v20.13.0

Compare Source

v20.12.2: 2024-04-10, Version 20.12.2 'Iron' (LTS), @​RafaelGSS

Compare Source

This is a security release.

Notable Changes
  • CVE-2024-27980 - Command injection via args parameter of child_process.spawn without shell option enabled on Windows
Commits

v20.12.1

Compare Source

v20.12.0

Compare Source

v20.11.1

Compare Source

v20.11.0

Compare Source

v20.10.0

Compare Source

v20.9.0

Compare Source

v20.8.1: 2023-10-13, Version 20.8.1 (Current), @​RafaelGSS

Compare Source

This is a security release.

Notable Changes

The following CVEs are fixed in this release:

More detailed information on each of the vulnerabilities can be found in October 2023 Security Releases blog post.

Commits

v20.8.0: 2023-09-28, Version 20.8.0 (Current), @​ruyadorno

Compare Source

Notable Changes
Stream performance improvements

Performance improvements to writable and readable streams, improving the creation and destruction by ±15% and reducing the memory overhead each stream takes in Node.js

Contributed by Benjamin Gruenbaum in #​49745 and Raz Luvaton in #​49834.

Performance improvements for readable webstream, improving readable stream async iterator consumption by ±140% and improving readable stream pipeTo consumption by ±60%

Contributed by Raz Luvaton in #​49662 and #​49690.

Rework of memory management in vm APIs with the importModuleDynamically option

This rework addressed a series of long-standing memory leaks and use-after-free issues in the following APIs that support importModuleDynamically:

  • vm.Script
  • vm.compileFunction
  • vm.SyntheticModule
  • vm.SourceTextModule

This should enable affected users (in particular Jest users) to upgrade from older versions of Node.js.

Contributed by Joyee Cheung in #​48510.

Other notable changes
Commits

Configuration

📅 Schedule: Branch creation - "before 3am on Friday" (UTC), Automerge - 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 these updates again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot requested review from avolkovi, sam-gc, yuchenshi and a team as code owners October 27, 2023 00:32
@changeset-bot
Copy link

changeset-bot bot commented Oct 27, 2023

⚠️ No Changeset found

Latest commit: a957b4b

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@google-oss-bot
Copy link
Contributor

google-oss-bot commented Oct 27, 2023

@google-oss-bot
Copy link
Contributor

google-oss-bot commented Oct 27, 2023

@renovate renovate bot force-pushed the renovate/node-20.x branch from 9e34286 to 631a393 Compare October 31, 2023 13:39
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 8b430a6 to e65c920 Compare November 12, 2023 15:10
@renovate renovate bot force-pushed the renovate/node-20.x branch 5 times, most recently from e624da4 to 5d4a42d Compare November 22, 2023 05:25
@renovate renovate bot force-pushed the renovate/node-20.x branch 3 times, most recently from 0cfe3dc to 89c55bd Compare November 29, 2023 20:48
@renovate renovate bot force-pushed the renovate/node-20.x branch 3 times, most recently from 71c45d7 to 11c8a8d Compare December 7, 2023 11:12
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 0cc25fe to a01d7ea Compare December 18, 2023 18:12
@renovate renovate bot force-pushed the renovate/node-20.x branch from a01d7ea to 0e364bc Compare December 30, 2023 02:32
@renovate renovate bot force-pushed the renovate/node-20.x branch 3 times, most recently from 5fd4b54 to 35eaaf2 Compare January 11, 2024 06:51
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 170caf4 to 74a5c59 Compare January 15, 2024 11:56
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 41f958a to c82cdc5 Compare April 9, 2024 21:44
@renovate renovate bot force-pushed the renovate/node-20.x branch 4 times, most recently from d575639 to 66d879c Compare May 8, 2024 14:49
@renovate renovate bot changed the title Update Node.js to v20 chore(deps): update node.js to v20 May 9, 2024
@renovate renovate bot force-pushed the renovate/node-20.x branch from 66d879c to 81df50b Compare May 14, 2024 06:17
@renovate renovate bot changed the title chore(deps): update node.js to v20 Update Node.js to v20 May 23, 2024
@renovate renovate bot force-pushed the renovate/node-20.x branch 5 times, most recently from 1e154c2 to ba2d414 Compare June 5, 2024 07:47
@renovate renovate bot force-pushed the renovate/node-20.x branch 6 times, most recently from 31c32da to 28f5d9b Compare June 22, 2024 09:11
@renovate renovate bot force-pushed the renovate/node-20.x branch from 28f5d9b to 8618065 Compare June 25, 2024 23:05
@renovate renovate bot force-pushed the renovate/node-20.x branch from 8618065 to 7893d5e Compare July 5, 2024 21:13
@renovate renovate bot force-pushed the renovate/node-20.x branch from 7893d5e to 595f199 Compare July 16, 2024 20:35
@renovate renovate bot force-pushed the renovate/node-20.x branch from 595f199 to a957b4b Compare July 23, 2024 18:29
Copy link
Contributor Author

renovate bot commented Jul 26, 2024

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

@renovate renovate bot changed the title Update Node.js to v20 Update Node.js to v20 - autoclosed Oct 29, 2024
@renovate renovate bot closed this Oct 29, 2024
@renovate renovate bot deleted the renovate/node-20.x branch October 29, 2024 02:21
@firebase firebase locked and limited conversation to collaborators Nov 29, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants