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 v20 #115

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 27, 2023

This PR contains the following updates:

Package Type Update Change
node (source) volta major 18.20.4 -> 20.17.0

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 - "after 10pm every weekend,before 5am every weekend" in timezone Asia/Tokyo, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

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.

@renovate
Copy link
Contributor Author

renovate bot commented Oct 27, 2023

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pnpm-lock.yaml
 ERR_PNPM_UNSUPPORTED_ENGINE  Unsupported environment (bad pnpm and/or Node.js version)

Your Node version is incompatible with "/tmp/renovate/repos/github/astronomy-club-at-nitic/notion-budget-bot".

Expected version: >=18.0.0 <19
Got: v20.13.0

This is happening because the package's manifest has an engines.node field specified.
To fix this issue, install the required Node version.

@renovate renovate bot force-pushed the renovate/node-20.x branch 3 times, most recently from 2b85d1a to 50d2217 Compare November 3, 2023 22:38
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 233604d to b063125 Compare November 22, 2023 15:25
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 01f2123 to 13f5d3a Compare December 1, 2023 19:00
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from a225f75 to 289ff50 Compare December 9, 2023 16:20
@renovate renovate bot force-pushed the renovate/node-20.x branch 3 times, most recently from d671642 to fe45e6f Compare January 12, 2024 19:03
@renovate renovate bot force-pushed the renovate/node-20.x branch 4 times, most recently from 4319dd2 to 773be8a Compare February 2, 2024 18:10
@renovate renovate bot force-pushed the renovate/node-20.x branch 3 times, most recently from 7943951 to 69a94ee Compare February 16, 2024 18:03
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from a167de3 to e97c355 Compare February 17, 2024 00:10
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 2760f07 to cd87c27 Compare April 19, 2024 18:24
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 2a05d69 to cf26334 Compare May 9, 2024 15:38
Copy link
Contributor Author

renovate bot commented May 9, 2024

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pnpm-lock.yaml
 ERR_PNPM_UNSUPPORTED_ENGINE  Unsupported environment (bad pnpm and/or Node.js version)

Your Node version is incompatible with "/tmp/renovate/repos/github/astronomy-club-at-nitic/notion-budget-bot".

Expected version: >=18.0.0 <19
Got: v20.17.0

This is happening because the package's manifest has an engines.node field specified.
To fix this issue, install the required Node version.

@renovate renovate bot force-pushed the renovate/node-20.x branch 3 times, most recently from 6c773b9 to ed21e40 Compare May 11, 2024 00:55
@renovate renovate bot force-pushed the renovate/node-20.x branch 3 times, most recently from bed7b3c to 5f69772 Compare May 24, 2024 22:06
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 37ef40a to 29f31c8 Compare May 31, 2024 20:22
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from c8f80b4 to 62f1e9a Compare June 14, 2024 18:30
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 2b948c2 to adef15a Compare June 21, 2024 18:56
@renovate renovate bot force-pushed the renovate/node-20.x branch 3 times, most recently from c2c5ef6 to 07b16bd Compare July 12, 2024 21:51
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 1f2f6f5 to 92ab515 Compare July 26, 2024 18:51
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 0e7d455 to 9213627 Compare August 16, 2024 18:28
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 043c743 to 2b608ee Compare August 23, 2024 20:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants