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 all node.js updates (major) #3319

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 4, 2023

This PR contains the following updates:

Package Change Age Adoption Passing Confidence Type Update
@types/node (source) ^16.18.48 -> ^20.0.0 age adoption passing confidence devDependencies major
@types/node (source) ^18.17.14 -> ^20.0.0 age adoption passing confidence dependencies major
@vercel/node (source) ^2.15.10 -> ^3.0.0 age adoption passing confidence devDependencies major
node (source) 18 -> 20 age adoption passing confidence major

Release Notes

vercel/vercel (@​vercel/node)

v3.2.10

Compare Source

Patch Changes

v3.2.9

Compare Source

Patch Changes

v3.2.8

Compare Source

Patch Changes

v3.2.7

Compare Source

Patch Changes

v3.2.6

Compare Source

Patch Changes

v3.2.5

Compare Source

Patch Changes

v3.2.4

Compare Source

Patch Changes

v3.2.3

Compare Source

Patch Changes

v3.2.2

Compare Source

Patch Changes

v3.2.1

Compare Source

Patch Changes

v3.2.0

Compare Source

Minor Changes
  • Ignore shouldAddHelpers when exporting a server to match production (#​11738)
Patch Changes
  • Update undici dep to address vulnerabilities (#​11749)

v3.1.7

Compare Source

Patch Changes

v3.1.6

Compare Source

Patch Changes

v3.1.5

Compare Source

Patch Changes

v3.1.4

Compare Source

Patch Changes

v3.1.3

Compare Source

Patch Changes

v3.1.2

Compare Source

Patch Changes

v3.1.1

Compare Source

Patch Changes

v3.1.0

Compare Source

Minor Changes
  • Make waitUntil consistent for Node.js & Edge (#​11553)

v3.0.28

Compare Source

Patch Changes

v3.0.27

Compare Source

Patch Changes

v3.0.26

Compare Source

Patch Changes

v3.0.25

Compare Source

Patch Changes

v3.0.24

Compare Source

Patch Changes

v3.0.23

Compare Source

Patch Changes

v3.0.22

Compare Source

Patch Changes

v3.0.21

Compare Source

Patch Changes

v3.0.20

Compare Source

Patch Changes

v3.0.19

Compare Source

Patch Changes

v3.0.18

Compare Source

Patch Changes

v3.0.17

Compare Source

Patch Changes

v3.0.16

Compare Source

Patch Changes

v3.0.15

Compare Source

Patch Changes
  • Await waitUntil promises to resolve before exiting (#​10915)

  • [next][node][redwood][remix] Bump @vercel/nft@0.26.1 (#​11009)

v3.0.14

Compare Source

Patch Changes

v3.0.13

Compare Source

Patch Changes

v3.0.12

Compare Source

Patch Changes

v3.0.11

Compare Source

Patch Changes

v3.0.10

Compare Source

Patch Changes

v3.0.9

Compare Source

Patch Changes
  • Replace usage of fetch with undici.request (#​10767)

v3.0.8

Compare Source

Patch Changes

v3.0.7

Compare Source

Patch Changes

v3.0.6

Compare Source

Patch Changes

v3.0.5

Compare Source

Patch Changes

v3.0.4

Compare Source

Patch Changes

v3.0.3

Compare Source

Patch Changes

v3.0.2

Compare Source

Patch Changes

v3.0.1

Compare Source

Patch Changes

v3.0.0

Compare Source

Major Changes
  • BREAKING CHANGE: Drop Node.js 14, bump minimum to Node.js 16 (#​10369)
Patch Changes
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-


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 becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • 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 added the 🤖 Type: Dependencies Dependency updates or something similar label Dec 4, 2023
Copy link

changeset-bot bot commented Dec 4, 2023

⚠️ No Changeset found

Latest commit: d7ee830

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Copy link
Contributor

github-actions bot commented Dec 4, 2023

Deploy preview for merchant-center-application-kit ready!

✅ Preview
https://merchant-center-application-dakr2jcq4-commercetools.vercel.app
https://appkit-sha-bb78867a4f672abbe419d55223593e59a488e766.commercetools.vercel.app
https://appkit-pr-3319.commercetools.vercel.app

Built with commit e665124.
This pull request is being automatically deployed with vercel-action

Copy link
Contributor

github-actions bot commented Dec 4, 2023

Deploy preview for application-kit-custom-views ready!

✅ Preview
https://application-kit-custom-views-1bop9dqqt-commercetools.vercel.app
https://appkit-cv-sha-5407855ee765d163bf7b43c1a466a5226ae87b39.commercetools.vercel.app
https://appkit-cv-pr-3319.commercetools.vercel.app

Built with commit b39abb1.
This pull request is being automatically deployed with vercel-action

@renovate renovate bot force-pushed the renovate/major-all-node.js-updates branch from 3f7639c to 5ca8953 Compare December 5, 2023 17:16
@renovate renovate bot force-pushed the renovate/major-all-node.js-updates branch from 5ca8953 to ea37b5f Compare December 7, 2023 13:01
@renovate renovate bot force-pushed the renovate/major-all-node.js-updates branch from ea37b5f to 39c5b31 Compare December 13, 2023 09:43
@renovate renovate bot force-pushed the renovate/major-all-node.js-updates branch from 39c5b31 to ab01176 Compare December 13, 2023 10:44
@renovate renovate bot force-pushed the renovate/major-all-node.js-updates branch from ab01176 to effe7bc Compare December 14, 2023 12:37
@renovate renovate bot force-pushed the renovate/major-all-node.js-updates branch from effe7bc to 1ecf9c2 Compare December 18, 2023 10:28
@CarlosCortizasCT
Copy link
Contributor

We recently agreed on keeping v18 for node, which is supported until May 2025.

Copy link

gitstream-cm bot commented Jun 18, 2024

This PR is missing a Jira ticket reference in the title or description.
Please add a Jira ticket reference to the title or description of this PR.

Copy link

gitstream-cm bot commented Jun 18, 2024

🥷 Code experts: emmenko

emmenko has most 🧠 knowledge in the files.

See details

.nvmrc

Knowledge based on git-blame:
emmenko: 100%

application-templates/starter-typescript/.nvmrc

Knowledge based on git-blame:

application-templates/starter/.nvmrc

Knowledge based on git-blame:

custom-views-templates/starter-typescript/.nvmrc

Knowledge based on git-blame:

custom-views-templates/starter/.nvmrc

Knowledge based on git-blame:

package.json

Knowledge based on git-blame:
emmenko: 58%

packages-backend/express/package.json

Knowledge based on git-blame:
emmenko: 66%

playground/package.json

Knowledge based on git-blame:
emmenko: 38%

pnpm-lock.yaml

Knowledge based on git-blame:
emmenko: 55%

To learn more about /:\ gitStream - Visit our Docs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant