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(deps): update dependency @types/node to v22 #1149

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Oct 30, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@types/node (source) 14.18.16 -> 22.10.7 age adoption passing confidence

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


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.

Copy link
Author

renovate bot commented Oct 30, 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: package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @nestjs/[email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/typeorm
npm ERR!   typeorm@"0.3.6" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer typeorm@"^0.2.34" from @nestjs/[email protected]
npm ERR! node_modules/@nestjs/typeorm
npm ERR!   @nestjs/typeorm@"8.0.3" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/typeorm
npm ERR!   peer typeorm@"^0.2.34" from @nestjs/[email protected]
npm ERR!   node_modules/@nestjs/typeorm
npm ERR!     @nestjs/typeorm@"8.0.3" 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 /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2025-01-16T01_31_28_734Z-debug-0.log

@renovate renovate bot force-pushed the renovate/root/node-22.x branch 3 times, most recently from c13fc28 to c03414b Compare November 5, 2024 04:14
@renovate renovate bot force-pushed the renovate/root/node-22.x branch 4 times, most recently from 85da933 to 718ecd7 Compare November 28, 2024 14:51
@renovate renovate bot force-pushed the renovate/root/node-22.x branch from 718ecd7 to 642adeb Compare December 11, 2024 09:54
@renovate renovate bot force-pushed the renovate/root/node-22.x branch 3 times, most recently from e41c279 to 3b38ba9 Compare January 3, 2025 07:09
@renovate renovate bot force-pushed the renovate/root/node-22.x branch from 3b38ba9 to d619d8c Compare January 14, 2025 18:20
@renovate renovate bot force-pushed the renovate/root/node-22.x branch from d619d8c to f159642 Compare January 16, 2025 01:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants