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 #523

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 18, 2023

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.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: 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 - "before 4am on Monday" (UTC), 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 renovate bot requested a review from MarcMogdanz December 18, 2023 03:54
Copy link
Contributor Author

renovate bot commented Dec 18, 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 ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @narando/nest-axios-interceptor@2.2.0
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.13" from @narando/nest-axios-interceptor@2.2.0
npm ERR! node_modules/@narando/nest-axios-interceptor
npm ERR!   @narando/nest-axios-interceptor@"2.2.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 @narando/nest-axios-interceptor@2.2.0
npm ERR!   node_modules/@narando/nest-axios-interceptor
npm ERR!     @narando/nest-axios-interceptor@"2.2.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-03-29T03_50_34_383Z-debug-0.log

@renovate renovate bot force-pushed the renovate/reflect-metadata-0.x branch from def2601 to 96774f6 Compare March 29, 2024 03:50
@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
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