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.10.7 #14435

Merged
merged 1 commit into from
Jan 17, 2025

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 16, 2025

This PR contains the following updates:

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

Configuration

📅 Schedule: 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 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 dependencies Pull requests that update a dependency file label Jan 16, 2025
Copy link
Contributor Author

renovate bot commented Jan 16, 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 error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: @nestjs/[email protected]
npm error Found: [email protected]
npm error node_modules/graphql
npm error   dev graphql@"16.9.0" from the root project
npm error   peer graphql@"^16.5.0" from @apollo/[email protected]
npm error   node_modules/@apollo/gateway
npm error     peerOptional @apollo/gateway@"^2.0.0" from @nestjs/[email protected]
npm error     node_modules/@nestjs/apollo
npm error       dev @nestjs/apollo@"13.0.0" from the root project
npm error   2 more (@apollo/server, @apollo/subgraph)
npm error
npm error Could not resolve dependency:
npm error peer graphql@"^16.10.0" from @nestjs/[email protected]
npm error node_modules/@nestjs/graphql
npm error   dev @nestjs/graphql@"13.0.0" 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 /tmp/renovate/cache/others/npm/_logs/2025-01-17T13_52_06_071Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2025-01-17T13_52_06_071Z-debug-0.log

@renovate renovate bot force-pushed the renovate/node-22.x branch 12 times, most recently from 7643fd7 to f143be0 Compare January 17, 2025 12:56
@renovate renovate bot force-pushed the renovate/node-22.x branch from f143be0 to 028cbff Compare January 17, 2025 13:04
@coveralls
Copy link

Pull Request Test Coverage Report for Build 0cababb9-805c-4b6d-ac56-667027edd30a

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 89.696%

Totals Coverage Status
Change from base Build fc27da9d-2a1e-4b8b-ac32-cb20670b91ce: 0.0%
Covered Lines: 7103
Relevant Lines: 7919

💛 - Coveralls

@kamilmysliwiec kamilmysliwiec merged commit 0c1df77 into master Jan 17, 2025
5 of 6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants