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 dependency node to v18.20.3 #2706

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Sep 19, 2023

Mend Renovate

This PR contains the following updates:

Package Type Update Change Age Adoption Passing Confidence
node (source) minor 18.17.1 -> 18.20.3 age adoption passing confidence
@types/node (source) devDependencies minor 18.17.17 -> 18.19.33 age adoption passing confidence

Release Notes

nodejs/node (node)

v18.20.3: 2024-05-21, Version 18.20.3 'Hydrogen' (LTS), @​richardlau

Compare Source

Notable Changes

This release fixes a regression introduced in Node.js 18.19.0 where http.server.close() was incorrectly closing idle connections.

A fix has also been included for compiling Node.js from source with newer versions of Clang.

The list of keys used to sign releases has been synchronized with the current list from the main branch.

Updated dependencies
  • acorn updated to 8.11.3.
  • acorn-walk updated to 8.3.2.
  • ada updated to 2.7.8.
  • c-ares updated to 1.28.1.
  • corepack updated to 0.28.0.
  • nghttp2 updated to 1.61.0.
  • ngtcp2 updated to 1.3.0.
  • npm updated to 10.7.0. Includes a fix from npm@10.5.1 to limit the number of open connections npm/cli#7324.
  • simdutf updated to 5.2.4.
  • zlib updated to 1.3.0.1-motley-7d77fb7.
Commits

v18.20.2: 2024-04-10, Version 18.20.2 'Hydrogen' (LTS), @​RafaelGSS

Compare Source

This is a security release.

Notable Changes
  • CVE-2024-27980 - Command injection via args parameter of child_process.spawn without shell option enabled on Windows
Commits

v18.20.1

Compare Source

v18.20.0

Compare Source

v18.19.1

Compare Source

v18.19.0

Compare Source

v18.18.2

Compare Source

v18.18.1: 2023-10-10, Version 18.18.1 'Hydrogen' (LTS), @​richardlau

Compare Source

Notable Changes

This release addresses some regressions that appeared in Node.js 18.18.0:

  • (Windows) FS can not handle certain characters in file name #​48673
  • 18 and 20 node images give error - Text file busy (after re-build images) nodejs/docker-node#1968
  • libuv update in 18.18.0 breaks webpack's thread-loader #​49911

The libuv 1.45.0 and 1.46.0 updates that were released in Node.js 18.18.0 have been temporarily reverted.

Commits

v18.18.0: 2023-09-18, Version 18.18.0 'Hydrogen' (LTS), @​ruyadorno

Compare Source

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 force-pushed the renovate/node-18.x branch 4 times, most recently from 6707c84 to e67270b Compare September 25, 2023 22:58
@renovate renovate bot force-pushed the renovate/node-18.x branch 4 times, most recently from 5b93950 to fec6908 Compare October 3, 2023 01:01
@renovate renovate bot force-pushed the renovate/node-18.x branch 2 times, most recently from 0d2cbfa to 81c0521 Compare October 7, 2023 03:36
@renovate renovate bot changed the title chore(deps): update dependency node to v18.18.0 chore(deps): update dependency node to v18.18.1 Oct 10, 2023
@renovate renovate bot force-pushed the renovate/node-18.x branch 2 times, most recently from f6f09e6 to cc15949 Compare October 12, 2023 22:55
@renovate renovate bot changed the title chore(deps): update dependency node to v18.18.1 chore(deps): update dependency node to v18.18.2 Oct 13, 2023
@renovate renovate bot force-pushed the renovate/node-18.x branch 4 times, most recently from d766ca9 to 132fce2 Compare October 18, 2023 18:16
@renovate renovate bot force-pushed the renovate/node-18.x branch 2 times, most recently from d284624 to ecaaa8f Compare October 31, 2023 09:28
@renovate renovate bot force-pushed the renovate/node-18.x branch 4 times, most recently from 7b64914 to 662f810 Compare November 8, 2023 00:21
@renovate renovate bot force-pushed the renovate/node-18.x branch 6 times, most recently from 22ba2d4 to 593cf8c Compare November 23, 2023 10:20
@renovate renovate bot changed the title chore(deps): update dependency node to v18.19.0 chore(deps): update dependency node to v18.19.1 Feb 14, 2024
@renovate renovate bot force-pushed the renovate/node-18.x branch 2 times, most recently from c024ad2 to db5f1be Compare February 15, 2024 17:02
@renovate renovate bot force-pushed the renovate/node-18.x branch 4 times, most recently from bf222f0 to ddca41d Compare February 29, 2024 14:51
@renovate renovate bot force-pushed the renovate/node-18.x branch 3 times, most recently from 4459ba3 to 1d7c50d Compare March 13, 2024 13:41
@renovate renovate bot force-pushed the renovate/node-18.x branch 2 times, most recently from beb5346 to fcc49cc Compare March 19, 2024 13:43
@renovate renovate bot changed the title chore(deps): update dependency node to v18.19.1 chore(deps): update dependency node to v18.20.0 Mar 26, 2024
@renovate renovate bot force-pushed the renovate/node-18.x branch 3 times, most recently from d696f70 to c6b0ff0 Compare April 3, 2024 15:41
@renovate renovate bot changed the title chore(deps): update dependency node to v18.20.0 chore(deps): update dependency node to v18.20.1 Apr 3, 2024
@renovate renovate bot force-pushed the renovate/node-18.x branch 2 times, most recently from 24da7d6 to 27f03a6 Compare April 10, 2024 00:55
Copy link
Contributor Author

renovate bot commented Apr 10, 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 unable to resolve dependency tree
npm error
npm error While resolving: serialport-monorepo@0.0.0
npm error Found: eslint@9.2.0
npm error node_modules/eslint
npm error   dev eslint@"9.2.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer eslint@"^8.56.0" from @typescript-eslint/parser@7.8.0
npm error node_modules/@typescript-eslint/parser
npm error   dev @typescript-eslint/parser@"7.8.0" from the root project
npm error   peer @typescript-eslint/parser@"^7.0.0" from @typescript-eslint/eslint-plugin@7.8.0
npm error   node_modules/@typescript-eslint/eslint-plugin
npm error     dev @typescript-eslint/eslint-plugin@"7.8.0" 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-06T21_37_41_475Z-eresolve-report.txt

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

@renovate renovate bot changed the title chore(deps): update dependency node to v18.20.1 chore(deps): update dependency node to v18.20.2 Apr 14, 2024
@renovate renovate bot force-pushed the renovate/node-18.x branch 2 times, most recently from 77c089e to 67da2b8 Compare May 10, 2024 20:53
Copy link
Contributor Author

renovate bot commented May 10, 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 unable to resolve dependency tree
npm error
npm error While resolving: serialport-monorepo@0.0.0
npm error Found: eslint@9.2.0
npm error node_modules/eslint
npm error   dev eslint@"9.2.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer eslint@"^8.56.0" from @typescript-eslint/parser@7.8.0
npm error node_modules/@typescript-eslint/parser
npm error   dev @typescript-eslint/parser@"7.8.0" from the root project
npm error   peer @typescript-eslint/parser@"^7.0.0" from @typescript-eslint/eslint-plugin@7.8.0
npm error   node_modules/@typescript-eslint/eslint-plugin
npm error     dev @typescript-eslint/eslint-plugin@"7.8.0" 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-22T23_54_09_807Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-05-22T23_54_09_807Z-debug-0.log

@renovate renovate bot changed the title chore(deps): update dependency node to v18.20.2 chore(deps): update dependency node to v18.20.3 May 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

0 participants