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
{{ message }}
Repository navigation
Replace the unmaintained chrono dependency (RUSTSEC-2026-0543) #283
RustSec published RUSTSEC-2026-0543 today: chrono is unmaintained, all versions are affected, and there is no patched release. It is informational, not a vulnerability. Because scripts/ci/check-dependency-advisories.py fails on any OSV hit, every PR now fails Regression corpus across the root lock and three fixture locks (first seen on #282).
Done when:
The SDK and its fixture consumers no longer depend on chrono. Use jiff or time per the advisory, keeping wire formats and public API types compatible or deprecating them through a normal minor/major path.
The temporary advisory exception for RUSTSEC-2026-0543 is removed from the check script.
Decision recorded on #285. The advisory is informational and chrono is in the 4.x public API, so removal is a 5.0 change; #285 is held as its basis. Until then the scoped exception for (chrono, RUSTSEC-2026-0543) stays. This issue remains the 5.0 work item.
Decision (General): #297 (head ff2660d) replaces chrono with jiff and is the 5.0.0 candidate. It changes public API types (chrono::DateTime<Utc> → jiff::Timestamp). The wire format is byte-identical: it matches 529 chrono reference timestamps and over 1,000 existing fixture timestamps.
We're not cutting 5.0 for this alone. RUSTSEC-2026-0543 is informational (unmaintained), not a vulnerability, and the temporary exception covers CI. #297 stays a draft and ships in the next planned breaking release of the Rust SDK, with any other queued breaking changes.
Activity
Warn instead of failing on the informational chrono notice
rmcdaniel commentedon Nov 18, 2026
Decision recorded on #285. The advisory is informational and chrono is in the 4.x public API, so removal is a 5.0 change; #285 is held as its basis. Until then the scoped exception for (
chrono, RUSTSEC-2026-0543) stays. This issue remains the 5.0 work item.rmcdaniel commentedon Nov 19, 2026
Decision (General): #297 (head ff2660d) replaces chrono with jiff and is the 5.0.0 candidate. It changes public API types (
chrono::DateTime<Utc>→jiff::Timestamp). The wire format is byte-identical: it matches 529 chrono reference timestamps and over 1,000 existing fixture timestamps.We're not cutting 5.0 for this alone. RUSTSEC-2026-0543 is informational (unmaintained), not a vulnerability, and the temporary exception covers CI. #297 stays a draft and ships in the next planned breaking release of the Rust SDK, with any other queued breaking changes.
Before that release:
This issue closes when that ships.