Skip to content

Update Rust crate toml to v1#71

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/toml-1.x
Open

Update Rust crate toml to v1#71
renovate[bot] wants to merge 1 commit intomainfrom
renovate/toml-1.x

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Feb 11, 2026

This PR contains the following updates:

Package Type Update Change
toml dependencies major 0.91.0

Release Notes

toml-rs/toml (toml)

v1.0.1

Compare Source

v1.0.0

Compare Source

v0.9.12

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
Copy link
Contributor Author

renovate bot commented Feb 11, 2026

⚠️ 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 xtask/Cargo.toml --package toml@0.9.11+spec-1.1.0 --precise 1.0.1
error: package ID specification `toml@0.9.11+spec-1.1.0` did not match any packages
help: there are similar package ID specifications:

  toml@1.0.1+spec-1.1.0

@renovate renovate bot force-pushed the renovate/toml-1.x branch from d6f6082 to fe7ef6a Compare February 12, 2026 19:34
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