Skip to content
This repository has been archived by the owner on Nov 13, 2024. It is now read-only.

Update dependency nodejs/node to v22 - autoclosed #99

Closed
wants to merge 1 commit into from
Closed

Update dependency nodejs/node to v22 - autoclosed #99

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 24, 2024 •
edited
Loading

This PR contains the following updates:

Package Update Change
nodejs/node major 20.18.0 -> 22.9.0

Release Notes

nodejs/node (nodejs/node)

v22.9.0: 2024-09-17, Version 22.9.0 (Current), @​RafaelGSS

Compare Source

New API to retrieve execution Stack Trace

A new API getCallSite has been introduced to the util module. This API allows users
to retrieve the stacktrace of the current execution. Example:

const util = require('node:util');

function exampleFunction() {
  const callSites = util.getCallSite();

  console.log('Call Sites:');
  callSites.forEach((callSite, index) => {
    console.log(`CallSite ${index + 1}:`);
    console.log(`Function Name: ${callSite.functionName}`);
    console.log(`Script Name: ${callSite.scriptName}`);
    console.log(`Line Number: ${callSite.lineNumber}`);
    console.log(`Column Number: ${callSite.column}`);
  });
  // CallSite 1:
  // Function Name: exampleFunction
  // Script Name: /home/example.js
  // Line Number: 5
  // Column Number: 26

  // CallSite 2:
  // Function Name: anotherFunction
  // Script Name: /home/example.js
  // Line Number: 22
  // Column Number: 3

  // ...
}

// A function to simulate another stack layer
function anotherFunction() {
  exampleFunction();
}

anotherFunction();

Thanks to Rafael Gonzaga for making this work on #​54380.

Disable V8 Maglev

We have seen several crashes/unexpected JS behaviors with maglev on v22
(which ships V8 v12.4). The bugs lie in the codegen so it would be difficult for
users to work around them or even figure out where the bugs are coming from.
Some bugs are fixed in the upstream while some others probably remain.

As v22 will get stuck with V8 v12.4 as LTS, it will be increasingly difficult to
backport patches for them even if the bugs are fixed. So disable it by default
on v22 to reduce the churn and troubles for users.

Thanks to Joyee Cheung for making this work on #​54384

Exposes X509_V_FLAG_PARTIAL_CHAIN to tls.createSecureContext

This releases introduces a new option to the API tls.createSecureContext. For
now on users can use tls.createSecureContext({ allowPartialTrustChain: true })
to treat intermediate (non-self-signed) certificates in the trust CA certificate
list as trusted.

Thanks to Anna Henningsen for making this work on #​54790

Other Notable Changes
  • [5c9599af5a] - src: create handle scope in FastInternalModuleStat (Joyee Cheung) #​54384
  • [e2307d87e8] - (SEMVER-MINOR) stream: relocate the status checking code in the onwritecomplete (YoonSoo_Shin) #​54032
Deprecations
  • [8433032948] - repl: doc-deprecate instantiating node:repl classes without new (Aviv Keller) #​54842
  • [8c4c85cf31] - zlib: deprecate instantiating classes without new (Yagiz Nizipli) #​54708
Commits

v22.8.0: 2024-09-03, Version 22.8.0 (Current), @​RafaelGSS

Compare Source

New JS API for compile cache

This release adds a new API module.enableCompileCache() that can be used to enable on-disk code caching of all modules loaded after this API is called.
Previously this could only be enabled by the NODE_COMPILE_CACHE environment variable, so it could only set by end-users.
This API allows tooling and library authors to enable caching of their own code.
This is a built-in alternative to the v8-compile-cache/v8-compile-cache-lib packages,
but have better performance and supports ESM.

Thanks to Joyee Cheung for working on this.

New option for vm.createContext() to create a context with a freezable globalThis

Node.js implements a flavor of vm.createContext() and friends that creates a context without contextifying its global
object when vm.constants.DONT_CONTEXTIFY is used. This is suitable when users want to freeze the context
(impossible when the global is contextified i.e. has interceptors installed) or speed up the global access if they
don't need the interceptor behavior.

Thanks to Joyee Cheung for working on this.

Support for coverage thresholds

Node.js now supports requiring code coverage to meet a specific threshold before the process exits successfully.
To use this feature, you need to enable the --experimental-test-coverage flag.

You can set thresholds for the following types of coverage:

  • Branch coverage: Use --test-coverage-branches=<threshold>
  • Function coverage: Use --test-coverage-functions=<threshold>
  • Line coverage: Use --test-coverage-lines=<threshold>

<threshold> should be an integer between 0 and 100. If an invalid value is provided, a TypeError will be thrown.

If the code coverage fails to meet the specified thresholds for any category, the process will exit with code 1.

For instance, to enforce a minimum of 80% line coverage and 60% branch coverage, you can run:

$ node --experimental-test-coverage --test-coverage-lines=80 --test-coverage-branches=60 example.js

Thanks Aviv Keller for working on this.

Other Notable Changes
  • [1f2cc2fa47] - (SEMVER-MINOR) src,lib: add performance.uvMetricsInfo (Rafael Gonzaga) #​54413
  • [1e01bdc0d0] - (SEMVER-MINOR) net: exclude ipv6 loopback addresses from server.listen (Giovanni Bucci) #​54264
  • [97fa075c2e] - (SEMVER-MINOR) test_runner: support running tests in process (Colin Ihrig) #​53927
  • [858b583c88] - (SEMVER-MINOR) test_runner: defer inheriting hooks until run() (Colin Ihrig) #​53927
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 is behind base branch, 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 was generated by Mend Renovate. View the repository job log.

@renovate renovate bot requested a review from a team as a code owner April 24, 2024 19:57
@renovate renovate bot force-pushed the renovate/nodejs-node-22.x branch 3 times, most recently from ea77996 to 4030df9 Compare May 7, 2024 19:00
@renovate renovate bot force-pushed the renovate/nodejs-node-22.x branch 3 times, most recently from 4788313 to 25447bf Compare May 16, 2024 00:17
@renovate renovate bot force-pushed the renovate/nodejs-node-22.x branch 3 times, most recently from 4446143 to 211d63b Compare June 3, 2024 06:52
@renovate renovate bot force-pushed the renovate/nodejs-node-22.x branch 2 times, most recently from db3b95c to 78042df Compare June 11, 2024 19:51
@renovate renovate bot force-pushed the renovate/nodejs-node-22.x branch from 78042df to d3149b2 Compare June 21, 2024 05:30
@renovate renovate bot force-pushed the renovate/nodejs-node-22.x branch 2 times, most recently from 892d065 to e14c79f Compare July 2, 2024 11:38
@renovate renovate bot force-pushed the renovate/nodejs-node-22.x branch 3 times, most recently from bc250fc to c8a2a40 Compare July 9, 2024 22:17
@renovate renovate bot force-pushed the renovate/nodejs-node-22.x branch 2 times, most recently from f2036ce to 1b17aa9 Compare July 20, 2024 23:53
@renovate renovate bot force-pushed the renovate/nodejs-node-22.x branch 2 times, most recently from bf630dc to e99bd6f Compare July 25, 2024 13:03
@renovate renovate bot force-pushed the renovate/nodejs-node-22.x branch from e99bd6f to 024918a Compare August 9, 2024 05:50
@renovate renovate bot force-pushed the renovate/nodejs-node-22.x branch 5 times, most recently from e0dea0e to d23aa65 Compare August 22, 2024 15:54
@renovate renovate bot force-pushed the renovate/nodejs-node-22.x branch from d23aa65 to dbeaf0b Compare September 2, 2024 06:54
@renovate renovate bot force-pushed the renovate/nodejs-node-22.x branch from dbeaf0b to 0de4f56 Compare September 3, 2024 15:16
@renovate renovate bot force-pushed the renovate/nodejs-node-22.x branch 2 times, most recently from 50a811a to 2120fbc Compare September 18, 2024 01:49
@renovate renovate bot force-pushed the renovate/nodejs-node-22.x branch from 2120fbc to 92714ff Compare October 7, 2024 19:59
@renovate renovate bot force-pushed the renovate/nodejs-node-22.x branch from 92714ff to ec3ce78 Compare October 8, 2024 21:07
@sonarqubecloud SonarQubeCloud
Copy link

sonarqubecloud bot commented Oct 8, 2024

Quality Gate Passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

@renovate renovate bot changed the title Update dependency nodejs/node to v22 Update dependency nodejs/node to v22 - autoclosed Oct 16, 2024
@renovate renovate bot closed this Oct 16, 2024
@renovate renovate bot deleted the renovate/nodejs-node-22.x branch October 16, 2024 17:35
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Reviewers
No reviews
Assignees
No one assigned
Labels
dependencies
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants