build(deps): Update Rust crate serde_yaml to 0.9.34 - autoclosed

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
serde_yaml	workspace.dependencies	patch	0.9 -> 0.9.34

---

Release Notes

dtolnay/serde-yaml (serde_yaml)

v0.9.34

Compare Source

As of this release, I am not planning to publish further versions of serde_yaml as none of my projects have been using YAML for a long time, so I have archived the GitHub repo and marked the crate deprecated in the version number. An official replacement isn't designated for those who still need to work with YAML, but https://crates.io/search?q=yaml\&sort=relevance and https://crates.io/keywords/yaml has a number of reasonable-looking options available.

v0.9.33

Compare Source

• Fix quadratic parse time for YAML containing deeply nested flow collections (https://github.com/dtolnay/unsafe-libyaml/issues/26)

---

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 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 Cargo.toml --package [email protected] --precise 0.9.34
error: package ID specification `[email protected]` did not match any packages
Did you mean one of these?

  [email protected]+deprecated