chore(deps): update rust crate toml to v1 #27

Open
renovate wants to merge 1 commit from renovate/toml-1.x into main
Collaborator

This PR contains the following updates:

Package Type Update Change
toml dependencies major 0.9.01.0.0

Release Notes

toml-rs/toml (toml)

v1.1.5

Compare Source

v1.1.4

Compare Source

v1.1.3

Compare Source

v1.1.2

Compare Source

v1.1.1

Compare Source

v1.1.0

Compare Source

v1.0.7

Compare Source

v1.0.6

Compare Source

v1.0.5

Compare Source

v1.0.4

Compare Source

v1.0.3

Compare Source

v1.0.2

Compare Source

v1.0.1

Compare Source

v1.0.0

Compare Source

v0.9.12

Compare Source


Configuration

📅 Schedule: (UTC)

  • 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 has been generated by Mend Renovate CLI.

This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [toml](https://github.com/toml-rs/toml) | dependencies | major | `0.9.0` → `1.0.0` | --- ### Release Notes <details> <summary>toml-rs/toml (toml)</summary> ### [`v1.1.5`](https://github.com/toml-rs/toml/compare/toml-v1.1.4...toml-v1.1.5) [Compare Source](https://github.com/toml-rs/toml/compare/toml-v1.1.4...toml-v1.1.5) ### [`v1.1.4`](https://github.com/toml-rs/toml/compare/toml-v1.1.3...toml-v1.1.4) [Compare Source](https://github.com/toml-rs/toml/compare/toml-v1.1.3...toml-v1.1.4) ### [`v1.1.3`](https://github.com/toml-rs/toml/compare/toml-v1.1.2...toml-v1.1.3) [Compare Source](https://github.com/toml-rs/toml/compare/toml-v1.1.2...toml-v1.1.3) ### [`v1.1.2`](https://github.com/toml-rs/toml/compare/toml-v1.1.1...toml-v1.1.2) [Compare Source](https://github.com/toml-rs/toml/compare/toml-v1.1.1...toml-v1.1.2) ### [`v1.1.1`](https://github.com/toml-rs/toml/compare/toml-v1.1.0...toml-v1.1.1) [Compare Source](https://github.com/toml-rs/toml/compare/toml-v1.1.0...toml-v1.1.1) ### [`v1.1.0`](https://github.com/toml-rs/toml/compare/toml-v1.0.7...toml-v1.1.0) [Compare Source](https://github.com/toml-rs/toml/compare/toml-v1.0.7...toml-v1.1.0) ### [`v1.0.7`](https://github.com/toml-rs/toml/compare/toml-v1.0.6...toml-v1.0.7) [Compare Source](https://github.com/toml-rs/toml/compare/toml-v1.0.6...toml-v1.0.7) ### [`v1.0.6`](https://github.com/toml-rs/toml/compare/toml-v1.0.5...toml-v1.0.6) [Compare Source](https://github.com/toml-rs/toml/compare/toml-v1.0.5...toml-v1.0.6) ### [`v1.0.5`](https://github.com/toml-rs/toml/compare/toml-v1.0.4...toml-v1.0.5) [Compare Source](https://github.com/toml-rs/toml/compare/toml-v1.0.4...toml-v1.0.5) ### [`v1.0.4`](https://github.com/toml-rs/toml/compare/toml-v1.0.3...toml-v1.0.4) [Compare Source](https://github.com/toml-rs/toml/compare/toml-v1.0.3...toml-v1.0.4) ### [`v1.0.3`](https://github.com/toml-rs/toml/compare/toml-v1.0.2...toml-v1.0.3) [Compare Source](https://github.com/toml-rs/toml/compare/toml-v1.0.2...toml-v1.0.3) ### [`v1.0.2`](https://github.com/toml-rs/toml/compare/toml-v1.0.1...toml-v1.0.2) [Compare Source](https://github.com/toml-rs/toml/compare/toml-v1.0.1...toml-v1.0.2) ### [`v1.0.1`](https://github.com/toml-rs/toml/compare/toml-v1.0.0...toml-v1.0.1) [Compare Source](https://github.com/toml-rs/toml/compare/toml-v1.0.0...toml-v1.0.1) ### [`v1.0.0`](https://github.com/toml-rs/toml/compare/toml-v0.9.12...toml-v1.0.0) [Compare Source](https://github.com/toml-rs/toml/compare/toml-v0.9.12...toml-v1.0.0) ### [`v0.9.12`](https://github.com/toml-rs/toml/compare/toml-v0.9.11...toml-v0.9.12) [Compare Source](https://github.com/toml-rs/toml/compare/toml-v0.9.11...toml-v0.9.12) </details> --- ### Configuration 📅 **Schedule**: (UTC) - 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. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate CLI](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My4wLjkiLCJ1cGRhdGVkSW5WZXIiOiI0NC4zMC4yIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119-->
chore(deps): update rust crate toml to v1
All checks were successful
ci/woodpecker/pr/test Pipeline was successful
275321da68
renovate force-pushed renovate/toml-1.x from 275321da68
All checks were successful
ci/woodpecker/pr/test Pipeline was successful
to 75fc0c04c3
All checks were successful
ci/woodpecker/pr/test Pipeline was successful
2026-03-16 21:16:08 +00:00
Compare
renovate changed title from chore(deps): update rust crate toml to v1 to Update Rust crate toml to v1 2026-04-04 00:28:51 +00:00
renovate changed title from Update Rust crate toml to v1 to chore(deps): update rust crate toml to v1 2026-04-05 05:02:17 +00:00
renovate changed title from chore(deps): update rust crate toml to v1 to Update Rust crate toml to v1 2026-04-05 09:47:49 +00:00
renovate changed title from Update Rust crate toml to v1 to chore(deps): update rust crate toml to v1 2026-04-05 20:17:38 +00:00
Author
Collaborator

⚠️ 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 --workspace
    Updating crates.io index
    Updating git repository `https://git.hydrar.de/jmarya/cmdbind`
fatal: unable to access 'https://git.hydrar.de/jmarya/cmdbind/': Failed to connect to git.hydrar.de port 443 after 2581 ms: Couldn't connect to server
warning: spurious network error (3 tries remaining): process didn't exit successfully: `git fetch --tags --force --update-head-ok 'https://git.hydrar.de/jmarya/cmdbind' '+refs/heads/*:refs/remotes/origin/*' '+HEAD:refs/remotes/origin/HEAD'` (exit status: 128)
fatal: unable to access 'https://git.hydrar.de/jmarya/cmdbind/': Failed to connect to git.hydrar.de port 443 after 134798 ms: Couldn't connect to server
warning: spurious network error (2 tries remaining): process didn't exit successfully: `git fetch --tags --force --update-head-ok 'https://git.hydrar.de/jmarya/cmdbind' '+refs/heads/*:refs/remotes/origin/*' '+HEAD:refs/remotes/origin/HEAD'` (exit status: 128)
fatal: unable to access 'https://git.hydrar.de/jmarya/cmdbind/': Failed to connect to git.hydrar.de port 443 after 4761 ms: Couldn't connect to server
warning: spurious network error (1 try remaining): process didn't exit successfully: `git fetch --tags --force --update-head-ok 'https://git.hydrar.de/jmarya/cmdbind' '+refs/heads/*:refs/remotes/origin/*' '+HEAD:refs/remotes/origin/HEAD'` (exit status: 128)
fatal: unable to access 'https://git.hydrar.de/jmarya/cmdbind/': Failed to connect to git.hydrar.de port 443 after 2759 ms: Couldn't connect to server
error: failed to get `cmdbind` as a dependency of package `bk v0.2.2 (/tmp/renovate/repos/forgejo/jmarya/bk)`

Caused by:
  failed to load source for dependency `cmdbind`

Caused by:
  unable to update https://git.hydrar.de/jmarya/cmdbind#a24deb32

Caused by:
  failed to fetch into: /home/ubuntu/.cargo/git/db/cmdbind-a450787ae50b555f

Caused by:
  process didn't exit successfully: `git fetch --tags --force --update-head-ok 'https://git.hydrar.de/jmarya/cmdbind' '+refs/heads/*:refs/remotes/origin/*' '+HEAD:refs/remotes/origin/HEAD'` (exit status: 128)

### ⚠️ 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 --workspace Updating crates.io index Updating git repository `https://git.hydrar.de/jmarya/cmdbind` fatal: unable to access 'https://git.hydrar.de/jmarya/cmdbind/': Failed to connect to git.hydrar.de port 443 after 2581 ms: Couldn't connect to server warning: spurious network error (3 tries remaining): process didn't exit successfully: `git fetch --tags --force --update-head-ok 'https://git.hydrar.de/jmarya/cmdbind' '+refs/heads/*:refs/remotes/origin/*' '+HEAD:refs/remotes/origin/HEAD'` (exit status: 128) fatal: unable to access 'https://git.hydrar.de/jmarya/cmdbind/': Failed to connect to git.hydrar.de port 443 after 134798 ms: Couldn't connect to server warning: spurious network error (2 tries remaining): process didn't exit successfully: `git fetch --tags --force --update-head-ok 'https://git.hydrar.de/jmarya/cmdbind' '+refs/heads/*:refs/remotes/origin/*' '+HEAD:refs/remotes/origin/HEAD'` (exit status: 128) fatal: unable to access 'https://git.hydrar.de/jmarya/cmdbind/': Failed to connect to git.hydrar.de port 443 after 4761 ms: Couldn't connect to server warning: spurious network error (1 try remaining): process didn't exit successfully: `git fetch --tags --force --update-head-ok 'https://git.hydrar.de/jmarya/cmdbind' '+refs/heads/*:refs/remotes/origin/*' '+HEAD:refs/remotes/origin/HEAD'` (exit status: 128) fatal: unable to access 'https://git.hydrar.de/jmarya/cmdbind/': Failed to connect to git.hydrar.de port 443 after 2759 ms: Couldn't connect to server error: failed to get `cmdbind` as a dependency of package `bk v0.2.2 (/tmp/renovate/repos/forgejo/jmarya/bk)` Caused by: failed to load source for dependency `cmdbind` Caused by: unable to update https://git.hydrar.de/jmarya/cmdbind#a24deb32 Caused by: failed to fetch into: /home/ubuntu/.cargo/git/db/cmdbind-a450787ae50b555f Caused by: process didn't exit successfully: `git fetch --tags --force --update-head-ok 'https://git.hydrar.de/jmarya/cmdbind' '+refs/heads/*:refs/remotes/origin/*' '+HEAD:refs/remotes/origin/HEAD'` (exit status: 128) ```
renovate force-pushed renovate/toml-1.x from 75fc0c04c3
All checks were successful
ci/woodpecker/pr/test Pipeline was successful
to 2e8c3b4a87
Some checks failed
renovate/artifacts Artifact file update failure
ci/woodpecker/pr/test Pipeline is running
2026-04-17 22:20:30 +00:00
Compare
Some checks failed
renovate/artifacts Artifact file update failure
ci/woodpecker/pr/test Pipeline is running
This pull request can be merged automatically.
This branch is out-of-date with the base branch
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin renovate/toml-1.x:renovate/toml-1.x
git switch renovate/toml-1.x

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch main
git merge --no-ff renovate/toml-1.x
git switch renovate/toml-1.x
git rebase main
git switch main
git merge --ff-only renovate/toml-1.x
git switch renovate/toml-1.x
git rebase main
git switch main
git merge --no-ff renovate/toml-1.x
git switch main
git merge --squash renovate/toml-1.x
git switch main
git merge --ff-only renovate/toml-1.x
git switch main
git merge renovate/toml-1.x
git push origin main
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
jmarya/bk!27
No description provided.