Skip to content

fix(deps): replace chrono with jiff (RUSTSEC-2026-0543) - #109

Merged
rennf93 merged 6 commits into
masterfrom
fix/chrono-to-jiff
Nov 18, 2026
Merged

rennf93 merged 6 commits into
masterfrom
fix/chrono-to-jiff

Conversation

@rennf93

@rennf93 rennf93 commented Nov 18, 2026

Copy link
Copy Markdown
Member

tower-guard-rs moves from chrono to jiff with the engine and resolves guard-agent-rs from its jiff branch, so cargo deny and cargo audit go green again.

What changed:

  • 71f6467 build(examples): pass guard-agent-rs into the example image builds
  • 71e7452 ci: test against the jiff engine on its companion branch
  • 811cd8b build(deps): resolve guard-agent-rs as a path dependency on the companion branch
  • 0f57149 fix(deps): replace chrono with jiff (RUSTSEC-2026-0543)

The engine moves from chrono to jiff in Guard-Core/guard-core-rs#184 (RUSTSEC-2026-0543, -0555, -0559). This repo follows it: chrono is gone from the dependency tree (cargo tree -i chrono --all-features prints nothing) and the timestamps it writes stay byte-identical.

TEMPORARY pins: the CI workflows check out the engine on fix/rustsec-actix-2026-11 and guard-agent-rs on fix/chrono-to-jiff (a sibling checkout for its path dependency). Each pin is reset to master in this PR before it merges, once the dependency it names has landed.

How I checked it, before CI: the repo's full gate (fmt, clippy -D warnings, tests, coverage, MSRV 1.92, audit, deny) on the head, plus the adversarial pass over the whole train (results in the trail).

rennf93 and others added 4 commits November 17, 2026 23:30
The adapter used chrono only to read the wall clock for the route time window and in tests that build a window around now. They now use jiff::Timestamp, and hhmm_in_zone takes the jiff timestamp the migrated engine expects. No public API of this crate changes.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Entire-Checkpoint: 01M7NT3J8FTPAMQX7A842Y138T
…nion branch

The optional guard-agent-rs 3.2.4 from crates.io still pulled chrono (RUSTSEC-2026-0543) into the lock. It now resolves as a sibling path dependency like the engine, and every workflow that places the engine sibling also checks out guard-agent-rs at fix/chrono-to-jiff as a temporary companion pin, to reset to master after the train merges.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Every workflow step that checks out guard-core-rs now takes the engine from fix/rustsec-actix-2026-11, the branch of guard-core-rs PR 184 that moves the engine from chrono to jiff, so the jobs build the adapter against the engine it will ship with. The ref goes back to master after the train merges, as the guard-agent-rs pin does.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
The adapter now has guard-agent-rs as a sibling path dependency, and cargo resolves it even with the feature off, so the example images failed to build with only the engine in the build context. The Dockerfiles take guard-agent-rs (manifest, lockfile and source) from an additional build context named agent, the same way they take the engine, and both compose files point that context at the sibling checkout. I built the simple example image for each adapter on a sibling layout like CI's and removed the images afterwards.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@rennf93 rennf93 added the no-issue No tracking issue applies to this change label Nov 18, 2026
@github-actions github-actions Bot added tests Test suite changes ci GitHub Actions dependencies Cargo.toml or Cargo.lock area: lib Touches src/ (tower::Layer / tower::Service adapter — currently a single-file lib stub) labels Nov 18, 2026
rennf93 and others added 2 commits November 18, 2026 07:43
The coverage job on the Linux toolchain counts a few untaken branches and closures that the macOS toolchain does not. Each now has a real test that takes the branch.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
The engine (guard-core-rs PR 184) and guard-agent-rs (PR 91) merged their jiff migrations, so the TEMPORARY companion pins to their branches go back to master.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@rennf93
rennf93 merged commit dc70c4c into master Nov 18, 2026
13 checks passed
@rennf93
rennf93 deleted the fix/chrono-to-jiff branch November 18, 2026 08:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area: lib Touches src/ (tower::Layer / tower::Service adapter — currently a single-file lib stub) ci GitHub Actions dependencies Cargo.toml or Cargo.lock no-issue No tracking issue applies to this change tests Test suite changes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant