Skip to content

chore(deps): update node.js to v24.6.0 - #2177

Merged
malice00 merged 2 commits into
masterfrom
renovate/node-24.x
Aug 17, 2025
Merged

malice00 merged 2 commits into
masterfrom
renovate/node-24.x

Conversation

@renovate

@renovate renovate Bot commented Aug 17, 2025 •

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Update Change
node (source) minor 24.5.0 -> 24.6.0

Release Notes

nodejs/node (node)

v24.6.0: 2025-08-14, Version 24.6.0 (Current), @​RafaelGSS

Compare Source

Notable Changes
  • [471fe712b3] - (SEMVER-MINOR) cli: add NODE_USE_SYSTEM_CA=1 (Joyee Cheung) #​59276
  • [38aedfbf73] - (SEMVER-MINOR) crypto: support ML-DSA KeyObject, sign, and verify (Filip Skokan) #​59259
  • [201304537e] - (SEMVER-MINOR) zlib: add dictionary support to zstdCompress and zstdDecompress (lluisemper) #​59240
  • [e79c93a5d0] - (SEMVER-MINOR) http: add server.keepAliveTimeoutBuffer option (Haram Jeong) #​59243
  • [c144d69efc] - lib: docs deprecate _http_* (Sebastian Beltran) #​59293
  • [aeb4de55a7] - (SEMVER-MINOR) fs: port SonicBoom module to fs module as Utf8Stream (James M Snell) #​58897
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 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.

@renovate
renovate Bot requested a review from prabhu as a code owner August 17, 2025 01:43
@renovate renovate Bot added the dependency Dependency updates label Aug 17, 2025
@prabhu

prabhu commented Aug 17, 2025

Copy link
Copy Markdown
Member

Maybe we should make such .nvmrc changes run all tests? It is funny that this PR is green, when node is trying to rival python in terms of breaking things.

@malice00

Copy link
Copy Markdown
Collaborator

I think the more correct question is: why did renovate only update .nvmrc?

@malice00

Copy link
Copy Markdown
Collaborator

@prabhu I guess now we run into the jest-issue you mentioned before. I think we need to decide on how to handle this: either try to replace jest with something, or wait until maybe node fixes things?

@prabhu

prabhu commented Aug 17, 2025

Copy link
Copy Markdown
Member

I added #2176. The PR nodejs/node#59117 is needed to fix OOM errors so looks like a useful improvement. I am definitely convinced that jest is the problem with just too many hacks. Poku, on the other hand, has no dependencies!

@setchy

setchy commented Aug 17, 2025 •

Copy link
Copy Markdown
Contributor

I think the more correct question is: why did renovate only update .nvmrc?

because different managers have different release cycles (node-tools vs docker vs @types/node etc)

@malice00

Copy link
Copy Markdown
Collaborator

I think the more correct question is: why did renovate only update .nvmrc?

because different managers have different release cycles (node-tools vs docker vs @types/node etc)

Fair enough, but besides the docker base-image, I don't see any reason why the other files had no updates. These are imo all based on the release on node.js itself, no other manager...

@renovate
renovate Bot force-pushed the renovate/node-24.x branch from ce0f8ff to 6708ab5 Compare August 17, 2025 20:59
Signed-off-by: Roland Asmann <roland.asmann@gmail.com>
@renovate

renovate Bot commented Aug 17, 2025

Copy link
Copy Markdown
Contributor Author

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

@malice00
malice00 merged commit 5d1835a into master Aug 17, 2025
@malice00
malice00 deleted the renovate/node-24.x branch August 17, 2025 23:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependency Dependency updates

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants