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

Update Node.js to v20.14.0 #522

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Update Node.js to v20.14.0 #522

wants to merge 2 commits into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 28, 2024 •
edited
Loading

Mend Renovate

This PR contains the following updates:

Package Type Update Change Pending Age Adoption Passing Confidence
node final minor 20.11.1 -> 20.14.0 20.15.1 (+1) age adoption passing confidence
node minor 20.11.1 -> 20.14.0 20.15.1 (+1) age adoption passing confidence
@types/node (source) devDependencies minor 20.10.8 -> 20.14.9 20.14.10 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 - "after 8pm every weekday,before 5am every weekday,every weekend" (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.

🔕 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.

jhaerDfine
jhaerDfine reviewed May 29, 2024
View reviewed changes
Copy link
Contributor

@jhaerDfine jhaerDfine left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

problematic upgrade

@renovate renovate bot force-pushed the renovate/node-20.x branch 5 times, most recently from 62ddc3c to 0320181 Compare June 5, 2024 16:40
@renovate renovate bot changed the title Update Node.js to v20.13.1 Update Node.js to v20.14.0 Jun 5, 2024
@renovate renovate bot changed the title Update Node.js to v20.14.0 Update Node.js to v20.13.1 Jun 6, 2024
@renovate renovate bot force-pushed the renovate/node-20.x branch 4 times, most recently from 639bd6d to d5d7626 Compare June 12, 2024 07:24
@renovate renovate bot changed the title Update Node.js to v20.13.1 Update Node.js to v20.14.0 Jun 12, 2024
@renovate renovate bot force-pushed the renovate/node-20.x branch 4 times, most recently from 105d14e to 3dfced7 Compare June 15, 2024 08:46
@renovate renovate bot changed the title Update Node.js to v20.14.0 Update Node.js to v20.13.1 Jun 15, 2024
@renovate renovate bot force-pushed the renovate/node-20.x branch 5 times, most recently from caf3979 to 36b6294 Compare June 19, 2024 07:59
@renovate renovate bot force-pushed the renovate/node-20.x branch 5 times, most recently from 0a1890b to 5c073c6 Compare June 27, 2024 05:35
@renovate renovate bot force-pushed the renovate/node-20.x branch 4 times, most recently from 174b040 to 1416ca1 Compare July 4, 2024 05:32
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from fa15d43 to 5e38a18 Compare July 6, 2024 11:47
@renovate renovate bot changed the title Update Node.js to v20.13.1 Update Node.js to v20.14.0 Jul 6, 2024
@renovate renovate bot force-pushed the renovate/node-20.x branch 2 times, most recently from 8c368e6 to f73b645 Compare July 10, 2024 07:29
@renovate Renovate
Copy link
Contributor Author

renovate bot commented Jul 19, 2024

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@jhaerDfine jhaerDfine jhaerDfine left review comments

Assignees
No one assigned
Labels
dependencies
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@jhaerDfine @aliabdoli77