You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
RUSTSEC-2026-0543, published 2026-11-17, marks chrono as unmaintained (all versions). It is an unmaintained advisory, not a vulnerability. Minigraf depends on chrono 0.4.45 directly (Cargo.toml, serde + std, no default features); no other dependency pulls it in.
cargo-deny (policy.yml) fails on it, so every PR on main and v3 went red. The advisory is ignored in deny.toml on both branches as a stopgap, with a comment pointing here.
Where chrono is used
src/temporal.rs (UTC-only timestamp parsing, which already avoids chrono's local-timezone code, GHSA-wcg3-cvx6-7396) and timestamp handling in src/db.rs, src/graph/, src/browser/.
To do
Replace chrono with a maintained crate; the advisory names jiff and time. Pick on binary size (1,250 KiB gate on v3) and wasm32 support.
Keep parsing results identical (UTC only, same accepted formats); add tests for the accepted forms first.
Remove the deny.toml ignore on the branch that drops chrono. Backport to main only if the support policy calls for it.
Activity
ci: ignore the chrono unmaintained advisory until it is replaced (#900)…
Merge pull request #901 from project-minigraf/ci/900-chrono-advisory-v3