fix(deps): switch from deprecated serde_yaml to yaml_serde fork #81

[aviavissar]

Summary

Issue

praxis-proxy/policy#81 — Replace the deprecated serde_yaml crate with the maintained yaml_serde fork (yaml.org).

Closes #81

What was done

A single line was changed in praxis-policy/Cargo.toml (workspace root):

Before:

serde_yaml = "0.9"

After:

# NOTE: serde_yaml is deprecated; using yaml_serde (yaml.org maintained fork) as drop-in.
serde_yaml = { package = "yaml_serde", version = "0.10.4" }

This uses Cargo's package rename feature: the actual crate downloaded from crates.io is yaml_serde, but all source code continues to reference serde_yaml:: unchanged. The 10 member crates inherit the dependency via { workspace = true }, so no other Cargo.toml files needed editing. Zero .rs source files were modified.

Cargo.lock was regenerated by cargo update, pulling in yaml_serde v0.10.7 and its dependency libyaml-rs v0.3.0.

Files changed

• praxis-policy/Cargo.toml — 1 line changed (dependency declaration)
• praxis-policy/Cargo.lock — regenerated automatically

What was verified

Step	Command	Result
Dependency resolution	cargo update	yaml_serde v0.10.7 + libyaml-rs v0.3.0 resolved successfully
Compilation	cargo build --workspace	All crates compiled without errors
Tests	cargo test --workspace	84 test suites passed, 0 failures
Linting	cargo clippy --workspace --all-targets	0 warnings

Prior art

The sibling repo (praxis-proxy/proxy) already completed the same migration using the identical technique (praxis/Cargo.toml line 75-76).

[araujof]

LGTM