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(deps): update node.js to >=20.15.0 #186

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 25, 2023

Mend Renovate

This PR contains the following updates:

Package Type Update Change Age Adoption Passing Confidence
node (source) engines minor >=20.0.0 -> >=20.15.0 age adoption passing confidence
@types/node (source) devDependencies minor ^20.9.0 -> ^20.14.8 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

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 4am on Monday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, 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 added dependencies Update one or more dependencies version patch Increment the patch version when merged labels Dec 25, 2023
@renovate renovate bot changed the title chore(dev-deps): update dependency @types/node to ^20.10.5 chore(dev-deps): update dependency @types/node to ^20.10.6 Dec 30, 2023
@renovate renovate bot changed the title chore(dev-deps): update dependency @types/node to ^20.10.6 chore(dev-deps): update dependency @types/node to ^20.10.7 Jan 7, 2024
@renovate renovate bot changed the title chore(dev-deps): update dependency @types/node to ^20.10.7 chore(dev-deps): update dependency @types/node to ^20.10.8 Jan 9, 2024
@renovate renovate bot changed the title chore(dev-deps): update dependency @types/node to ^20.10.8 chore(dev-deps): update dependency @types/node to ^20.11.0 Jan 11, 2024
@renovate renovate bot changed the title chore(dev-deps): update dependency @types/node to ^20.11.0 chore(dev-deps): update dependency @types/node to ^20.11.1 Jan 15, 2024
@renovate renovate bot changed the title chore(dev-deps): update dependency @types/node to ^20.11.1 chore(dev-deps): update dependency @types/node to ^20.11.2 Jan 15, 2024
@renovate renovate bot changed the title chore(dev-deps): update dependency @types/node to ^20.11.2 chore(dev-deps): update dependency @types/node to ^20.11.3 Jan 15, 2024
@renovate renovate bot changed the title chore(dev-deps): update dependency @types/node to ^20.11.3 chore(dev-deps): update dependency @types/node to ^20.11.4 Jan 16, 2024
@renovate renovate bot changed the title chore(dev-deps): update dependency @types/node to ^20.11.4 chore(dev-deps): update dependency @types/node to ^20.11.5 Jan 17, 2024
@renovate renovate bot force-pushed the renovate/node-20.x branch 3 times, most recently from d81319c to e6c4d27 Compare January 17, 2024 15:45
@renovate renovate bot changed the title chore(dev-deps): update dependency @types/node to ^20.11.5 chore(dev-deps): update dependency @types/node to ^20.11.6 Jan 24, 2024
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from c37816d to 3562cd3 Compare January 26, 2024 05:38
@renovate renovate bot changed the title chore(dev-deps): update dependency @types/node to ^20.11.6 chore(dev-deps): update dependency @types/node to ^20.11.7 Jan 26, 2024
@renovate renovate bot changed the title chore(dev-deps): update dependency @types/node to ^20.11.7 chore(dev-deps): update dependency @types/node to ^20.11.8 Jan 27, 2024
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 46674dd to 21a2154 Compare May 8, 2024 14:00
@renovate renovate bot changed the title chore(dev-deps): update dependency @types/node to ^20.12.10 chore(dev-deps): update dependency @types/node to ^20.12.11 May 8, 2024
@renovate renovate bot force-pushed the renovate/node-20.x branch 3 times, most recently from f1fb43c to 7818c85 Compare May 13, 2024 18:03
@renovate renovate bot changed the title chore(dev-deps): update dependency @types/node to ^20.12.11 chore(dev-deps): update dependency @types/node to ^20.12.12 May 14, 2024
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from b83de6f to 55912ef Compare May 16, 2024 13:22
@renovate renovate bot changed the title chore(dev-deps): update dependency @types/node to ^20.12.12 chore(deps): update node.js to >=20.13.1 May 28, 2024
@renovate renovate bot changed the title chore(deps): update node.js to >=20.13.1 chore(deps): 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 aa00a40 to 831c087 Compare June 5, 2024 09:44
@renovate renovate bot force-pushed the renovate/node-20.x branch 4 times, most recently from aac9401 to ad44b65 Compare June 18, 2024 08:29
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from c528878 to ed2b25c Compare June 20, 2024 19:10
@renovate renovate bot changed the title chore(deps): update node.js to >=20.14.0 chore(deps): update node.js to >=20.15.0 Jun 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Update one or more dependencies version patch Increment the patch version when merged
Development

Successfully merging this pull request may close these issues.

None yet

0 participants