Skip to content
This repository was archived by the owner on Jan 24, 2024. It is now read-only.

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Oct 27, 2023

Mend Renovate

This PR contains the following updates:

Package Type Update Change Pending Age Adoption Passing Confidence
node major 18.18.2 -> 20.11.0 age adoption passing confidence
@types/node (source) devDependencies minor 20.8.10 -> 20.11.5 20.11.6 age adoption passing confidence

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/Tokyo, 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 added the dependencies Pull requests that update a dependency file label Oct 27, 2023
@renovate renovate bot force-pushed the renovate/node-20.x branch from 7b38ccc to c4299c6 Compare November 10, 2023 21:33
@renovate renovate bot force-pushed the renovate/node-20.x branch 5 times, most recently from ccae21b to 45ed7c5 Compare November 25, 2023 01:53
@renovate renovate bot force-pushed the renovate/node-20.x branch 4 times, most recently from 8fe6f82 to 5d80fbe Compare December 2, 2023 19:44
@renovate renovate bot force-pushed the renovate/node-20.x branch 3 times, most recently from a02c78f to 3415957 Compare December 10, 2023 11:09
@renovate renovate bot force-pushed the renovate/node-20.x branch from 3415957 to a4e0e0d Compare December 20, 2023 21:38
@renovate renovate bot force-pushed the renovate/node-20.x branch from a4e0e0d to 0166e86 Compare January 2, 2024 00:37
@renovate renovate bot force-pushed the renovate/node-20.x branch 4 times, most recently from 51a7fc4 to 51ff10b Compare January 14, 2024 07:25
@renovate renovate bot force-pushed the renovate/node-20.x branch 4 times, most recently from fef3c58 to cdf8170 Compare January 19, 2024 10:39
@renovate renovate bot force-pushed the renovate/node-20.x branch from cdf8170 to 8891cb5 Compare January 20, 2024 10:46
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants