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 v16.18.121 #2519

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 7, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@types/node (source) 16.18.78 -> 16.18.121 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.

Copy link
Contributor Author

renovate bot commented Feb 7, 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/sequelize@10.0.0
npm ERR! Found: reflect-metadata@0.2.1
npm ERR! node_modules/reflect-metadata
npm ERR!   dev reflect-metadata@"0.2.1" from the root project
npm ERR!   peer reflect-metadata@"^0.1.12 || ^0.2.0" from @nestjs/common@10.3.2
npm ERR!   node_modules/@nestjs/common
npm ERR!     dev @nestjs/common@"10.3.2" from the root project
npm ERR!     peer @nestjs/common@"^8.0.0 || ^9.0.0 || ^10.0.0" from @mikro-orm/nestjs@5.2.3
npm ERR!     node_modules/@mikro-orm/nestjs
npm ERR!       dev @mikro-orm/nestjs@"5.2.3" from the root project
npm ERR!     11 more (@nestjs/axios, @nestjs/core, @nestjs/mapped-types, ...)
npm ERR!   7 more (@nestjs/core, @nestjs/mapped-types, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer reflect-metadata@"^0.1.13" from @nestjs/sequelize@10.0.0
npm ERR! node_modules/@nestjs/sequelize
npm ERR!   dev @nestjs/sequelize@"10.0.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: reflect-metadata@0.1.14
npm ERR! node_modules/reflect-metadata
npm ERR!   peer reflect-metadata@"^0.1.13" from @nestjs/sequelize@10.0.0
npm ERR!   node_modules/@nestjs/sequelize
npm ERR!     dev @nestjs/sequelize@"10.0.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 /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/2024-05-06T21_25_43_682Z-debug-0.log

@renovate renovate bot force-pushed the renovate/node-16.x branch 6 times, most recently from 0420de9 to eaf9695 Compare February 8, 2024 21:09
@renovate renovate bot changed the title chore(deps): update dependency @types/node to v16.18.79 chore(deps): update dependency @types/node to v16.18.80 Feb 8, 2024
@renovate renovate bot changed the title chore(deps): update dependency @types/node to v16.18.80 chore(deps): update dependency @types/node to v16.18.81 Feb 15, 2024
@renovate renovate bot changed the title chore(deps): update dependency @types/node to v16.18.81 chore(deps): update dependency @types/node to v16.18.82 Feb 15, 2024
@renovate renovate bot force-pushed the renovate/node-16.x branch 3 times, most recently from a442f7a to 2fd7dc7 Compare February 22, 2024 22:46
@renovate renovate bot changed the title chore(deps): update dependency @types/node to v16.18.82 chore(deps): update dependency @types/node to v16.18.83 Feb 22, 2024
@renovate renovate bot changed the title chore(deps): update dependency @types/node to v16.18.83 chore(deps): update dependency @types/node to v16.18.84 Feb 28, 2024
@renovate renovate bot changed the title chore(deps): update dependency @types/node to v16.18.84 chore(deps): update dependency @types/node to v16.18.85 Feb 28, 2024
@renovate renovate bot changed the title chore(deps): update dependency @types/node to v16.18.85 chore(deps): update dependency @types/node to v16.18.86 Feb 29, 2024
@renovate renovate bot changed the title chore(deps): update dependency @types/node to v16.18.86 chore(deps): update dependency @types/node to v16.18.87 Mar 6, 2024
@renovate renovate bot changed the title chore(deps): update dependency @types/node to v16.18.87 chore(deps): update dependency @types/node to v16.18.88 Mar 12, 2024
@renovate renovate bot changed the title chore(deps): update dependency @types/node to v16.18.88 chore(deps): update dependency @types/node to v16.18.89 Mar 13, 2024
@renovate renovate bot changed the title chore(deps): update dependency @types/node to v16.18.106 chore(deps): update dependency @types/node to v16.18.107 Sep 4, 2024
@renovate renovate bot changed the title chore(deps): update dependency @types/node to v16.18.107 chore(deps): update dependency @types/node to v16.18.108 Sep 5, 2024
@renovate renovate bot changed the title chore(deps): update dependency @types/node to v16.18.108 chore(deps): update dependency @types/node to v16.18.109 Sep 25, 2024
@renovate renovate bot changed the title chore(deps): update dependency @types/node to v16.18.109 chore(deps): update dependency @types/node to v16.18.110 Sep 25, 2024
@renovate renovate bot changed the title chore(deps): update dependency @types/node to v16.18.110 chore(deps): update dependency @types/node to v16.18.111 Sep 26, 2024
@renovate renovate bot changed the title chore(deps): update dependency @types/node to v16.18.111 chore(deps): update dependency @types/node to v16.18.112 Sep 27, 2024
@renovate renovate bot changed the title chore(deps): update dependency @types/node to v16.18.112 chore(deps): update dependency @types/node to v16.18.113 Oct 8, 2024
@renovate renovate bot changed the title chore(deps): update dependency @types/node to v16.18.113 chore(deps): update dependency @types/node to v16.18.114 Oct 17, 2024
@renovate renovate bot changed the title chore(deps): update dependency @types/node to v16.18.114 chore(deps): update dependency @types/node to v16.18.115 Oct 23, 2024
@renovate renovate bot changed the title chore(deps): update dependency @types/node to v16.18.115 chore(deps): update dependency @types/node to v16.18.116 Oct 29, 2024
@renovate renovate bot changed the title chore(deps): update dependency @types/node to v16.18.116 chore(deps): update dependency @types/node to v16.18.117 Oct 31, 2024
@renovate renovate bot changed the title chore(deps): update dependency @types/node to v16.18.117 chore(deps): update dependency @types/node to v16.18.118 Oct 31, 2024
@renovate renovate bot changed the title chore(deps): update dependency @types/node to v16.18.118 chore(deps): update dependency @types/node to v16.18.119 Nov 3, 2024
@renovate renovate bot changed the title chore(deps): update dependency @types/node to v16.18.119 chore(deps): update dependency @types/node to v16.18.120 Nov 25, 2024
@renovate renovate bot changed the title chore(deps): update dependency @types/node to v16.18.120 chore(deps): update dependency @types/node to v16.18.121 Nov 28, 2024
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