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.18.1 #139

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

Update Node.js to v20.18.1 #139

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 1, 2024

This PR contains the following updates:

Package Type Update Change Age Adoption Passing Confidence
node (source) minor 20.7.0 -> 20.18.1 age adoption passing confidence
@types/node (source) devDependencies minor 20.6.3 -> 20.17.12 age adoption passing confidence

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 - "* 0-3 * * 1" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

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 was generated by Mend Renovate. View the repository job log.

Copy link
Contributor Author

renovate bot commented Apr 1, 2024

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: decap-cms-app@3.0.12
npm error Found: react@18.2.0
npm error node_modules/react
npm error   react@"18.2.0" from the root project
npm error   peer react@">=16.8.0" from @dnd-kit/accessibility@3.0.1
npm error   node_modules/@dnd-kit/accessibility
npm error     @dnd-kit/accessibility@"^3.0.0" from @dnd-kit/core@6.0.8
npm error     node_modules/@dnd-kit/core
npm error       peer @dnd-kit/core@"^6.0.6" from @dnd-kit/modifiers@6.0.1
npm error       node_modules/@dnd-kit/modifiers
npm error         @dnd-kit/modifiers@"^6.0.1" from decap-cms-widget-file@3.0.4
npm error         node_modules/decap-cms-app/node_modules/decap-cms-widget-file
npm error         2 more (decap-cms-widget-list, decap-cms-widget-relation)
npm error       4 more (@dnd-kit/sortable, decap-cms-widget-file, ...)
npm error   36 more (@dnd-kit/core, @dnd-kit/modifiers, @dnd-kit/sortable, ...)
npm error
npm error Could not resolve dependency:
npm error peer react@"^16.8.4 || ^17.0.0" from decap-cms-app@3.0.12
npm error node_modules/decap-cms-app
npm error   decap-cms-app@"3.0.12" from the root project
npm error
npm error Conflicting peer dependency: react@17.0.2
npm error node_modules/react
npm error   peer react@"^16.8.4 || ^17.0.0" from decap-cms-app@3.0.12
npm error   node_modules/decap-cms-app
npm error     decap-cms-app@"3.0.12" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2024-05-08T14_58_17_824Z-eresolve-report.txt

npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-05-08T14_58_17_824Z-debug-0.log

Copy link

vercel bot commented Apr 1, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
charlottestuby ❌ Failed (Inspect) Jan 6, 2025 1:30pm

@renovate renovate bot force-pushed the renovate/node-20.x branch from a74d7eb to d1ae113 Compare April 2, 2024 21:18
@renovate renovate bot force-pushed the renovate/node-20.x branch from d1ae113 to 1de2618 Compare April 3, 2024 15:51
@renovate renovate bot changed the title Update dependency node to v20.12.0 Update dependency node to v20.12.1 Apr 3, 2024
@renovate renovate bot force-pushed the renovate/node-20.x branch from 1de2618 to 7da2dda Compare April 4, 2024 01:40
@renovate renovate bot force-pushed the renovate/node-20.x branch from 7da2dda to b15a6fb Compare April 6, 2024 02:46
@renovate renovate bot force-pushed the renovate/node-20.x branch from b15a6fb to 6f63a95 Compare April 9, 2024 04:26
@renovate renovate bot force-pushed the renovate/node-20.x branch from 6f63a95 to 346ac8f Compare April 9, 2024 23:28
@renovate renovate bot force-pushed the renovate/node-20.x branch from 346ac8f to d6082b7 Compare April 10, 2024 20:55
@renovate renovate bot changed the title Update dependency node to v20.12.1 Update dependency node to v20.12.2 Apr 10, 2024
@renovate renovate bot changed the title Update dependency node to v20.12.2 chore(deps): update dependency node to v20.12.2 Apr 17, 2024
@renovate renovate bot force-pushed the renovate/node-20.x branch from d6082b7 to bf0266a Compare May 1, 2024 21:23
@renovate renovate bot force-pushed the renovate/node-20.x branch from bf0266a to faa6c5b Compare May 6, 2024 14:13
@renovate renovate bot force-pushed the renovate/node-20.x branch from faa6c5b to b666ce7 Compare May 6, 2024 19:07
@renovate renovate bot force-pushed the renovate/node-20.x branch from b666ce7 to b24f038 Compare May 7, 2024 16:16
@renovate renovate bot changed the title chore(deps): update dependency node to v20.12.2 chore(deps): update dependency node to v20.13.0 May 7, 2024
@renovate renovate bot force-pushed the renovate/node-20.x branch from e7fbffa to af5ca3a Compare October 25, 2024 13:11
@renovate renovate bot force-pushed the renovate/node-20.x branch from af5ca3a to ceffc98 Compare October 28, 2024 21:45
@renovate renovate bot force-pushed the renovate/node-20.x branch from ceffc98 to 91f8717 Compare October 29, 2024 18:33
@renovate renovate bot force-pushed the renovate/node-20.x branch from 91f8717 to 859e79b Compare October 31, 2024 06:14
@renovate renovate bot force-pushed the renovate/node-20.x branch from 859e79b to 7b15639 Compare October 31, 2024 18:16
@renovate renovate bot force-pushed the renovate/node-20.x branch from 7b15639 to 9e155b1 Compare November 3, 2024 04:38
@renovate renovate bot changed the title Update dependency node to v20.18.0 Update Node.js to v20.18.0 Nov 13, 2024
@renovate renovate bot force-pushed the renovate/node-20.x branch from 9e155b1 to 35ce1a4 Compare November 20, 2024 18:06
@renovate renovate bot changed the title Update Node.js to v20.18.0 Update Node.js to v20.18.1 Nov 20, 2024
@renovate renovate bot force-pushed the renovate/node-20.x branch from 35ce1a4 to 175fa15 Compare November 23, 2024 06:39
@renovate renovate bot force-pushed the renovate/node-20.x branch from 175fa15 to 7d8cc3f Compare November 25, 2024 23:01
@renovate renovate bot force-pushed the renovate/node-20.x branch from 7d8cc3f to 7e50d03 Compare November 28, 2024 08:47
@renovate renovate bot force-pushed the renovate/node-20.x branch from 7e50d03 to 223c7aa Compare December 11, 2024 11:35
@renovate renovate bot force-pushed the renovate/node-20.x branch from 223c7aa to cfeec41 Compare January 1, 2025 04:10
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