Skip to content

Update dependency @types/node to v24#42

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

Update dependency @types/node to v24#42
renovate[bot] wants to merge 1 commit intomainfrom
renovate/node-24.x

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Oct 28, 2025

This PR contains the following updates:

Package Change Age Confidence
@types/node (source) 20.8.624.10.13 age confidence

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 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 added the renovate label Oct 28, 2025
@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 ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: cli-authentication@1.0.0
npm ERR! Found: @typescript-eslint/eslint-plugin@6.8.0
npm ERR! node_modules/@typescript-eslint/eslint-plugin
npm ERR!   dev @typescript-eslint/eslint-plugin@"8.41.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! dev @typescript-eslint/eslint-plugin@"8.41.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: eslint@9.34.0
npm ERR! node_modules/eslint
npm ERR!   peer eslint@"^8.57.0 || ^9.0.0" from @typescript-eslint/eslint-plugin@8.41.0
npm ERR!   node_modules/@typescript-eslint/eslint-plugin
npm ERR!     dev @typescript-eslint/eslint-plugin@"8.41.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /runner/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /runner/cache/others/npm/_logs/2026-02-17T18_03_59_481Z-debug-0.log

@renovate renovate bot force-pushed the renovate/node-24.x branch 2 times, most recently from 479b1d3 to 810e22e Compare November 8, 2025 23:39
@renovate renovate bot force-pushed the renovate/node-24.x branch 2 times, most recently from 0ec69d6 to 59c6094 Compare November 11, 2025 05:33
@renovate renovate bot force-pushed the renovate/node-24.x branch 2 times, most recently from 676d960 to c931282 Compare November 24, 2025 02:52
@renovate renovate bot force-pushed the renovate/node-24.x branch from c931282 to 8d5932e Compare December 3, 2025 05:12
@renovate renovate bot force-pushed the renovate/node-24.x branch 4 times, most recently from bd27d09 to b2c66e0 Compare December 18, 2025 16:13
@renovate renovate bot force-pushed the renovate/node-24.x branch 5 times, most recently from cfaf486 to 2c5f4a0 Compare January 18, 2026 19:33
@renovate renovate bot force-pushed the renovate/node-24.x branch 3 times, most recently from bd689ed to c428e0f Compare February 11, 2026 03:10
@renovate renovate bot force-pushed the renovate/node-24.x branch from c428e0f to 358b898 Compare February 13, 2026 19:32
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