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.15.0 #293

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update Node.js to v20.15.0 #293

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 27, 2024

Mend Renovate

This PR contains the following updates:

Package Type Update Change Age Adoption Passing Confidence
node (source) volta minor 20.11.0 -> 20.15.0 age adoption passing confidence
@types/node (source) devDependencies minor 20.11.7 -> 20.14.10 age adoption passing confidence

Release Notes

nodejs/node (node)

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


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 has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot changed the title Update dependency @types/node to v20.11.8 Update dependency @types/node to v20.11.9 Jan 28, 2024
@renovate renovate bot changed the title Update dependency @types/node to v20.11.9 Update dependency @types/node to v20.11.10 Jan 28, 2024
@renovate renovate bot changed the title Update dependency @types/node to v20.11.10 Update dependency @types/node to v20.11.11 Jan 30, 2024
@renovate renovate bot changed the title Update dependency @types/node to v20.11.11 Update dependency @types/node to v20.11.13 Jan 31, 2024
@renovate renovate bot changed the title Update dependency @types/node to v20.11.13 Update dependency @types/node to v20.11.14 Jan 31, 2024
@renovate renovate bot changed the title Update dependency @types/node to v20.11.14 Update dependency @types/node to v20.11.15 Feb 1, 2024
@renovate renovate bot changed the title Update dependency @types/node to v20.11.15 Update dependency @types/node to v20.11.16 Feb 1, 2024
@renovate renovate bot changed the title Update dependency @types/node to v20.11.16 Update dependency @types/node to v20.11.17 Feb 8, 2024
@renovate renovate bot changed the title Update dependency @types/node to v20.11.17 Update Node.js to v20.11.1 Feb 14, 2024
@renovate renovate bot force-pushed the renovate/node-20.x branch 3 times, most recently from c09decc to c587897 Compare February 15, 2024 19:51
@renovate renovate bot force-pushed the renovate/node-20.x branch 5 times, most recently from 57f8ced to db5b3e8 Compare February 29, 2024 17:56
@renovate renovate bot force-pushed the renovate/node-20.x branch 3 times, most recently from 896a87b to a08b398 Compare March 13, 2024 14:01
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from d893232 to 04623f9 Compare March 18, 2024 21:38
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 5d27dc5 to d33ba6d Compare April 10, 2024 18:06
@renovate renovate bot changed the title Update Node.js to v20.12.1 Update Node.js to v20.12.2 Apr 10, 2024
@renovate renovate bot force-pushed the renovate/node-20.x branch 3 times, most recently from 40216ae to 8605887 Compare May 6, 2024 18:17
@renovate renovate bot changed the title Update Node.js to v20.12.2 Update Node.js to v20.13.0 May 7, 2024
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 035504e to 5d05abb Compare May 8, 2024 14:03
@renovate renovate bot changed the title Update Node.js to v20.13.0 Update Node.js to v20.13.1 May 9, 2024
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from da887ed to 41c661f Compare May 14, 2024 07:33
@renovate renovate bot changed the title Update Node.js to v20.13.1 Update Node.js to v20.14.0 May 28, 2024
@renovate renovate bot force-pushed the renovate/node-20.x branch 5 times, most recently from 5b7c2f9 to 673fe06 Compare June 5, 2024 09:58
@renovate renovate bot force-pushed the renovate/node-20.x branch 5 times, most recently from 29f7d7d to ff9cbc9 Compare June 20, 2024 20:11
@renovate renovate bot changed the title Update Node.js to v20.14.0 Update Node.js to v20.15.0 Jun 20, 2024
@renovate renovate bot force-pushed the renovate/node-20.x branch 3 times, most recently from 3226714 to 8688f11 Compare June 25, 2024 22:14
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.

None yet

0 participants