Ignore chrono's unmaintained advisory until replacing it is its own release

Merged
JE
3d ago
+7-1

RUSTSEC-2026-0543 (published today) marks chrono unmaintained. It reports no vulnerability, and no chrono release addresses it, yet cargo deny fails the Rust Tests job on every PR because of it (first seen on #306).

chrono is part of the crate's public API: types::DateTime is chrono::DateTime<Utc>, and Date parses with chrono. Switching to jiff or time is therefore a breaking 0.MINOR release in its own right, not a lockfile bump. This PR adds the advisory to deny.toml's ignore list, with the reason and the point at which to revisit it, using the format the file's header already asks for.

make deny in rust/: advisories ok, bans ok, licenses ok, sources ok.


Summary by cubic

cargo deny fails on every PR because RUSTSEC-2026-0543 marks chrono unmaintained despite reporting no vulnerability. This PR ignores that advisory in rust/deny.toml with a reason and a revisit point, since replacing chrono is a breaking 0.MINOR release of its own (types::DateTime is chrono::DateTime<Utc>, and Date parses with chrono — it's in the crate's public API).