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 @swc/cli to ^0.6.0 #2238

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 16, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@swc/cli ^0.5.0 -> ^0.6.0 age adoption passing confidence

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.


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:

Copy link
Contributor Author

renovate bot commented Jan 16, 2025

⚠️ 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: backend/package-lock.json
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @nestjs/cli@10.4.9
npm error Found: @swc/cli@0.6.0
npm error node_modules/@swc/cli
npm error   dev @swc/cli@"^0.6.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 || ^0.5.0" from @nestjs/cli@10.4.9
npm error node_modules/@nestjs/cli
npm error   @nestjs/cli@"^10.4.9" from the root project
npm error
npm error Conflicting peer dependency: @swc/cli@0.5.2
npm error node_modules/@swc/cli
npm error   peerOptional @swc/cli@"^0.1.62 || ^0.3.0 || ^0.4.0 || ^0.5.0" from @nestjs/cli@10.4.9
npm error   node_modules/@nestjs/cli
npm error     @nestjs/cli@"^10.4.9" 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-18T17_25_16_639Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2025-01-18T17_25_16_639Z-debug-0.log

@renovate renovate bot enabled auto-merge (squash) January 16, 2025 05:06
@renovate renovate bot force-pushed the renovate/nestjs branch 5 times, most recently from ae6a944 to 2c371af Compare January 18, 2025 17:21
@renovate renovate bot force-pushed the renovate/nestjs branch from 2c371af to 34e43ac Compare January 18, 2025 17:25
auto-merge was automatically disabled January 18, 2025 17:54

Pull request was closed

Copy link
Contributor Author

renovate bot commented Jan 18, 2025

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update (^0.6.0). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps array of your Renovate config.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

@renovate renovate bot deleted the renovate/nestjs branch January 18, 2025 17:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

1 participant