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 >=20.17.0 #2173

Merged
merged 1 commit into from
Sep 4, 2024
Merged

Update Node.js to >=20.17.0 #2173

merged 1 commit into from
Sep 4, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 1, 2024

This PR contains the following updates:

Package Type Update Change Age Adoption Passing Confidence
node (source) engines minor >=20.12.2 -> >=20.17.0 age adoption passing confidence
@types/node (source) devDependencies minor ^20.12.7 -> ^20.16.4 age adoption passing confidence
node minor 20.12.2-alpine -> 20.17.0-alpine age adoption passing confidence
node (source) minor 20.12.2 -> 20.17.0 age adoption passing confidence

Release Notes

nodejs/node (node)

v20.17.0

Compare Source

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


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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 a review from h3poteto as a code owner May 1, 2024 18:56
@renovate renovate bot changed the title Update dependency @types/node to ^20.12.8 Update dependency @types/node to ^20.12.9 May 6, 2024
@renovate renovate bot changed the title Update dependency @types/node to ^20.12.9 Update dependency @types/node to ^20.12.10 May 6, 2024
@renovate renovate bot changed the title Update dependency @types/node to ^20.12.10 Update Node.js to >=20.13.0 May 7, 2024
@renovate renovate bot force-pushed the renovate/node-20.x branch 3 times, most recently from bb9f882 to f211418 Compare May 8, 2024 13:10
@renovate renovate bot changed the title Update Node.js to >=20.13.0 Update Node.js to >=20.13.1 May 9, 2024
@renovate renovate bot force-pushed the renovate/node-20.x branch 3 times, most recently from 38cd8cc to 198c253 Compare May 14, 2024 06:17
@renovate renovate bot changed the title Update Node.js to >=20.13.1 Update Node.js to >=20.14.0 May 28, 2024
@renovate renovate bot force-pushed the renovate/node-20.x branch 7 times, most recently from 3097728 to c3a349b Compare June 4, 2024 00:50
@renovate renovate bot force-pushed the renovate/node-20.x branch 5 times, most recently from 5b8a4e7 to bafe36e Compare June 20, 2024 16:27
@renovate renovate bot changed the title Update Node.js to >=20.14.0 Update Node.js to >=20.15.0 Jun 20, 2024
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from bace8ae to 1b8ad8d Compare June 22, 2024 11:19
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 3e388ad to 8419973 Compare June 25, 2024 23:28
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 33a312d to f88140e Compare July 8, 2024 20:12
@renovate renovate bot changed the title Update Node.js to >=20.15.0 Update Node.js to >=20.15.1 Jul 8, 2024
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 8c5ba81 to f8593e9 Compare July 23, 2024 18:34
@renovate renovate bot changed the title Update Node.js to >=20.15.1 Update Node.js to >=20.16.0 Jul 24, 2024
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 30d9f49 to 862e038 Compare July 28, 2024 10:19
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 9dca171 to 2fa51b8 Compare August 16, 2024 19:20
@renovate renovate bot force-pushed the renovate/node-20.x branch 3 times, most recently from 00b626a to 99c0662 Compare August 21, 2024 17:43
@renovate renovate bot changed the title Update Node.js to >=20.16.0 Update Node.js to >=20.17.0 Aug 21, 2024
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 1250608 to ab02c9c Compare August 28, 2024 03:04
@h3poteto h3poteto merged commit 6dbdd55 into master Sep 4, 2024
13 checks passed
@h3poteto h3poteto deleted the renovate/node-20.x branch September 4, 2024 14:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant