Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Jun 21, 2024

This PR contains the following updates:

Package Type Update Change
lazy_static dependencies minor 1.4.0 -> 1.5.0

Release Notes

rust-lang-nursery/lazy-static.rs (lazy_static)

v1.5.0

Compare Source


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 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 requested a review from Pandapip1 as a code owner June 21, 2024 23:15
@renovate renovate bot force-pushed the renovate/lazy_static-1.x-lockfile branch 2 times, most recently from f0bde01 to 5127101 Compare September 17, 2024 18:43
@renovate renovate bot force-pushed the renovate/lazy_static-1.x-lockfile branch 11 times, most recently from e604290 to c0a7d52 Compare August 15, 2025 13:31
@renovate renovate bot force-pushed the renovate/lazy_static-1.x-lockfile branch from c0a7d52 to ecda845 Compare August 17, 2025 12:52
@renovate renovate bot force-pushed the renovate/lazy_static-1.x-lockfile branch 2 times, most recently from a45676d to d83efd9 Compare September 7, 2025 02:26
@renovate renovate bot force-pushed the renovate/lazy_static-1.x-lockfile branch from d83efd9 to 42d2e57 Compare September 15, 2025 03:19
@renovate renovate bot force-pushed the renovate/lazy_static-1.x-lockfile branch from 42d2e57 to 892d91d Compare September 15, 2025 03:21
@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.5.0
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