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 ^0.2.0 #564

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 14, 2023

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
reflect-metadata (source) ^0.1.14 -> ^0.2.0 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


Configuration

📅 Schedule: Branch creation - "after 8pm every weekday,before 7pm on Sunday" (UTC), 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 Dec 14, 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: @automapper/classes@8.8.1
npm error Found: reflect-metadata@0.2.2
npm error node_modules/reflect-metadata
npm error   reflect-metadata@"^0.2.0" from the root project
npm error   peer reflect-metadata@"^0.1.12 || ^0.2.0" from @nestjs/common@10.3.3
npm error   node_modules/@nestjs/common
npm error     @nestjs/common@"10.3.3" from the root project
npm error     peer @nestjs/common@"^7.0.0 || ^8.0.0 || ^9.0.0 || ^10.0.0" from @automapper/nestjs@8.8.1
npm error     node_modules/@automapper/nestjs
npm error       @automapper/nestjs@"^8.8.1" from the root project
npm error     10 more (@nestjs/apollo, @nestjs/axios, @nestjs/config, ...)
npm error   5 more (@nestjs/core, @nestjs/cqrs, @nestjs/graphql, ...)
npm error
npm error Could not resolve dependency:
npm error peer reflect-metadata@"~0.1.13" from @automapper/classes@8.8.1
npm error node_modules/@automapper/classes
npm error   @automapper/classes@"^8.8.1" from the root project
npm error
npm error Conflicting peer dependency: reflect-metadata@0.1.14
npm error node_modules/reflect-metadata
npm error   peer reflect-metadata@"~0.1.13" from @automapper/classes@8.8.1
npm error   node_modules/@automapper/classes
npm error     @automapper/classes@"^8.8.1" 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/2024-05-09T03_33_48_880Z-eresolve-report.txt

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

@renovate renovate bot force-pushed the renovate/reflect-metadata-0.x branch 23 times, most recently from 46a8642 to 310f194 Compare December 21, 2023 09:16
@renovate renovate bot force-pushed the renovate/reflect-metadata-0.x branch 3 times, most recently from d9318dd to 69bfcf8 Compare December 27, 2023 01:34
@renovate renovate bot force-pushed the renovate/reflect-metadata-0.x branch 9 times, most recently from a11c3d4 to d9e7c2b Compare September 14, 2024 01:23
@renovate renovate bot force-pushed the renovate/reflect-metadata-0.x branch 4 times, most recently from b3ed43d to e79d41e Compare September 21, 2024 01:44
@renovate renovate bot force-pushed the renovate/reflect-metadata-0.x branch 7 times, most recently from 7e90875 to 3641260 Compare September 28, 2024 04:29
@renovate renovate bot force-pushed the renovate/reflect-metadata-0.x branch 6 times, most recently from 90a049b to e3f1530 Compare October 9, 2024 03:50
@renovate renovate bot force-pushed the renovate/reflect-metadata-0.x branch 2 times, most recently from bc490eb to 89120ef Compare October 11, 2024 03:28
@renovate renovate bot force-pushed the renovate/reflect-metadata-0.x branch from 89120ef to 2db31b2 Compare October 12, 2024 00:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants