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 ^20.11.0 #50

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Feb 3, 2024

Mend Renovate

This PR contains the following updates:

Package Type Update Change
node (source) engines minor ^20 -> ^20.11.0

Release Notes

nodejs/node (node)

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 - "every weekend" in timezone Asia/Shanghai, 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 this update 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.

Copy link

github-actions bot commented Feb 3, 2024

Eslint Check Result

✅ 0 error 0 warning.

Typescript Check Result

❌ 3 errors.

Details

Scope: 3 of 4 workspace projects
packages/parse lint:ts$ tsc --noEmit
packages/preview lint:ts$ tsc --noEmit
packages/parse lint:ts: Done
packages/preview lint:ts: Done
packages/cli lint:ts$ tsc --noEmit
packages/cli lint:ts: src/parse.ts(7,55): error TS2307: Cannot find module 'svg-to-component-parse' or its corresponding type declarations.
packages/cli lint:ts: src/parse.ts(28,24): error TS7006: Parameter 'v' implicitly has an 'any' type.
packages/cli lint:ts: src/preview.ts(18,45): error TS2307: Cannot find module 'svg-to-component-preview' or its corresponding type declarations.
packages/cli lint:ts: Failed
/home/runner/work/svg-to-component/svg-to-component/packages/cli:
 ERR_PNPM_RECURSIVE_RUN_FIRST_FAIL  [email protected] lint:ts: `tsc --noEmit`
Exit status 2

UnitTest Check Result

✅ passed.


Commented by Action check pull request #50, last updated on Tue Feb 6 18:02:01 CST 2024.

@renovate renovate bot force-pushed the renovate/node-20.x branch from 41db687 to b7fc1a1 Compare February 6, 2024 10:00
@taoliujun taoliujun closed this Feb 7, 2024
Copy link
Author

renovate bot commented Feb 7, 2024

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update (^20.11.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 February 7, 2024 05:15
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