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.

Sign up for GitHub

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

Jump to bottom

chore(deps): update dependency node to v20 #2723

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

chore(deps): update dependency node to v20 #2723

wants to merge 1 commit into from
+2 −2

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 24, 2023 •
edited

Mend Renovate

This PR contains the following updates:

Package Type Update Change Age Adoption Passing Confidence
node (source) major 18.17.1 -> 20.13.1 age adoption passing confidence
@types/node (source) devDependencies major 18.17.17 -> 20.12.12 age adoption passing confidence

Release Notes

nodejs/node (node)

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

v20.7.0: 2023-09-18, Version 20.7.0 (Current), @​UlisesGascon

Compare Source

Notable Changes
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 has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot force-pushed the renovate/node-20.x branch 3 times, most recently from 6d5ed97 to 058b06b Compare October 25, 2023 18:57
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 6da5194 to d22e653 Compare November 4, 2023 07:10
@renovate renovate bot force-pushed the renovate/node-20.x branch 3 times, most recently from ea0711a to 419cc15 Compare November 8, 2023 00:22
@renovate renovate bot force-pushed the renovate/node-20.x branch 9 times, most recently from 9019f3a to 7fffb77 Compare November 24, 2023 01:18
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 422655f to 696e593 Compare November 29, 2023 20:15
@renovate renovate bot force-pushed the renovate/node-20.x branch 3 times, most recently from ef01c36 to 91093c8 Compare December 7, 2023 07:28
@renovate renovate bot force-pushed the renovate/node-20.x branch 5 times, most recently from b7b62c0 to 7f84d42 Compare January 11, 2024 08:28
@renovate renovate bot force-pushed the renovate/node-20.x branch 3 times, most recently from 48092d5 to 09c0572 Compare February 15, 2024 17:02
@renovate renovate bot force-pushed the renovate/node-20.x branch 5 times, most recently from 8544b26 to 8c45b83 Compare February 29, 2024 17:54
@renovate renovate bot force-pushed the renovate/node-20.x branch 3 times, most recently from d25d830 to fbe9795 Compare March 13, 2024 13:42
@renovate renovate bot force-pushed the renovate/node-20.x branch 3 times, most recently from 3491b5b to e62b18f Compare March 19, 2024 13:43
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from c0b6e4c to e006870 Compare March 30, 2024 07:07
@renovate renovate bot force-pushed the renovate/node-20.x branch 4 times, most recently from 1a8ff2f to b50e315 Compare April 7, 2024 05:46
@renovate Renovate
Copy link
Contributor Author

renovate bot commented Apr 10, 2024 •
edited

⚠ 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: package-lock.json
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: [email protected]
npm error Found: [email protected]
npm error node_modules/eslint
npm error   dev eslint@"9.2.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer eslint@"^8.56.0" from @typescript-eslint/[email protected]
npm error node_modules/@typescript-eslint/parser
npm error   dev @typescript-eslint/parser@"7.8.0" from the root project
npm error   peer @typescript-eslint/parser@"^7.0.0" from @typescript-eslint/[email protected]
npm error   node_modules/@typescript-eslint/eslint-plugin
npm error     dev @typescript-eslint/eslint-plugin@"7.8.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2024-05-06T21_38_27_718Z-eresolve-report.txt

npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-05-06T21_38_27_718Z-debug-0.log

@renovate renovate bot force-pushed the renovate/node-20.x branch 3 times, most recently from dd113ed to 471cb29 Compare May 6, 2024 21:38
@renovate Renovate
Copy link
Contributor Author

renovate bot commented May 10, 2024 •
edited

⚠️ 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: package-lock.json
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: [email protected]
npm error Found: [email protected]
npm error node_modules/eslint
npm error   dev eslint@"9.2.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer eslint@"^8.56.0" from @typescript-eslint/[email protected]
npm error node_modules/@typescript-eslint/parser
npm error   dev @typescript-eslint/parser@"7.8.0" from the root project
npm error   peer @typescript-eslint/parser@"^7.0.0" from @typescript-eslint/[email protected]
npm error   node_modules/@typescript-eslint/eslint-plugin
npm error     dev @typescript-eslint/eslint-plugin@"7.8.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2024-05-22T23_55_22_948Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-05-22T23_55_22_948Z-debug-0.log

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
0 participants