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(): update node.js to v18.20.5 #125

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 31, 2024

This PR contains the following updates:

Package Type Update Change
node (source) engines minor 18.19.1 -> 18.20.5

Release Notes

nodejs/node (node)

v18.20.5: 2024-11-12, Version 18.20.5 'Hydrogen' (LTS), @​aduh95

Compare Source

Notable Changes
  • [ac37e554a5] - esm: mark import attributes and JSON module as stable (Nicolò Ribaudo) #​55333
Commits

v18.20.4

Compare Source

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 [email protected] 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


Configuration

📅 Schedule: Branch creation - "after 10pm every weekend,before 5am every weekend" in timezone Asia/Tokyo, 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

vercel bot commented Mar 31, 2024

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

Name Status Preview Comments Updated (UTC)
reoiam-dev-web ❌ Failed (Inspect) Nov 13, 2024 2:12am

Copy link
Contributor Author

renovate bot commented Mar 31, 2024

⚠ Artifact update problem

Renovate failed to update artifacts 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: bun.lockb
Command failed: bun install
bun install v1.1.3 (2615dc74)
 Saved yarn.lock

$ patch-package
$ concurrently -n "HUSKY,PLAYWRIGHT,TURBO" -c "magenta,blue,cyan" "husky install" "playwright install" "turbo build --filter='./packages/*'" && bun --cwd apps/web _postprepare
$ concurrently -n "PANDA,CONTENTLAYER" -c "yellow,blue" "panda codegen" "contentlayer build"
error: script "_postprepare" exited with code 1
error: prepare script from "reoiam-dev" exited with 1

File name: yarn.lock
error This project's package.json defines "packageManager": "yarn@[email protected]". However the current global version of Yarn is 1.22.22.

Presence of the "packageManager" field indicates that the project is meant to be used with Corepack, a tool included by default with all official Node.js distributions starting from 16.9 and 14.19.
Corepack must currently be enabled by running corepack enable in your terminal. For more information, check out https://yarnpkg.com/corepack.

@renovate renovate bot force-pushed the renovate/node-18.x branch from 4e47c22 to bf51c00 Compare April 1, 2024 09:07
@renovate renovate bot force-pushed the renovate/node-18.x branch from bf51c00 to bf1ff0c Compare April 3, 2024 02:42
@renovate renovate bot force-pushed the renovate/node-18.x branch from bf1ff0c to 56174af Compare April 7, 2024 05:54
@renovate renovate bot changed the title chore(): update node.js to v18.20.0 chore(): update node.js to v18.20.1 Apr 7, 2024
@renovate renovate bot force-pushed the renovate/node-18.x branch from 56174af to 6c0bd54 Compare April 10, 2024 19:28
@renovate renovate bot changed the title chore(): update node.js to v18.20.1 chore(): update node.js to v18.20.2 Apr 10, 2024
@renovate renovate bot force-pushed the renovate/node-18.x branch from 6c0bd54 to 31e69df Compare May 23, 2024 08:49
@renovate renovate bot changed the title chore(): update node.js to v18.20.2 chore(): update node.js to v18.20.3 May 23, 2024
Copy link
Contributor Author

renovate bot commented May 23, 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: yarn.lock
error This project's package.json defines "packageManager": "yarn@[email protected]". However the current global version of Yarn is 1.22.22.

Presence of the "packageManager" field indicates that the project is meant to be used with Corepack, a tool included by default with all official Node.js distributions starting from 16.9 and 14.19.
Corepack must currently be enabled by running corepack enable in your terminal. For more information, check out https://yarnpkg.com/corepack.

@renovate renovate bot force-pushed the renovate/node-18.x branch from 31e69df to a9934df Compare July 10, 2024 05:36
@renovate renovate bot changed the title chore(): update node.js to v18.20.3 chore(): update node.js to v18.20.4 Jul 10, 2024
@renovate renovate bot force-pushed the renovate/node-18.x branch from a9934df to 0b6fe39 Compare November 13, 2024 02:11
@renovate renovate bot changed the title chore(): update node.js to v18.20.4 chore(): update node.js to v18.20.5 Nov 13, 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