Repository navigation
Description
Why
cargo audit --deny warnings fails on RUSTSEC-2026-0543, published 2026-11-17: chrono is unmaintained, all versions affected, no patched version. The maintainer is winding the crate down (chronotope/chrono#1768). The scheduled audit on main and every manifest or lockfile PR (for example #1473) fail until this is resolved.
It is an informational advisory, not a vulnerability. A lockfile update cannot clear it.
Where chrono is used
chrono 0.4.45 is a direct dependency of clickhousectl and clickhouse-cloud-api only; nothing else pulls it in. About 159 references:
clickhouse-cloud-api(71, public API):chrono::DateTime<chrono::Utc>on model fields (created_at,expire_atand similar), through chrono'sserdefeature. Changing the type is a breaking change for the published crate.clickhousectl: RFC 3339 parse and format (including millisecond precision for the Postgres API),Utc::now, Unix timestamps, date arithmetic incloud/activity.rs, and twostrptime-style HTTP date formats inversion_manager/download.rs.clickhouse-openapi-analyzer: matches the type namesDateTime,NaiveDateTimeandNaiveDateinsrc/responses.rs.
No time zone database is used; everything is UTC or a fixed offset.
Options
| jiff | time | Ignore the advisory | |
|---|---|---|---|
| Version | 1.0.0 (2026-11-15), MSRV 1.85 | 0.3.55, MSRV 1.88 | n/a |
| Named by the advisory | yes, and by the chrono maintainer | yes | n/a |
| serde for RFC 3339 | default on Timestamp, no field attributes |
#[serde(with = "time::serde::rfc3339")] on every field, plus an Option variant |
n/a |
| Public API stability | 1.0 | still 0.x | n/a |
| Already in the tree | no | dev-dependencies only (AWS SDK, rcgen); not in the shipped binary |
n/a |
Recommendation
Move to jiff, in 0.6.0.
- Model fields stay a plain type with no serde attributes, which keeps the analyzer's type-based mapping.
- A 1.0 type is a better thing to expose from a published library than a 0.x one.
- 0.6.0 is unreleased and already breaking, so the public type change costs nothing extra now. Later it needs another breaking release, with an audit ignore in between, which
AGENTS.mdsays to avoid.
jiff 1.0.0 is two days old. Check its docs for the exact API before starting; the mapping below is the expected one, not verified against 1.0.
Plan
- Library PR:
chrono::DateTime<chrono::Utc>→jiff::Timestampon all model fields and thePgCreatedAtPropertyalias; update the analyzer's type-name matcher; changelog entry under## Unreleasedwith the caller migration. Confirm wire output is unchanged (…Z, and what the fractional digits look like). - CLI PR: migrate the remaining call sites, drop
chronofrom both manifests, confirmcargo auditis clean.
Done when
chronois not inCargo.lock.cargo audit --deny warningspasses.- Request and response timestamps are byte-identical on the wire for the existing tests.
Activity
build(deps): replace chrono with jiff (#1474)