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 dependency node to v20 - autoclosed #611

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 27, 2023

This PR contains the following updates:

Package Update Change
node (source) major 18 -> 20

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

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" in timezone America/New_York, 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 this update again.


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

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

Copy link

codecov bot commented Nov 27, 2023

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 83.41%. Comparing base (bff992a) to head (b948876).
Report is 1 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #611   +/-   ##
=======================================
  Coverage   83.41%   83.41%           
=======================================
  Files          40       40           
  Lines        1073     1073           
  Branches      197      197           
=======================================
  Hits          895      895           
  Misses        166      166           
  Partials       12       12           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@renovate renovate bot force-pushed the renovate/node-20.x branch 6 times, most recently from f460784 to 374f2c5 Compare December 6, 2023 09:42
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 2794c35 to c78d78c Compare December 11, 2023 09:08
@renovate renovate bot force-pushed the renovate/node-20.x branch 4 times, most recently from d0b11bd to 0e2b45c Compare December 25, 2023 06:15
@renovate renovate bot force-pushed the renovate/node-20.x branch 3 times, most recently from da2c714 to 72414cb Compare January 1, 2024 08:10
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 3ad8c8f to a09507a Compare January 11, 2024 12:14
@renovate renovate bot force-pushed the renovate/node-20.x branch 5 times, most recently from aa7d409 to 407fc6f Compare January 22, 2024 07:47
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 738a9ab to 4adadfb Compare January 29, 2024 08:14
@renovate renovate bot force-pushed the renovate/node-20.x branch 3 times, most recently from ee360bc to e21156f Compare February 6, 2024 06:55
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 6d05779 to 95a0365 Compare February 16, 2024 07:43
@renovate renovate bot force-pushed the renovate/node-20.x branch 4 times, most recently from cbe66d2 to 088c574 Compare April 29, 2024 06:07
@renovate renovate bot force-pushed the renovate/node-20.x branch 4 times, most recently from aaf5315 to 64c9479 Compare May 13, 2024 04:29
@renovate renovate bot force-pushed the renovate/node-20.x branch 3 times, most recently from 7032db4 to a1ddb70 Compare May 20, 2024 06:10
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from cf73040 to cb16500 Compare June 10, 2024 06:17
@renovate renovate bot force-pushed the renovate/node-20.x branch 4 times, most recently from 7651fe6 to ba5482a Compare June 21, 2024 13:15
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 1a4cc0d to 31476aa Compare July 1, 2024 04:56
@renovate renovate bot force-pushed the renovate/node-20.x branch from 31476aa to c8322fd Compare July 3, 2024 11:23
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from bab3952 to 6dab7de Compare July 15, 2024 04:41
@renovate renovate bot force-pushed the renovate/node-20.x branch from 6dab7de to 39830c4 Compare July 24, 2024 14:54
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 3f63989 to 427b831 Compare September 4, 2024 16:58
@renovate renovate bot force-pushed the renovate/node-20.x branch from 427b831 to b948876 Compare September 16, 2024 15:27
@renovate renovate bot changed the title chore(deps): update dependency node to v20 chore(deps): update dependency node to v20 - autoclosed Sep 19, 2024
@renovate renovate bot closed this Sep 19, 2024
@renovate renovate bot deleted the renovate/node-20.x branch September 19, 2024 21:52
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.

0 participants