Skip to content

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 29, 2025

This PR contains the following updates:

Package Type Update Change
chrono dependencies patch 0.4.40 -> 0.4.42

Release Notes

chronotope/chrono (chrono)

v0.4.42: 0.4.42

Compare Source

What's Changed

v0.4.41

Compare Source

What's Changed


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 force-pushed the renovate/chrono-0.x-lockfile branch from ca9976e to 1c4cc17 Compare May 23, 2025 19:11
@renovate renovate bot force-pushed the renovate/chrono-0.x-lockfile branch from 1c4cc17 to 777e5a5 Compare June 19, 2025 06:45
@rohanku rohanku force-pushed the main branch 2 times, most recently from 844a025 to 7a55f75 Compare June 20, 2025 20:44
@renovate renovate bot force-pushed the renovate/chrono-0.x-lockfile branch from 777e5a5 to 411a3f4 Compare September 8, 2025 10:43
@renovate renovate bot changed the title fix(deps): update rust crate chrono to v0.4.41 fix(deps): update rust crate chrono to v0.4.42 Sep 8, 2025
@renovate renovate bot changed the title fix(deps): update rust crate chrono to v0.4.42 chore(deps): update rust crate chrono to v0.4.42 Sep 25, 2025
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 libs/gds/Cargo.toml --package [email protected] --precise 0.4.42
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