Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Jan 1, 2025

This PR contains the following updates:

Package Type Update Change
dyn-clone workspace.dependencies patch 1.0.16 -> 1.0.20

Release Notes

dtolnay/dyn-clone (dyn-clone)

v1.0.20

Compare Source

v1.0.19

Compare Source

  • Documentation improvements

v1.0.18

Compare Source

  • Documentation improvements

v1.0.17

Compare Source

  • Work around non_local_definitions warning being triggered in macro-generated impl in clone_trait_object! with rustc 1.78-nightly (#​28)

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.

@renovate renovate bot force-pushed the renovate/dyn-clone-1.x-lockfile branch from 6eca42a to 51dbe18 Compare February 1, 2025 04:28
@renovate renovate bot changed the title Update Rust crate dyn-clone to v1.0.17 Update Rust crate dyn-clone to v1.0.18 Feb 1, 2025
@renovate renovate bot force-pushed the renovate/dyn-clone-1.x-lockfile branch from 51dbe18 to 90ebf47 Compare March 4, 2025 02:00
@renovate renovate bot changed the title Update Rust crate dyn-clone to v1.0.18 Update Rust crate dyn-clone to v1.0.19 Mar 4, 2025
@renovate renovate bot force-pushed the renovate/dyn-clone-1.x-lockfile branch from 90ebf47 to 22e7fcb Compare July 27, 2025 20:27
@renovate renovate bot changed the title Update Rust crate dyn-clone to v1.0.19 Update Rust crate dyn-clone to v1.0.20 Jul 27, 2025
@renovate
Copy link
Contributor Author

renovate bot commented Sep 25, 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: Cargo.lock
Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path Cargo.toml --package [email protected] --precise 1.0.20
error: failed to acquire package cache lock

Caused by:
  failed to open: /home/ubuntu/.cargo/.package-cache

Caused by:
  failed to create directory `/home/ubuntu/.cargo`

Caused by:
  File exists (os error 17)

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