Migrate date/time handling from unmaintained chrono #8

Open
opened 2026-11-20 12:58:34 +09:00 by agent · 1 comment

Purpose

Migrate TauClock away from chrono, which RustSec marks unmaintained in RUSTSEC-2026-0543.

Baseline

  • main: 5392214361b263c23b0cadf45d989658a606c712
  • direct chrono = 0.4.42; lock resolves 0.4.43
  • usage covers local/UTC clock display and next-alarm scheduling

Acceptance conditions

  • replace chrono with a maintained library, preferring Jiff 1.x
  • preserve local and UTC display formats, epoch-millisecond timer behavior, persisted alarm JSON compatibility, and next-alarm behavior across ordinary dates and DST gaps/ambiguities
  • add deterministic scheduling tests, including DST-sensitive behavior where practical
  • cargo tree contains no chrono
  • Rust format, compilation, lints/tests, and frontend/build checks pass

Safety

Use a branch and PR; do not push to main. No release or deployment is in scope without a separate gate.

Exact next action

Model the existing local-time ambiguity/fallback policy with Jiff and add tests before changing behavior.

## Purpose Migrate TauClock away from `chrono`, which RustSec marks unmaintained in RUSTSEC-2026-0543. ## Baseline - `main`: `5392214361b263c23b0cadf45d989658a606c712` - direct `chrono = 0.4.42`; lock resolves `0.4.43` - usage covers local/UTC clock display and next-alarm scheduling ## Acceptance conditions - replace `chrono` with a maintained library, preferring Jiff 1.x - preserve local and UTC display formats, epoch-millisecond timer behavior, persisted alarm JSON compatibility, and next-alarm behavior across ordinary dates and DST gaps/ambiguities - add deterministic scheduling tests, including DST-sensitive behavior where practical - `cargo tree` contains no `chrono` - Rust format, compilation, lints/tests, and frontend/build checks pass ## Safety Use a branch and PR; do not push to `main`. No release or deployment is in scope without a separate gate. ## Exact next action Model the existing local-time ambiguity/fallback policy with Jiff and add tests before changing behavior. <!-- chrono-rustsec-2026-0543 -->
Author

Implementation evidence — 2026-11-20

PR #10: #10
Exact head: 1d01c501ca (3 GPG-signed commits, source branch agent:issue-8-migrate-chrono-jiff).

  • direct/active Chrono dependency replaced by Jiff 1.0.1
  • local/UTC display, epoch milliseconds, persisted JSON, fold and legacy gap behavior preserved
  • deterministic scheduling/JSON tests: 7 / 7 PASS
  • fmt, Clippy with warnings denied, build: PASS
  • compatible lock refresh removed all vulnerability-class cargo-audit findings
  • six remaining warning-class Tauri/Linux transitive advisories are documented and tracked in #9

Exact next action: Mina reviews immutable SHA 1d01c50; merge/release remain separate authorization gates.

## Implementation evidence — 2026-11-20 PR #10: https://git.rumginger.org/kamat/tauclock/pulls/10 Exact head: 1d01c501ca82e1c29af7625f21d2c5684f0795a6 (3 GPG-signed commits, source branch agent:issue-8-migrate-chrono-jiff). - direct/active Chrono dependency replaced by Jiff 1.0.1 - local/UTC display, epoch milliseconds, persisted JSON, fold and legacy gap behavior preserved - deterministic scheduling/JSON tests: 7 / 7 PASS - fmt, Clippy with warnings denied, build: PASS - compatible lock refresh removed all vulnerability-class cargo-audit findings - six remaining warning-class Tauri/Linux transitive advisories are documented and tracked in #9 Exact next action: Mina reviews immutable SHA 1d01c50; merge/release remain separate authorization gates. <!-- chrono-evidence-1d01c50 -->
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: kamat/tauclock#8