Skip to content

chore(deps): update node.js to v24.19.0 - #20

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/node-24.x
Open

chore(deps): update node.js to v24.19.0#20
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/node-24.x

Conversation

@renovate

@renovate renovate Bot commented Jun 2, 2026

Copy link
Copy Markdown
Contributor

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Type Update Change Pending
node (source) engines minor ^24.15.0^24.19.0 v24.20.0
node (source) minor 24.15.024.19.0 v24.20.0
node (source) tools minor 24.15.024.19.0 v24.20.0

Release Notes

nodejs/node (node)

v24.19.0: 2026-08-03, Version 24.19.0 'Krypton' (LTS), @​aduh95

Compare Source

Notable Changes
  • [d08872b530] - (SEMVER-MINOR) buffer: implement blob.textStream() (Matthew Aitken) #​64036
  • [35222948be] - (SEMVER-MINOR) deps: update OpenSSL build config to support compression (Tim Perry) #​62217
  • [d6ab039f24] - (SEMVER-MINOR) doc: update blockList stability status to release candidate (alphaleadership) #​63050
  • [1da05fb79d] - doc: mark stream.compose stable (Matteo Collina) #​62562
  • [3c1636dabf] - (SEMVER-MINOR) esm: add --experimental-import-text flag (Efe) #​62300
  • [e323e877be] - (SEMVER-MINOR) fs: support caller-supplied readFile() buffers (Matteo Collina) #​63634
  • [c1248c9544] - (SEMVER-MINOR) http: add httpValidation option to configure header value validation (RajeshKumar11) #​61597
  • [a534b65815] - (SEMVER-MINOR) net: support TCP_KEEPINTVL and TCP_KEEPCNT in setKeepAlive (Guy Bedford) #​63825
  • [a23cdec683] - (SEMVER-MINOR) perf_hooks: sample delay per event loop iteration (Pablo Erhard) #​62935
  • [7428b57a37] - (SEMVER-MINOR) src: allow empty --experimental-config-file (Marco Ippolito) #​61610
  • [e57597173c] - (SEMVER-MINOR) stream: expose ReadableStreamTee (Matteo Collina) #​64195
  • [5396235993] - (SEMVER-MINOR) tls: report negotiated TLS groups (Filip Skokan) #​64119
  • [5e901b5cd9] - (SEMVER-MINOR) tls: add certificateCompression option (Tim Perry) #​62217
Commits

Note

PR body was truncated to here.


Configuration

📅 Schedule: (UTC)

  • 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 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.

@renovate renovate Bot added the dependencies label Jun 2, 2026
@renovate
renovate Bot force-pushed the renovate/node-24.x branch 3 times, most recently from 3cc1c98 to ec86ed0 Compare June 9, 2026 09:28
@renovate
renovate Bot force-pushed the renovate/node-24.x branch 3 times, most recently from 209defc to 6111fc8 Compare June 24, 2026 00:59
@renovate renovate Bot changed the title chore(deps): update node.js to v24.16.0 chore(deps): update node.js to v24.17.0 Jun 24, 2026
@renovate
renovate Bot force-pushed the renovate/node-24.x branch from 6111fc8 to 8e91161 Compare June 30, 2026 02:59
@renovate renovate Bot changed the title chore(deps): update node.js to v24.17.0 chore(deps): update node.js to v24.18.0 Jun 30, 2026
@renovate
renovate Bot force-pushed the renovate/node-24.x branch from 8e91161 to 8df5214 Compare June 30, 2026 09:18
@renovate
renovate Bot force-pushed the renovate/node-24.x branch 2 times, most recently from 0bd8a30 to 8b13383 Compare July 22, 2026 13:00
@renovate

renovate Bot commented Jul 22, 2026

Copy link
Copy Markdown
Contributor Author

⚠️ 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: pnpm-lock.yaml
? Verifying lockfile against supply-chain policies (490 entries)...
✗ Lockfile failed supply-chain policy check (490 entries in 4.8s)
[ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 12 lockfile entries failed verification:
  @next/env@16.2.11 was published at 2026-07-21T15:58:36.000Z, within the minimumReleaseAge cutoff (2026-07-21T13:00:26.470Z)
  @next/eslint-plugin-next@16.2.11 was published at 2026-07-21T15:58:21.000Z, within the minimumReleaseAge cutoff (2026-07-21T13:00:26.470Z)
  @next/swc-darwin-arm64@16.2.11 was published at 2026-07-21T15:57:29.000Z, within the minimumReleaseAge cutoff (2026-07-21T13:00:26.470Z)
  @next/swc-darwin-x64@16.2.11 was published at 2026-07-21T15:57:58.000Z, within the minimumReleaseAge cutoff (2026-07-21T13:00:26.470Z)
  @next/swc-linux-arm64-gnu@16.2.11 was published at 2026-07-21T15:57:16.000Z, within the minimumReleaseAge cutoff (2026-07-21T13:00:26.470Z)
  @next/swc-linux-arm64-musl@16.2.11 was published at 2026-07-21T15:57:00.000Z, within the minimumReleaseAge cutoff (2026-07-21T13:00:26.470Z)
  @next/swc-linux-x64-gnu@16.2.11 was published at 2026-07-21T15:57:33.000Z, within the minimumReleaseAge cutoff (2026-07-21T13:00:26.470Z)
  @next/swc-linux-x64-musl@16.2.11 was published at 2026-07-21T15:57:17.000Z, within the minimumReleaseAge cutoff (2026-07-21T13:00:26.470Z)
  @next/swc-win32-arm64-msvc@16.2.11 was published at 2026-07-21T15:57:48.000Z, within the minimumReleaseAge cutoff (2026-07-21T13:00:26.470Z)
  @next/swc-win32-x64-msvc@16.2.11 was published at 2026-07-21T15:57:42.000Z, within the minimumReleaseAge cutoff (2026-07-21T13:00:26.470Z)
  eslint-config-next@16.2.11 was published at 2026-07-21T15:59:19.000Z, within the minimumReleaseAge cutoff (2026-07-21T13:00:26.470Z)
  next@16.2.11 was published at 2026-07-21T15:59:55.000Z, within the minimumReleaseAge cutoff (2026-07-21T13:00:26.470Z)

The lockfile contains entries that the active policies reject. This can mean the lockfile is stale, or that someone committed a lockfile that bypassed the policy locally — inspect recent changes to pnpm-lock.yaml before trusting it. If the changes look expected, run "pnpm clean --lockfile" and then "pnpm install" to rebuild from a fresh resolution. Alternatively, relax the policy that flagged them.

@renovate
renovate Bot force-pushed the renovate/node-24.x branch from 8b13383 to dd41f33 Compare July 27, 2026 13:41
@renovate
renovate Bot force-pushed the renovate/node-24.x branch from dd41f33 to 01d4466 Compare August 4, 2026 02:45
@renovate renovate Bot changed the title chore(deps): update node.js to v24.18.0 chore(deps): update node.js to v24.18.1 Aug 4, 2026
@renovate
renovate Bot force-pushed the renovate/node-24.x branch 3 times, most recently from a894673 to 5239b97 Compare August 10, 2026 01:14
@renovate renovate Bot changed the title chore(deps): update node.js to v24.18.1 chore(deps): update node.js to v24.19.0 Aug 10, 2026
@renovate
renovate Bot force-pushed the renovate/node-24.x branch from 5239b97 to fe93837 Compare August 12, 2026 08:17
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