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 #126

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 9, 2024

This PR contains the following updates:

Package Type Update Change Age Adoption Passing Confidence
node (source) minor 20.12.1 -> 20.17.0 age adoption passing confidence
@types/node (source) devDependencies minor 20.13.0 -> 20.16.2 age adoption passing confidence

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

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 was generated by Mend Renovate. View the repository job log.

Copy link

netlify bot commented Apr 9, 2024

Deploy Preview for my-nuxt-experiments ready!

Name Link
🔨 Latest commit 3237ea3
🔍 Latest deploy log https://app.netlify.com/sites/my-nuxt-experiments/deploys/66ce72143b0a820008bbf056
😎 Deploy Preview https://deploy-preview-126--my-nuxt-experiments.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

Copy link

netlify bot commented Apr 9, 2024

Deploy Preview for my-nuxt-starter-storybook ready!

Name Link
🔨 Latest commit 3237ea3
🔍 Latest deploy log https://app.netlify.com/sites/my-nuxt-starter-storybook/deploys/66ce7214207d0a0008cf3717
😎 Deploy Preview https://deploy-preview-126--my-nuxt-starter-storybook.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@renovate renovate bot changed the title chore(deps): update dependency @types/node to v20.12.6 chore(deps): update dependency @types/node to v20.12.7 Apr 9, 2024
@renovate renovate bot changed the title chore(deps): update dependency @types/node to v20.12.7 chore(deps): update dependency node to v20.12.2 Apr 10, 2024
@renovate renovate bot force-pushed the renovate/node-20.x branch 4 times, most recently from 2dd6a58 to afe38f1 Compare May 7, 2024 16:16
@renovate renovate bot changed the title chore(deps): update dependency node to v20.12.2 chore(deps): update dependency node to v20.13.0 May 7, 2024
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 1300dba to 0a677da Compare May 9, 2024 16:27
@renovate renovate bot changed the title chore(deps): update dependency node to v20.13.0 chore(deps): update dependency node to v20.13.1 May 9, 2024
@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 6 times, most recently from 273e2c3 to 922f695 Compare June 5, 2024 09:02
@renovate renovate bot force-pushed the renovate/node-20.x branch 5 times, most recently from c3f077b to 7a9a93f Compare June 20, 2024 19:37
@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 47ffd02 to eff5651 Compare June 25, 2024 22:15
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 9ec774b to be63f55 Compare July 8, 2024 19:40
@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 2 times, most recently from 4c6c07f to 6d292c4 Compare July 23, 2024 20:45
@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 f6541fd to f591b8f Compare August 2, 2024 21:52
@renovate renovate bot force-pushed the renovate/node-20.x branch 4 times, most recently from 6a519b8 to 6d3063e Compare August 21, 2024 20:35
@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
Copy link
Contributor Author

renovate bot commented Aug 29, 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 August 29, 2024 19:08
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.

1 participant