Closed renovate[bot] closed 2 weeks ago
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:
The artifact failure details are included below:
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @nestjs/cli@10.4.5
npm error Found: @swc/cli@0.5.0
npm error node_modules/@swc/cli
npm error dev @swc/cli@"^0.5.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peerOptional @swc/cli@"^0.1.62 || ^0.3.0 || ^0.4.0" from @nestjs/cli@10.4.5
npm error node_modules/@nestjs/cli
npm error @nestjs/cli@"^10.1.16" from the root project
npm error
npm error Conflicting peer dependency: @swc/cli@0.4.0
npm error node_modules/@swc/cli
npm error peerOptional @swc/cli@"^0.1.62 || ^0.3.0 || ^0.4.0" from @nestjs/cli@10.4.5
npm error node_modules/@nestjs/cli
npm error @nestjs/cli@"^10.1.16" 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-11-06T20_20_44_973Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-11-06T20_20_44_973Z-debug-0.log
This PR contains the following updates:
^0.4.0
->^0.5.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.
This PR was generated by Mend Renovate. View the repository job log.
Thanks for the PR!
Deployments, as required, will be available below:
Please create PRs in draft mode. Mark as ready to enable:
After merge, new images are deployed in: