Skip to content

fix(deps): update dependency reflect-metadata to v0.2.2 #942

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.

Sign up for GitHub

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

Jump to bottom
Closed
renovate wants to merge 1 commit into from
Closed

fix(deps): update dependency reflect-metadata to v0.2.2 #942

renovate wants to merge 1 commit into from

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Dec 15, 2023 •
edited
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
reflect-metadata (source) ^0.1.13 -> ^0.2.0 age adoption passing confidence
reflect-metadata (source) 0.1.14 -> 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: microsoft/reflect-metadata@v0.2.0...v0.2.1

v0.2.0: reflect-metadata 0.2.0

Compare Source

What's Changed

Full Changelog: microsoft/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.

@renovate
Copy link
Contributor Author

renovate bot commented Dec 15, 2023 •
edited
Loading

⚠ 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: sample/table-storage/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/reflect-metadata
npm ERR!   reflect-metadata@"^0.2.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer reflect-metadata@"^0.1.12" from @nestjs/[email protected]
npm ERR! node_modules/@nestjs/common
npm ERR!   @nestjs/common@"^10.0.0" from the root project
npm ERR!   peer @nestjs/common@"^10.0.0" from @nestjs/[email protected]
npm ERR!   node_modules/@nestjs/core
npm ERR!     @nestjs/core@"^10.0.0" from the root project
npm ERR!     2 more (@nestjs/platform-express, @nestjs/testing)
npm ERR!   2 more (@nestjs/platform-express, @nestjs/testing)
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/reflect-metadata
npm ERR!   peer reflect-metadata@"^0.1.12" from @nestjs/[email protected]
npm ERR!   node_modules/@nestjs/common
npm ERR!     @nestjs/common@"^10.0.0" from the root project
npm ERR!     peer @nestjs/common@"^10.0.0" from @nestjs/[email protected]
npm ERR!     node_modules/@nestjs/core
npm ERR!       @nestjs/core@"^10.0.0" from the root project
npm ERR!       2 more (@nestjs/platform-express, @nestjs/testing)
npm ERR!     2 more (@nestjs/platform-express, @nestjs/testing)
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! 
npm ERR! For a full report see:
npm ERR! /tmp/renovate/cache/others/npm/_logs/2024-03-29T04_39_47_679Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-03-29T04_39_47_679Z-debug-0.log
File name: sample/cosmos-db/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/reflect-metadata
npm ERR!   reflect-metadata@"^0.2.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer reflect-metadata@"^0.1.12" from @nestjs/[email protected]
npm ERR! node_modules/@nestjs/common
npm ERR!   @nestjs/common@"^10.0.0" from the root project
npm ERR!   peer @nestjs/common@"^10.0.0" from @nestjs/[email protected]
npm ERR!   node_modules/@nestjs/core
npm ERR!     @nestjs/core@"^10.0.0" from the root project
npm ERR!     2 more (@nestjs/platform-express, @nestjs/testing)
npm ERR!   2 more (@nestjs/platform-express, @nestjs/testing)
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/reflect-metadata
npm ERR!   peer reflect-metadata@"^0.1.12" from @nestjs/[email protected]
npm ERR!   node_modules/@nestjs/common
npm ERR!     @nestjs/common@"^10.0.0" from the root project
npm ERR!     peer @nestjs/common@"^10.0.0" from @nestjs/[email protected]
npm ERR!     node_modules/@nestjs/core
npm ERR!       @nestjs/core@"^10.0.0" from the root project
npm ERR!       2 more (@nestjs/platform-express, @nestjs/testing)
npm ERR!     2 more (@nestjs/platform-express, @nestjs/testing)
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! 
npm ERR! For a full report see:
npm ERR! /tmp/renovate/cache/others/npm/_logs/2024-03-29T04_39_53_864Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-03-29T04_39_53_864Z-debug-0.log
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/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/[email protected]
npm ERR! node_modules/@nestjs/common
npm ERR!   @nestjs/common@"^9.0.0 || ^10.0.0" from the root project
npm ERR!   peer @nestjs/common@"^10.0.0" from @nestjs/[email protected]
npm ERR!   node_modules/@nestjs/core
npm ERR!     @nestjs/core@"^9.0.0 || ^10.0.0" from the root project
npm ERR!     1 more (@nestjs/testing)
npm ERR!   1 more (@nestjs/testing)
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/reflect-metadata
npm ERR!   peer reflect-metadata@"^0.1.12" from @nestjs/[email protected]
npm ERR!   node_modules/@nestjs/common
npm ERR!     @nestjs/common@"^9.0.0 || ^10.0.0" from the root project
npm ERR!     peer @nestjs/common@"^10.0.0" from @nestjs/[email protected]
npm ERR!     node_modules/@nestjs/core
npm ERR!       @nestjs/core@"^9.0.0 || ^10.0.0" from the root project
npm ERR!       1 more (@nestjs/testing)
npm ERR!     1 more (@nestjs/testing)
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-03-29T04_40_18_630Z-debug-0.log

@renovate renovate bot force-pushed the renovate/reflect-metadata-0.x branch 4 times, most recently from ab9d1c8 to dc6fcd9 Compare January 17, 2024 12:25
@renovate renovate bot force-pushed the renovate/reflect-metadata-0.x branch from dc6fcd9 to d33fe31 Compare February 4, 2024 10:02
@renovate renovate bot force-pushed the renovate/reflect-metadata-0.x branch from d33fe31 to e79af5d Compare March 29, 2024 04:40
@renovate renovate bot changed the title fix(deps): update dependency reflect-metadata to v0.2.1 fix(deps): update dependency reflect-metadata to v0.2.2 Mar 29, 2024
@renovate renovate bot force-pushed the renovate/reflect-metadata-0.x branch from e79af5d to b37f049 Compare May 10, 2024 21:47
@renovate
Copy link
Contributor Author

renovate bot commented May 10, 2024 •
edited
Loading

⚠️ 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: sample/table-storage/package-lock.json
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @nestjs/[email protected]
npm error Found: [email protected]
npm error node_modules/reflect-metadata
npm error   reflect-metadata@"^0.2.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer reflect-metadata@"^0.1.12" from @nestjs/[email protected]
npm error node_modules/@nestjs/common
npm error   @nestjs/common@"^10.0.0" from the root project
npm error   peer @nestjs/common@"^10.0.0" from @nestjs/[email protected]
npm error   node_modules/@nestjs/core
npm error     @nestjs/core@"^10.0.0" from the root project
npm error     2 more (@nestjs/platform-express, @nestjs/testing)
npm error   2 more (@nestjs/platform-express, @nestjs/testing)
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/reflect-metadata
npm error   peer reflect-metadata@"^0.1.12" from @nestjs/[email protected]
npm error   node_modules/@nestjs/common
npm error     @nestjs/common@"^10.0.0" from the root project
npm error     peer @nestjs/common@"^10.0.0" from @nestjs/[email protected]
npm error     node_modules/@nestjs/core
npm error       @nestjs/core@"^10.0.0" from the root project
npm error       2 more (@nestjs/platform-express, @nestjs/testing)
npm error     2 more (@nestjs/platform-express, @nestjs/testing)
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/2024-07-13T15_45_09_205Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-07-13T15_45_09_205Z-debug-0.log
File name: sample/cosmos-db/package-lock.json
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @nestjs/[email protected]
npm error Found: [email protected]
npm error node_modules/reflect-metadata
npm error   reflect-metadata@"^0.2.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer reflect-metadata@"^0.1.12" from @nestjs/[email protected]
npm error node_modules/@nestjs/common
npm error   @nestjs/common@"^10.0.0" from the root project
npm error   peer @nestjs/common@"^10.0.0" from @nestjs/[email protected]
npm error   node_modules/@nestjs/core
npm error     @nestjs/core@"^10.0.0" from the root project
npm error     2 more (@nestjs/platform-express, @nestjs/testing)
npm error   2 more (@nestjs/platform-express, @nestjs/testing)
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/reflect-metadata
npm error   peer reflect-metadata@"^0.1.12" from @nestjs/[email protected]
npm error   node_modules/@nestjs/common
npm error     @nestjs/common@"^10.0.0" from the root project
npm error     peer @nestjs/common@"^10.0.0" from @nestjs/[email protected]
npm error     node_modules/@nestjs/core
npm error       @nestjs/core@"^10.0.0" from the root project
npm error       2 more (@nestjs/platform-express, @nestjs/testing)
npm error     2 more (@nestjs/platform-express, @nestjs/testing)
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/2024-07-13T15_45_14_249Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-07-13T15_45_14_249Z-debug-0.log
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/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/[email protected]
npm ERR! node_modules/@nestjs/common
npm ERR!   @nestjs/common@"^9.0.0 || ^10.0.0" from the root project
npm ERR!   peer @nestjs/common@"^10.0.0" from @nestjs/[email protected]
npm ERR!   node_modules/@nestjs/core
npm ERR!     @nestjs/core@"^9.0.0 || ^10.0.0" from the root project
npm ERR!     1 more (@nestjs/testing)
npm ERR!   1 more (@nestjs/testing)
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/reflect-metadata
npm ERR!   peer reflect-metadata@"^0.1.12" from @nestjs/[email protected]
npm ERR!   node_modules/@nestjs/common
npm ERR!     @nestjs/common@"^9.0.0 || ^10.0.0" from the root project
npm ERR!     peer @nestjs/common@"^10.0.0" from @nestjs/[email protected]
npm ERR!     node_modules/@nestjs/core
npm ERR!       @nestjs/core@"^9.0.0 || ^10.0.0" from the root project
npm ERR!       1 more (@nestjs/testing)
npm ERR!     1 more (@nestjs/testing)
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-07-13T15_45_34_014Z-debug-0.log

@renovate renovate bot force-pushed the renovate/reflect-metadata-0.x branch from b37f049 to b11fb08 Compare May 12, 2024 06:57
@renovate renovate bot force-pushed the renovate/reflect-metadata-0.x branch 2 times, most recently from 5bef9f0 to 7402dcd Compare June 5, 2024 16:44
@renovate renovate bot force-pushed the renovate/reflect-metadata-0.x branch from 7402dcd to 5dfe7ca Compare June 12, 2024 00:54
@renovate renovate bot force-pushed the renovate/reflect-metadata-0.x branch 4 times, most recently from ea412c1 to 145cfd5 Compare July 10, 2024 23:05
@renovate renovate bot force-pushed the renovate/reflect-metadata-0.x branch from 145cfd5 to 53f37c5 Compare July 13, 2024 15:45
@manekinekko manekinekko closed this Sep 5, 2024
@renovate
Copy link
Contributor Author

renovate bot commented Sep 5, 2024

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update (^0.2.0). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps array of your Renovate config.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

@renovate renovate bot deleted the renovate/reflect-metadata-0.x branch September 5, 2024 09:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@manekinekko