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

fix(deps): update dependency cache-manager to v6 #905

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 11, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
cache-manager (source) ^5.7.6 -> ^6.0.0 age adoption passing confidence
cache-manager (source) 5.7.6 -> 6.3.2 age adoption passing confidence

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

⚠️ 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/cache-manager
npm error   dev cache-manager@"6.3.2" from the root project
npm error   cache-manager@"^6.0.0" from @anchan828/[email protected]
npm error   packages/cache
npm error     @anchan828/[email protected]
npm error     node_modules/@anchan828/nest-cache
npm error       workspace packages/cache from the root project
npm error   4 more (@anchan828/nest-cache-common, ...)
npm error
npm error Could not resolve dependency:
npm error peer cache-manager@"<=5" from @nestjs/[email protected]
npm error node_modules/@nestjs/cache-manager
npm error   dev @nestjs/cache-manager@"2.3.0" from the root project
npm error   dev @nestjs/cache-manager@"2.3.0" from @anchan828/[email protected]
npm error   packages/cache
npm error     @anchan828/[email protected]
npm error     node_modules/@anchan828/nest-cache
npm error       workspace packages/cache from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/cache-manager
npm error   peer cache-manager@"<=5" from @nestjs/[email protected]
npm error   node_modules/@nestjs/cache-manager
npm error     dev @nestjs/cache-manager@"2.3.0" from the root project
npm error     dev @nestjs/cache-manager@"2.3.0" from @anchan828/[email protected]
npm error     packages/cache
npm error       @anchan828/[email protected]
npm error       node_modules/@anchan828/nest-cache
npm error         workspace packages/cache 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/2025-01-05T04_08_01_765Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2025-01-05T04_08_01_765Z-debug-0.log

@renovate renovate bot force-pushed the renovate/cache-manager-6.x branch from e1e08d8 to d4fa5f0 Compare October 13, 2024 04:07
@renovate renovate bot force-pushed the renovate/cache-manager-6.x branch 3 times, most recently from 70c2b64 to ad60dea Compare October 22, 2024 00:17
@renovate renovate bot force-pushed the renovate/cache-manager-6.x branch 2 times, most recently from 0d3182a to 4f3f048 Compare October 30, 2024 20:19
@renovate renovate bot force-pushed the renovate/cache-manager-6.x branch 3 times, most recently from 6133c33 to 414c187 Compare November 10, 2024 04:07
@renovate renovate bot force-pushed the renovate/cache-manager-6.x branch 2 times, most recently from 6945662 to 9939e8b Compare November 17, 2024 04:08
@renovate renovate bot force-pushed the renovate/cache-manager-6.x branch 3 times, most recently from d92719a to ffb2ba0 Compare November 27, 2024 01:19
@renovate renovate bot force-pushed the renovate/cache-manager-6.x branch 4 times, most recently from 1ea13f2 to dc25903 Compare December 8, 2024 04:08
@renovate renovate bot force-pushed the renovate/cache-manager-6.x branch 3 times, most recently from ce3be57 to ae73f56 Compare December 17, 2024 01:43
@renovate renovate bot force-pushed the renovate/cache-manager-6.x branch from ae73f56 to 6455219 Compare December 22, 2024 04:08
@renovate renovate bot force-pushed the renovate/cache-manager-6.x branch 2 times, most recently from 0b0b973 to 8be5c5a Compare December 30, 2024 00:25
@renovate renovate bot force-pushed the renovate/cache-manager-6.x branch from 8be5c5a to 247deaf Compare January 5, 2025 04:08
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