fix(deps): update all non-major dependencies - autoclosed

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
anyhow	dependencies	patch	1.0.68 -> 1.0.79
camino	dependencies	patch	1.0 -> 1.1
camino	dependencies	patch	1.0.4 -> 1.1.6
chrono	dependencies	patch	0.4.23 -> 0.4.33
clap	dependencies	patch	4.2 -> 4.5
fn-error-context	dependencies	patch	0.2.0 -> 0.2.1
gvariant	dependencies	minor	0.4.0 -> 0.5.0
hex	dependencies	patch	^0.4 -> ^0.4.3
indicatif	dependencies	patch	0.17.0 -> 0.17.7
libc	dependencies	patch	^0.2 -> ^0.2.153
libc	dependencies	patch	0.2.92 -> 0.2.153
log	dependencies	patch	0.4.0 -> 0.4.20
once_cell	dependencies	patch	1.9 -> 1.19
openssl	dependencies	patch	^0.10 -> ^0.10.63
regex	dependencies	patch	1.7.1 -> 1.10.3
schemars (source)	dependencies	patch	0.8.6 -> 0.8.16
serde (source)	dependencies	patch	1.0.125 -> 1.0.196
serde_ignored	dependencies	patch	0.1.9 -> 0.1.10
serde_json	dependencies	patch	1.0.64 -> 1.0.113
serde_with	dependencies	patch	>= 1.9.4, < 2 -> >= 1.14.0, < 2
serde_yaml	dependencies	patch	0.9.17 -> 0.9.31
tempfile (source)	dependencies	patch	3.3 -> 3.10
tempfile (source)	dependencies	patch	3.3.0 -> 3.10.0
tokio (source)	dependencies	patch	>= 1.13.0 -> >= 1.36.0
toml	dependencies	minor	0.7.2 -> 0.8.10
uuid	dependencies	patch	1.2.2 -> 1.7.0

---

Release Notes

wmanley/gvariant-rs (gvariant)

v0.5.0

Compare Source

toml-rs/toml (toml)

v0.8.10

Compare Source

v0.8.9

Compare Source

v0.8.8

Compare Source

v0.8.7

Compare Source

v0.8.6

Compare Source

v0.8.5

Compare Source

v0.8.4

Compare Source

v0.8.3

Compare Source

v0.8.2

Compare Source

v0.8.1

Compare Source

v0.8.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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[renovate]

⚠ 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 lib/Cargo.toml --package [email protected] --precise 0.5.0
    Updating crates.io index
error: failed to select a version for the requirement `gvariant = "^0.4.0"`
candidate versions found which didn't match: 0.5.0
location searched: crates.io index
required by package `ostree-ext v0.13.1`
    ... which satisfies dependency `ostree-ext = "^0.13"` (locked to 0.13.1) of package `bootc-lib v0.1.0 (/tmp/renovate/repos/github/containers/bootc/lib)`
    ... which satisfies path dependency `bootc-lib` (locked to 0.1.0) of package `bootc v0.1.0 (/tmp/renovate/repos/github/containers/bootc/cli)`
perhaps a crate was updated and forgotten to be re-vendored?

[openshift-ci]

Hi @renovate[bot]. Thanks for your PR.

I'm waiting for a containers member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.