Skip to content

chore(deps): update node.js to v24#1626

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

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

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Oct 28, 2025

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Type Update Change Age Confidence
node stage major 22.17.124.13.1 age confidence
@types/node (source) devDependencies major 22.16.524.10.13 age confidence

Release Notes

nodejs/node (node)

v24.13.1: 2026-02-10, Version 24.13.1 'Krypton' (LTS), @​aduh95

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 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
Copy link
Contributor Author

renovate bot commented Oct 28, 2025

⚠️ 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 warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @formatjs/intl@3.1.6
npm error Found: typescript@5.5.4
npm error node_modules/typescript
npm error   typescript@"5.5.4" from the root project
npm error   peer typescript@">=4.2.0" from ts-api-utils@1.3.0
npm error   node_modules/ts-api-utils
npm error     ts-api-utils@"^1.3.0" from @typescript-eslint/eslint-plugin@7.18.0
npm error     node_modules/@typescript-eslint/eslint-plugin
npm error       dev @typescript-eslint/eslint-plugin@"7.18.0" from the root project
npm error     ts-api-utils@"^1.3.0" from @typescript-eslint/type-utils@7.18.0
npm error     node_modules/@typescript-eslint/type-utils
npm error       @typescript-eslint/type-utils@"7.18.0" from @typescript-eslint/eslint-plugin@7.18.0
npm error       node_modules/@typescript-eslint/eslint-plugin
npm error         dev @typescript-eslint/eslint-plugin@"7.18.0" from the root project
npm error     2 more (@typescript-eslint/typescript-estree, @typescript-eslint/typescript-estree)
npm error   1 more (ts-loader)
npm error
npm error Could not resolve dependency:
npm error peerOptional typescript@"^5.6.0" from @formatjs/intl@3.1.6
npm error node_modules/@formatjs/intl
npm error   @formatjs/intl@"3.1.6" from the root project
npm error
npm error Conflicting peer dependency: typescript@5.9.3
npm error node_modules/typescript
npm error   peerOptional typescript@"^5.6.0" from @formatjs/intl@3.1.6
npm error   node_modules/@formatjs/intl
npm error     @formatjs/intl@"3.1.6" 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 /runner/cache/others/npm/_logs/2026-02-17T17_54_57_908Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-02-17T17_54_57_908Z-debug-0.log

@renovate renovate bot force-pushed the renovate/node-24.x branch 3 times, most recently from 984ea16 to 6b10490 Compare November 3, 2025 03:55
@renovate renovate bot force-pushed the renovate/node-24.x branch 3 times, most recently from 38ea75e to dfcb44a Compare November 13, 2025 02:01
@renovate renovate bot force-pushed the renovate/node-24.x branch 7 times, most recently from d98f860 to 6c78e76 Compare November 30, 2025 00:42
@renovate renovate bot force-pushed the renovate/node-24.x branch 4 times, most recently from 0db2015 to 8f00204 Compare December 11, 2025 21:25
@renovate renovate bot force-pushed the renovate/node-24.x branch 4 times, most recently from 8ce47d6 to 05aa37d Compare December 18, 2025 19:07
@renovate renovate bot force-pushed the renovate/node-24.x branch 3 times, most recently from 7348200 to 0941089 Compare December 29, 2025 06:49
@renovate renovate bot force-pushed the renovate/node-24.x branch 2 times, most recently from b0679ad to 6315949 Compare January 3, 2026 02:56
@renovate renovate bot force-pushed the renovate/node-24.x branch 2 times, most recently from cfb6f91 to 32d17e3 Compare January 10, 2026 18:22
@renovate renovate bot force-pushed the renovate/node-24.x branch 3 times, most recently from a02731a to 227cbac Compare January 15, 2026 19:29
@renovate renovate bot force-pushed the renovate/node-24.x branch 5 times, most recently from 190d516 to b0f9b16 Compare February 8, 2026 02:30
@renovate renovate bot force-pushed the renovate/node-24.x branch from b0f9b16 to 0604cfe Compare February 10, 2026 23:54
@renovate renovate bot force-pushed the renovate/node-24.x branch from 0604cfe to d80ba33 Compare February 12, 2026 03:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants

Comments