Skip to content

Add preliminary events filter, bump to v1.0.5 - #6

Merged
chriselsen merged 3 commits into
mainfrom
feat/preliminary-events-filter
Aug 24, 2026
Merged

chriselsen merged 3 commits into
mainfrom
feat/preliminary-events-filter

Conversation

@chriselsen

Copy link
Copy Markdown
Contributor

Summary

Adds a way to suppress unconfirmed ("preliminary") severity alerts entirely,
clarifies the Significant Events flag, and bumps the version.

Preliminary events filter

  • Add INCLUDE_PRELIMINARY_EVENTS environment variable (default true) to
    optionally exclude gauges and basin polygons whose elevated severity is
    still preliminary — i.e. not yet confirmed across MIN_CONFIRMING_ISSUANCES
    daily forecast issuances
  • Lets operators trade earlier notice for fewer false positives by setting it
    to false, on top of the existing "(preliminary)" labeling
  • Add a preliminary boolean to OutputSchema and to gauge/basin metadata,
    alongside the existing confirmed field

Documentation

  • Expand the INCLUDE_SIGNIFICANT_EVENTS description to explain what a
    significant event actually is (an area-wide event clustered from gauge
    discharge predictions exceeding danger thresholds, weighted by affected
    population/area) and what the flag controls (polygon rendering + [event]
    gauge cross-referencing)

Version bump

  • package.json version bumped to 1.0.5
  • Checked all dependencies against latest available versions — already up to
    date, no changes needed
  • typescript remains pinned at 6.0.3: typescript-eslint's peer range
    still caps at <6.1.0, so 7.x isn't installable alongside it yet
  • CHANGELOG updated

Testing

  • npx tsc --noEmit — passes
  • npm run lint — passes
  • npm run build — passes
  • npm audit — 0 vulnerabilities

Not verified: end-to-end run against the live Google Flood Forecasting API
(requires API_KEY/ETL_* credentials), so the new filter's behavior on
real preliminary/confirmed gauge data hasn't been observed directly.

Blocked / follow-ups

  • None blocking. Revisit pinning typescript to 7.x once typescript-eslint
    adds support.

Checked all dependencies against latest available versions; already
up to date. typescript remains pinned at 6.0.3 pending
typescript-eslint TypeScript 7 support (peer range still caps at
<6.1.0).

Verified: npm run build, npm run lint, tsc --noEmit, npm audit (0
vulnerabilities) all pass.
- Add INCLUDE_PRELIMINARY_EVENTS env var (default true) to optionally
  suppress gauges/basin polygons whose elevated severity is still
  preliminary (not yet confirmed across MIN_CONFIRMING_ISSUANCES
  forecast issuances), letting operators trade earlier notice for
  fewer false positives
- Add preliminary boolean to OutputSchema and gauge/basin metadata,
  alongside the existing confirmed field
- Expand INCLUDE_SIGNIFICANT_EVENTS description to explain what a
  significant event is (area-wide event clustered from gauge
  discharge predictions exceeding danger thresholds, weighted by
  affected population/area) and what the flag controls
@chriselsen
chriselsen merged commit 60ce873 into main Aug 24, 2026
1 check passed
@chriselsen
chriselsen deleted the feat/preliminary-events-filter branch August 24, 2026 04:13
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