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.17.0 #32

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 23, 2024

This PR contains the following updates:

Package Update Change
node (source) minor 20.10.0 -> 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


Configuration

📅 Schedule: Branch creation - "after 10:00 before 19:00 every weekday except after 13:00 before 14:00" in timezone Europe/Berlin, 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.

@renovate renovate bot requested a review from prisis as a code owner May 23, 2024 13:01
Copy link
Contributor

github-actions bot commented May 23, 2024

Thank you for following the naming conventions! 🙏

@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 7756ba2 to 10be22a Compare May 23, 2024 13:33
@renovate renovate bot force-pushed the renovate/node-20.x branch 6 times, most recently from 8ba79da to 906e653 Compare May 28, 2024 20:16
@renovate renovate bot changed the title chore(deps): update dependency node to v20.13.1 chore(deps): update dependency node to v20.14.0 May 28, 2024
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 5a3cd8d to 91ba939 Compare June 3, 2024 05:16
@renovate renovate bot force-pushed the renovate/node-20.x branch 14 times, most recently from c3f7f43 to ef9e293 Compare June 18, 2024 05:59
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 3ea9795 to 47dd30b Compare June 19, 2024 20:59
@renovate renovate bot force-pushed the renovate/node-20.x branch from 47dd30b to 10a72e7 Compare June 20, 2024 17:36
@renovate renovate bot changed the title chore(deps): update dependency node to v20.14.0 chore(deps): update dependency node to v20.15.0 Jun 20, 2024
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 79866bf to 4865484 Compare July 8, 2024 18:27
@renovate renovate bot changed the title chore(deps): update dependency node to v20.15.0 chore(deps): update dependency node to v20.15.1 Jul 8, 2024
@renovate renovate bot force-pushed the renovate/node-20.x branch from 4865484 to 5423959 Compare July 24, 2024 13:01
@renovate renovate bot changed the title chore(deps): update dependency node to v20.15.1 chore(deps): update dependency node to v20.16.0 Jul 24, 2024
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 6b7babc to 0e3cd2a Compare August 12, 2024 08:18
@renovate renovate bot force-pushed the renovate/node-20.x branch from 0e3cd2a to 8a8d807 Compare August 19, 2024 10:35
@renovate renovate bot force-pushed the renovate/node-20.x branch from 8a8d807 to 999a617 Compare August 21, 2024 17:56
@renovate renovate bot changed the title chore(deps): update dependency node to v20.16.0 chore(deps): update dependency node to v20.17.0 Aug 21, 2024
@github-actions github-actions bot added the Stale label Sep 19, 2024
@github-actions github-actions bot closed this Sep 26, 2024
Copy link
Contributor Author

renovate bot commented Sep 26, 2024

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update (20.17.0). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps array of your Renovate config.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

@renovate renovate bot deleted the renovate/node-20.x branch September 26, 2024 00:12
Copy link
Contributor

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using our GitHub Discussions tab for questions.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 26, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants