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.5.0 #2161

Merged
merged 2 commits into from
Nov 7, 2024
Merged

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 7, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@swc/cli ^0.4.0 -> ^0.5.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:

@renovate renovate bot enabled auto-merge (squash) November 7, 2024 03:05
Copy link
Contributor Author

renovate bot commented Nov 7, 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: backend/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: @swc/[email protected]
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/[email protected]
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/[email protected]
npm error node_modules/@swc/cli
npm error   peerOptional @swc/cli@"^0.1.62 || ^0.3.0 || ^0.4.0" from @nestjs/[email protected]
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-07T03_05_37_994Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-11-07T03_05_37_994Z-debug-0.log

Copy link
Contributor Author

renovate bot commented Nov 7, 2024

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

@renovate renovate bot merged commit e6ef0aa into main Nov 7, 2024
24 checks passed
@renovate renovate bot deleted the renovate/nestjs branch November 7, 2024 03:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

1 participant