Skip to content

Track the new chrono and chrono-tz unmaintained advisories - #108

Open
Ghosts wants to merge 1 commit into
masterfrom
chrono-advisory
Open

Ghosts wants to merge 1 commit into
masterfrom
chrono-advisory

Conversation

@Ghosts

@Ghosts Ghosts commented Nov 19, 2026

Copy link
Copy Markdown
Member

The dependencies check on master started failing after the #106 merge. RustSec published two new advisories:

  • RUSTSEC-2026-0543: chrono 0.4.45 is unmaintained. It's used directly and by cron, chrono-tz, rmcp and schemars.
  • RUSTSEC-2026-0555: chrono-tz 0.10.4 is unmaintained. Schedules use it for time zones.

Neither is a vulnerability, and neither has a patched release. This adds both to scripts/security/dependency-policy.json with the other reviewed upstream maintenance warnings. Replacing chrono needs cron and rmcp to move first.

This unblocks the beta cut: publication requires dependencies to pass on the source commit.

Checks: pnpm check:dependencies passes locally (0 vulnerabilities, 9 tracked warnings), and Biome is clean on the file. I didn't run the full pnpm verify locally for this one-file change; CI runs it.

RUSTSEC-2026-0543 and RUSTSEC-2026-0555 mark both crates unmaintained with no
patched release. They are not vulnerabilities; record them with the other
reviewed upstream maintenance warnings so the dependency check passes again.

This branch has not been deployed

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant