Latest Results
chore: drop `serde_yaml` rename (#2015)
* chore(deps): drop serde_yaml rename, use yaml_serde directly
The workspace currently aliases yaml_serde 0.10 as serde_yaml via
Cargo package renaming. This was a useful porting convenience when
migrating away from the deprecated serde_yaml 0.9, but now that the
migration is complete it actively confuses readers: the manifest says
serde_yaml, the source says serde_yaml::Value, but the actual crate
is yaml_serde.
This bit downstream consumers of yamlpatch 1.25.0, whose public
Op::Replace(serde_yaml::Value) signature is in fact
Op::Replace(yaml_serde::Value) due to this same rename. Downstream
code that constructed a real serde_yaml::Value saw an unreadable
"expected yaml_serde::Value, found serde_yaml::Value" error.
Switch the workspace dependency from serde_yaml = { package =
"yaml_serde", version = "0.10" } to yaml_serde = "0.10" and rename
all ~249 source references from serde_yaml:: to yaml_serde::. This
brings the manifest, source code, and compiler diagnostics into
agreement.
No behavior change. cargo check, cargo fmt --check, and the
non-network-dependent test suites pass on the workspace.
* chore: add .git-blame-ignore-revs for mechanical rename
Lists the serde_yaml -> yaml_serde rename commit so `git blame` and
GitHub's blame view skip it and surface the prior author of each
touched line instead. Run once locally to opt in:
git config blame.ignoreRevsFile .git-blame-ignore-revs
GitHub honors the file automatically. Latest Branches
+49%
×2.1
-35%
trail-of-forks:dm/remove-ids © 2026 CodSpeed Technology