Skip to content

chore: waive RUSTSEC-2026-0543 (chrono unmaintained) - #755

Merged
bahdotsh merged 1 commit into
mainfrom
chore/waive-chrono-unmaintained-advisory
Nov 17, 2026
Merged

bahdotsh merged 1 commit into
mainfrom
chore/waive-chrono-unmaintained-advisory

Conversation

@bahdotsh

Copy link
Copy Markdown
Member

Why

The Dependency Audit job is failing on main (runs for #751 and #752) and will fail on every open pull request. Nothing merged caused it: RUSTSEC-2026-0543 was published today and marks chrono unmaintained, all versions affected, no safe upgrade.

error[unmaintained]: chrono is unmaintained
  chrono 0.4.45
  ID: RUSTSEC-2026-0543
advisories FAILED, bans ok, licenses ok, sources ok

What

  • deny.toml: waive RUSTSEC-2026-0543, with the rationale.
  • .cargo/audit.toml: the same id, since that list must stay a superset of deny.toml's.

What this does not do

chrono is a direct workspace dependency of offline-protocol, offline-protocol-mls, offline-protocol-reliability and offline-protocol-router, compiled and shipped. The waiver is a notice-not-vulnerability call that buys time; the remedy is a migration to jiff or time, which touches persisted and serialized timestamps and belongs in its own pull request. The waiver comment says to drop it there.

Verification

  • cargo deny --all-features check: advisories ok, bans ok, licenses ok, sources ok (the same command CI runs).
  • cargo audit: reported RUSTSEC-2026-0543 before the change, does not after.

The advisory was published on 2026-11-17 and fails the Dependency Audit job on main and on every open pull request. It is a maintenance-status notice, not a vulnerability, and it covers every chrono release, so there is no version to move to.

chrono is a direct dependency of four crates and is compiled and shipped. The waiver says so, and is to be dropped by the pull request that migrates the workspace to jiff or time.
@bahdotsh
bahdotsh merged commit dc265c1 into main Nov 17, 2026
45 checks passed
@github-actions github-actions Bot locked and limited conversation to collaborators Nov 17, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant