• v1.0.2 53240035f3

    v1.0.2 — Alert correctness & integrity
    All checks were successful
    CD / test (push) Successful in 3m44s
    CD / deploy (push) Successful in 1m0s
    Stable

    claude-bot released this 2026-07-18 14:28:31 +00:00 | 171 commits to main since this release

    Patch release: alert-pipeline correctness and integrity. Bug fixes only, no new features. Addresses the highest-severity findings from the 2026-07-17 codebase audit.

    Fixed

    • False all-clears on transient NWS outages (#40) — fetches retry with jittered backoff and return None on failure; a failed cycle performs no clearing or dispatch. An empty resolved-locations list can no longer mass-clear, and alerts with no ends/expires get a synthetic expiry so they stay visible and clearable.
    • Dropped alerts during large outbreaks (#41)/alerts/active responses are now paginated (bounded, logged) instead of truncated to page one and then cleared as "disappeared".
    • SPC Day 1/2/3 collapsed into one notification (#42) — convective outlooks record and dispatch per day.
    • MCD state false-positives (#43) — state matching parses the AREAS AFFECTED line, so "in"/"or" no longer match Indiana/Oregon.
    • Duplicate SPC notifications on reissuance (#44) — a same-risk reissue is treated as a continuation instead of a new outlook.
    • Alert history lost on channel deletion (#48) — deleting a channel preserves its sent_alerts rows as dashboard-only records.
    • Public location page stuck on "Loading alerts…" (#49) — current active alerts are server-rendered with a "No active alerts" empty state.
    • Details-link failures could drop notifications (#54) — all six notifier channels now send without a link on failure.
    • One malformed SPC feature aborted the whole poll (#62) — per-feature parsing and the SPC gathers are now failure-tolerant.

    Full test suite green (344 passed) including new regression tests across all fix areas.

    Full changelog: see CHANGELOG.md. PR #92.

    Downloads