Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Dec 13, 2023

This PR contains the following updates:

Package Change Age Confidence
reflect-metadata (source) 0.1.14 -> 0.2.2 age 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


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
Copy link
Contributor Author

renovate bot commented Dec 13, 2023

⚠ 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 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   dev reflect-metadata@"0.2.2" 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   dev @nestjs/common@"9.4.3" from the root project
npm error   peer @nestjs/common@"^9.0.0" from @nestjs/[email protected]
npm error   node_modules/@nestjs/core
npm error     dev @nestjs/core@"9.4.3" from the root project
npm error     2 more (@nestjs/microservices, @nestjs/testing)
npm error   2 more (@nestjs/microservices, @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     dev @nestjs/common@"9.4.3" from the root project
npm error     peer @nestjs/common@"^9.0.0" from @nestjs/[email protected]
npm error     node_modules/@nestjs/core
npm error       dev @nestjs/core@"9.4.3" from the root project
npm error       2 more (@nestjs/microservices, @nestjs/testing)
npm error     2 more (@nestjs/microservices, @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-05-08T01_37_09_780Z-eresolve-report.txt

npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-05-08T01_37_09_780Z-debug-0.log

@renovate renovate bot force-pushed the renovate/reflect-metadata-0.x branch from ae9f419 to 75c8b0c Compare December 14, 2023 20:56
@renovate renovate bot changed the title chore(deps): update dependency reflect-metadata to v0.2.0 chore(deps): update dependency reflect-metadata to v0.2.1 Dec 14, 2023
@renovate renovate bot force-pushed the renovate/reflect-metadata-0.x branch 4 times, most recently from 6e9a9df to 8523ddc Compare December 20, 2023 12:47
@renovate renovate bot force-pushed the renovate/reflect-metadata-0.x branch 3 times, most recently from 27e19e7 to 9361a6b Compare January 3, 2024 00:14
@renovate renovate bot force-pushed the renovate/reflect-metadata-0.x branch 6 times, most recently from a44ce19 to 18db182 Compare January 12, 2024 12:44
@renovate renovate bot force-pushed the renovate/reflect-metadata-0.x branch 5 times, most recently from 91308c5 to c32c38e Compare January 19, 2024 19:24
@renovate renovate bot force-pushed the renovate/reflect-metadata-0.x branch 7 times, most recently from 81f4e77 to 9c475f2 Compare January 30, 2024 03:21
@renovate renovate bot force-pushed the renovate/reflect-metadata-0.x branch 2 times, most recently from e7e280c to 74022d8 Compare January 31, 2024 09:03
@renovate renovate bot force-pushed the renovate/reflect-metadata-0.x branch 6 times, most recently from 5d5e92b to 52c0e96 Compare October 1, 2025 21:06
@renovate renovate bot force-pushed the renovate/reflect-metadata-0.x branch 4 times, most recently from 46512e6 to 597191a Compare October 8, 2025 06:55
@renovate renovate bot force-pushed the renovate/reflect-metadata-0.x branch 5 times, most recently from 5910c1c to 1614dd4 Compare October 15, 2025 06:32
@renovate renovate bot force-pushed the renovate/reflect-metadata-0.x branch 7 times, most recently from e76af7c to 15930c4 Compare October 24, 2025 23:15
@renovate renovate bot force-pushed the renovate/reflect-metadata-0.x branch 6 times, most recently from b47fe49 to ff45cd5 Compare November 6, 2025 03:45
@renovate renovate bot force-pushed the renovate/reflect-metadata-0.x branch from ff45cd5 to fce60ff Compare November 7, 2025 11:42
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.

1 participant