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 reflect-metadata to v0.2.2 #467

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 11, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
reflect-metadata (source) ^0.1.13 -> ^0.1.13 || ^0.2.0 age adoption passing confidence
reflect-metadata (source) 0.1.13 -> 0.2.2 age adoption passing confidence

Release Notes

rbuckton/reflect-metadata (reflect-metadata)

v0.2.2

Compare Source

v0.2.1

Compare Source

What's Changed

Full Changelog: rbuckton/reflect-metadata@v0.2.0...v0.2.1

v0.2.0: reflect-metadata 0.2.0

Compare Source

What's Changed

Full Changelog: rbuckton/reflect-metadata@v0.1.14...v0.2.0

v0.1.14

Compare Source


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 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.

Copy link
Contributor Author

renovate bot commented Feb 11, 2024

⚠ Artifact update problem

Renovate failed to update artifacts 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/common@8.4.1
npm ERR! Found: reflect-metadata@0.2.2
npm ERR! node_modules/reflect-metadata
npm ERR!   dev reflect-metadata@"0.2.2" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer reflect-metadata@"^0.1.12" from @nestjs/common@8.4.1
npm ERR! node_modules/@nestjs/common
npm ERR!   dev @nestjs/common@"8.4.1" from the root project
npm ERR!   peer @nestjs/common@"^8.0.0" from @nestjs/core@8.4.1
npm ERR!   node_modules/@nestjs/core
npm ERR!     dev @nestjs/core@"8.4.1" 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.12" from @nestjs/common@8.4.1
npm ERR!   node_modules/@nestjs/common
npm ERR!     dev @nestjs/common@"8.4.1" from the root project
npm ERR!     peer @nestjs/common@"^8.0.0" from @nestjs/core@8.4.1
npm ERR!     node_modules/@nestjs/core
npm ERR!       dev @nestjs/core@"8.4.1" 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-04-26T13_49_42_001Z-debug-0.log

File name: demo/package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @nestjs/common@8.4.1
npm ERR! Found: reflect-metadata@0.2.2
npm ERR! node_modules/reflect-metadata
npm ERR!   reflect-metadata@"0.2.2" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer reflect-metadata@"^0.1.12" from @nestjs/common@8.4.1
npm ERR! node_modules/@nestjs/common
npm ERR!   @nestjs/common@"8.4.1" from the root project
npm ERR!   peer @nestjs/common@"^8.0.0" from @nestjs/core@8.4.1
npm ERR!   node_modules/@nestjs/core
npm ERR!     @nestjs/core@"8.4.1" from the root project
npm ERR!     3 more (@nestjs/platform-express, @nestjs/testing, @nestjs/typeorm)
npm ERR!   3 more (@nestjs/platform-express, @nestjs/testing, @nestjs/typeorm)
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.12" from @nestjs/common@8.4.1
npm ERR!   node_modules/@nestjs/common
npm ERR!     @nestjs/common@"8.4.1" from the root project
npm ERR!     peer @nestjs/common@"^8.0.0" from @nestjs/core@8.4.1
npm ERR!     node_modules/@nestjs/core
npm ERR!       @nestjs/core@"8.4.1" from the root project
npm ERR!       3 more (@nestjs/platform-express, @nestjs/testing, @nestjs/typeorm)
npm ERR!     3 more (@nestjs/platform-express, @nestjs/testing, @nestjs/typeorm)
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-04-26T13_49_48_486Z-debug-0.log

@renovate renovate bot force-pushed the renovate/reflect-metadata-0.x branch 2 times, most recently from 4105f38 to 23fd19d Compare February 11, 2024 07:30
@renovate renovate bot force-pushed the renovate/reflect-metadata-0.x branch from 23fd19d to 81f0105 Compare March 29, 2024 04:23
@renovate renovate bot changed the title chore(deps): update dependency reflect-metadata to v0.2.1 chore(deps): update dependency reflect-metadata to v0.2.2 Mar 29, 2024
@renovate renovate bot force-pushed the renovate/reflect-metadata-0.x branch 2 times, most recently from 281db11 to 2a09d8f Compare April 26, 2024 13:49
@renovate renovate bot force-pushed the renovate/reflect-metadata-0.x branch from 2a09d8f to cd31599 Compare May 21, 2024 16:38
Copy link
Contributor Author

renovate bot commented May 21, 2024

⚠️ Artifact update problem

Renovate failed to update artifacts 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/common@8.4.1
npm ERR! Found: reflect-metadata@0.2.2
npm ERR! node_modules/reflect-metadata
npm ERR!   dev reflect-metadata@"0.2.2" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer reflect-metadata@"^0.1.12" from @nestjs/common@8.4.1
npm ERR! node_modules/@nestjs/common
npm ERR!   dev @nestjs/common@"8.4.1" from the root project
npm ERR!   peer @nestjs/common@"^8.0.0" from @nestjs/core@8.4.1
npm ERR!   node_modules/@nestjs/core
npm ERR!     dev @nestjs/core@"8.4.1" 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.12" from @nestjs/common@8.4.1
npm ERR!   node_modules/@nestjs/common
npm ERR!     dev @nestjs/common@"8.4.1" from the root project
npm ERR!     peer @nestjs/common@"^8.0.0" from @nestjs/core@8.4.1
npm ERR!     node_modules/@nestjs/core
npm ERR!       dev @nestjs/core@"8.4.1" 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-10-23T03_50_41_208Z-debug-0.log

File name: demo/package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @nestjs/common@8.4.1
npm ERR! Found: reflect-metadata@0.2.2
npm ERR! node_modules/reflect-metadata
npm ERR!   reflect-metadata@"0.2.2" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer reflect-metadata@"^0.1.12" from @nestjs/common@8.4.1
npm ERR! node_modules/@nestjs/common
npm ERR!   @nestjs/common@"8.4.1" from the root project
npm ERR!   peer @nestjs/common@"^8.0.0" from @nestjs/core@8.4.1
npm ERR!   node_modules/@nestjs/core
npm ERR!     @nestjs/core@"8.4.1" from the root project
npm ERR!     3 more (@nestjs/platform-express, @nestjs/testing, @nestjs/typeorm)
npm ERR!   3 more (@nestjs/platform-express, @nestjs/testing, @nestjs/typeorm)
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.12" from @nestjs/common@8.4.1
npm ERR!   node_modules/@nestjs/common
npm ERR!     @nestjs/common@"8.4.1" from the root project
npm ERR!     peer @nestjs/common@"^8.0.0" from @nestjs/core@8.4.1
npm ERR!     node_modules/@nestjs/core
npm ERR!       @nestjs/core@"8.4.1" from the root project
npm ERR!       3 more (@nestjs/platform-express, @nestjs/testing, @nestjs/typeorm)
npm ERR!     3 more (@nestjs/platform-express, @nestjs/testing, @nestjs/typeorm)
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-10-23T03_50_45_941Z-debug-0.log

@renovate renovate bot force-pushed the renovate/reflect-metadata-0.x branch 2 times, most recently from 98ef213 to ec5ff5c Compare June 5, 2024 16:48
@renovate renovate bot force-pushed the renovate/reflect-metadata-0.x branch from ec5ff5c to 9b46a9f Compare June 11, 2024 13:28
@renovate renovate bot force-pushed the renovate/reflect-metadata-0.x branch from 9b46a9f to 5164171 Compare June 21, 2024 13:47
@renovate renovate bot force-pushed the renovate/reflect-metadata-0.x branch from 5164171 to 3ff776d Compare July 1, 2024 10:30
@renovate renovate bot force-pushed the renovate/reflect-metadata-0.x branch from 3ff776d to 9f07344 Compare July 8, 2024 21:41
@renovate renovate bot force-pushed the renovate/reflect-metadata-0.x branch from 9f07344 to d382b6b Compare October 22, 2024 10:59
@renovate renovate bot force-pushed the renovate/reflect-metadata-0.x branch from d382b6b to 042fb11 Compare October 23, 2024 03:50
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