Skip to content

Replace the unmaintained chrono dependency (RUSTSEC-2026-0543) #283

Open

Description

@rmcdaniel

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.

Activity

  1. rmcdaniel commented on Nov 18, 2026

    @rmcdaniel
    MemberAuthor

    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.

  2. rmcdaniel commented on Nov 19, 2026

    @rmcdaniel
    MemberAuthor

    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:

    1. Rebase 5.0: Replace chrono with jiff in the public API (#283) #297 onto main.
    2. Re-pin the command-keys and nexus test locks to the published 5.x.
    3. Remove the advisory exception.

    This issue closes when that ships.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions