Skip to content

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 19, 2025

This PR contains the following updates:

Package Type Update Change
serde_json dependencies patch 1.0.142 -> 1.0.145

Release Notes

serde-rs/json (serde_json)

v1.0.145

Compare Source

  • Raise serde version requirement to >=1.0.220

v1.0.144

Compare Source

  • Switch serde dependency to serde_core (#​1285)

v1.0.143

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 becomes conflicted, 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 changed the title fix(deps): update rust crate serde_json to v1.0.143 fix(deps): update rust crate serde_json to v1.0.144 Sep 14, 2025
@renovate renovate bot force-pushed the renovate/serde_json-1.x-lockfile branch from 45d09c0 to bce282b Compare September 14, 2025 02:00
@renovate renovate bot force-pushed the renovate/serde_json-1.x-lockfile branch from bce282b to c9a0ca3 Compare September 14, 2025 17:00
@renovate renovate bot changed the title fix(deps): update rust crate serde_json to v1.0.144 fix(deps): update rust crate serde_json to v1.0.145 Sep 14, 2025
@renovate renovate bot changed the title fix(deps): update rust crate serde_json to v1.0.145 chore(deps): update rust crate serde_json to v1.0.145 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 raiden/Cargo.toml --package [email protected] --precise 1.0.145
warning: virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
note: to keep the current resolver, specify `workspace.resolver = "1"` in the workspace root's manifest
note: to use the edition 2021 resolver, specify `workspace.resolver = "2"` in the workspace root's manifest
note: for more details see https://doc.rust-lang.org/cargo/reference/resolver.html#resolver-versions
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