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.18 #202

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 27, 2024

This PR contains the following updates:

Package Type Update Change
node (source) engines minor 20.11 -> 20.18

Release Notes

nodejs/node (node)

v20.18.1: 2024-11-20, Version 20.18.1 'Iron' (LTS), @​marco-ippolito

Compare Source

Notable Changes
Commits

v20.18.0: 2024-10-03, Version 20.18.0 'Iron' (LTS), @​targos

Compare Source

Notable Changes
Experimental Network Inspection Support in Node.js

This update introduces the initial support for network inspection in Node.js.
Currently, this is an experimental feature, so you need to enable it using the --experimental-network-inspection flag.
With this feature enabled, you can inspect network activities occurring within a JavaScript application.

To use network inspection, start your Node.js application with the following command:

$ node --inspect-wait --experimental-network-inspection index.js

Please note that the network inspection capabilities are in active development.
We are actively working on enhancing this feature and will continue to expand its functionality in future updates.

Contributed by Kohei Ueno in #​53593 and #​54246

Exposes X509_V_FLAG_PARTIAL_CHAIN to tls.createSecureContext

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

Contributed by Anna Henningsen in #​54790

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.

Contributed by Joyee Cheung in #​54394

Deprecations
  • [64aa31f6e5] - repl: doc-deprecate instantiating node:repl classes without new (Aviv Keller) #​54842
  • [4c52ee3d7f] - zlib: deprecate instantiating classes without new (Yagiz Nizipli) #​54708
Other Notable Changes
Commits

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

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.

Copy link

Quality Gate Passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud

Copy link

codecov bot commented Mar 27, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 28.57%. Comparing base (4fab673) to head (85353de).

Additional details and impacted files
@@            Coverage Diff            @@
##               main     #202   +/-   ##
=========================================
  Coverage     28.57%   28.57%           
  Complexity       18       18           
=========================================
  Files            10       10           
  Lines           175      175           
  Branches         17       17           
=========================================
  Hits             50       50           
  Misses          121      121           
  Partials          4        4           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@renovate renovate bot force-pushed the renovate/node-20.x branch from f3f51a6 to 13d8015 Compare May 8, 2024 00:07
@renovate renovate bot changed the title chore(deps): update node.js to 20.12 chore(deps): update node.js to 20.13 May 8, 2024
@renovate renovate bot force-pushed the renovate/node-20.x branch from 13d8015 to d494745 Compare May 29, 2024 00:19
@renovate renovate bot changed the title chore(deps): update node.js to 20.13 chore(deps): update node.js to 20.14 May 29, 2024
@renovate renovate bot force-pushed the renovate/node-20.x branch from d494745 to ea38ccf Compare June 21, 2024 01:22
@renovate renovate bot changed the title chore(deps): update node.js to 20.14 chore(deps): update node.js to 20.15 Jun 21, 2024
Copy link

@renovate renovate bot force-pushed the renovate/node-20.x branch from ea38ccf to 5ac1f8e Compare July 25, 2024 00:41
@renovate renovate bot changed the title chore(deps): update node.js to 20.15 chore(deps): update node.js to 20.16 Jul 25, 2024
@renovate renovate bot force-pushed the renovate/node-20.x branch from 5ac1f8e to 85353de Compare August 22, 2024 00:11
@renovate renovate bot changed the title chore(deps): update node.js to 20.16 chore(deps): update node.js to 20.17 Aug 22, 2024
Copy link

@renovate renovate bot force-pushed the renovate/node-20.x branch from 85353de to 6d009c2 Compare October 4, 2024 01:48
@renovate renovate bot changed the title chore(deps): update node.js to 20.17 chore(deps): update node.js to 20.18 Oct 4, 2024
Copy link

sonarqubecloud bot commented Oct 4, 2024

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants