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

Update Node.js to v20 #823

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

Update Node.js to v20 #823

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 22, 2023

Mend Renovate

This PR contains the following updates:

Package Type Update Change Age Adoption Passing Confidence
node final major 18-slim -> 20-slim age adoption passing confidence
node (source) major 16.20.2 -> 20.14.0 age adoption passing confidence
@types/node (source) devDependencies major 14.18.63 -> 20.12.13 age adoption passing confidence
@types/node (source) dependencies major 16.18.96 -> 20.12.13 age adoption passing confidence

Release Notes

nodejs/node (node)

v20.14.0: 2024-05-28, Version 20.14.0 'Iron' (LTS), @​marco-ippolito

Compare Source

Notable Changes
Commits

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: 2024-05-07, Version 20.13.0 'Iron' (LTS), @​marco-ippolito

Compare Source

2024-05-07, Version 20.13.0 'Iron' (LTS), @​marco-ippolito

buffer: improve base64 and base64url performance

The performance of the base64 and base64url encoding and decoding functions has been improved significantly.

Contributed by Yagiz Nizipli in #​52428

crypto: deprecate implicitly shortened GCM tags

This release, introduces a doc-only deprecation of using GCM authentication tags that are shorter than the cipher's block size, unless the user specified the authTagLength option.

Contributed by Tobias Nießen in #​52345

events,doc: mark CustomEvent as stable

From this release CustomEvent has been marked stable.

Contributed by Daeyeon Jeong in #​52618

fs: add stacktrace to fs/promises

Sync functions in fs throwed an error with a stacktrace which is helpful for debugging. But functions in fs/promises throwed an error without a stacktrace. This commit adds stacktraces by calling Error.captureStacktrace and re-throwing the error.

Contributed by 翠 / green in #​49849

report: add --report-exclude-network option

New option --report-exclude-network, also available as report.excludeNetwork, enables the user to exclude networking interfaces in their diagnostic report. On some systems, this can cause the report to take minutes to generate so this option can be used to optimize that.

Contributed by Ethan Arrowood in #​51645

src: add uv_get_available_memory to report and process

From this release it is possible to get the available memory in the system by calling process.getAvailableMemory().

Contributed by theanarkh #​52023

stream: support typed arrays

This commit adds support for typed arrays in streams.

Contributed by IlyasShabi #​51866

util: support array of formats in util.styleText

It is now possible to pass an array of format strings to util.styleText to apply multiple formats to the same text.

console.log(util.styleText(['underline', 'italic'], 'My italic underlined message'));

Contributed by Marco Ippolito in #​52040

v8: implement v8.queryObjects() for memory leak regression testing

This is similar to the queryObjects() console API provided by the Chromium DevTools console. It can be used to search for objects that have the matching constructor on its prototype chain in the heap after a full garbage collection, which can be useful for memory leak regression tests.
To avoid surprising results, users should avoid using this API on constructors whose implementation they don't control, or on constructors that can be invoked by other parties in the application.

To avoid accidental leaks, this API does not return raw references to the objects found. By default, it returns the count of the objects found. If options.format is 'summary', it returns an array containing brief string representations for each object. The visibility provided in this API is similar to what the heap snapshot provides, while users can save the cost of serialization and parsing and directly filer the target objects during the search.

We have been using this API internally for the test suite, which has been more stable than any other leak regression testing strategies in the CI. With a public implementation we can now use the public API instead.

const { queryObjects } = require('node:v8');
class A { foo = 'bar'; }
console.log(queryObjects(A)); // 0
let a = new A();
console.log(queryObjects(A)); // 1
// [ "A { foo: 'bar' }" ]
console.log(queryObjects(A, { format: 'summary' }));

// Release the object.
a = null;
// Search again. queryObjects() includes a full garbage collection
// so a should disappear.
console.log(queryObjects(A)); // 0

class B extends A { bar = 'qux'; }
// The child class B's prototype has A's prototype on its prototype chain
// so the prototype object shows up too.
console.log(queryObjects(A, { format: 'summary' })); // [ A {}' ]

Contributed by Joyee Cheung in #​51927

watch: mark as stable

From this release Watch Mode is considered stable.
When in watch mode, changes in the watched files cause the Node.js process to restart.

Contributed by Moshe Atlow in #​52074

Other 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 changed the title Update Node.js to v20 Update Node.js to v20 - autoclosed Oct 20, 2023
@renovate renovate bot closed this Oct 20, 2023
@renovate renovate bot deleted the renovate/node-20.x branch October 20, 2023 01:38
@renovate renovate bot changed the title Update Node.js to v20 - autoclosed Update Node.js to v20 Oct 24, 2023
@renovate renovate bot reopened this Oct 24, 2023
@renovate renovate bot restored the renovate/node-20.x branch October 24, 2023 01:49
@renovate renovate bot changed the title Update Node.js to v20 Update dependency @types/node to v20 Oct 24, 2023
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 08e65c0 to 7aacf03 Compare October 24, 2023 15:40
@renovate renovate bot changed the title Update dependency @types/node to v20 Update dependency node to v20 Oct 24, 2023
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 7367c67 to 96785c5 Compare October 31, 2023 11:58
@renovate renovate bot force-pushed the renovate/node-20.x branch 6 times, most recently from 1123a06 to fc9fadf Compare November 23, 2023 21:58
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 3ca08ff to 07ff1a5 Compare November 29, 2023 22:10
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from e2d6dac to 94dbe4a Compare December 3, 2023 12:38
@renovate renovate bot changed the title Update dependency node to v20 Update Node.js to v20 Dec 3, 2023
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 78ce576 to 23f7ba7 Compare December 7, 2023 08:16
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 5985829 to 684791f Compare January 9, 2024 20:01
@renovate renovate bot force-pushed the renovate/node-20.x branch 4 times, most recently from e571203 to b656bd9 Compare March 19, 2024 13:04
@renovate renovate bot force-pushed the renovate/node-20.x branch 3 times, most recently from 2ccfd14 to c098322 Compare March 30, 2024 06:38
@renovate renovate bot force-pushed the renovate/node-20.x branch 10 times, most recently from 772f42e to 46cd50f Compare April 9, 2024 17:28
@renovate renovate bot force-pushed the renovate/node-20.x branch 3 times, most recently from 0f2bfe7 to 2f9925d Compare April 10, 2024 23:32
@renovate renovate bot force-pushed the renovate/node-20.x branch 5 times, most recently from 4b0dc3c to aa26ef0 Compare May 8, 2024 12:36
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from dab8ca3 to 07b0a13 Compare May 14, 2024 08:32
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.

None yet

0 participants