Skip to content

Release v1.0.1 (maintenance)

v1.0.1 is a small operational / CI hygiene release. It does not change risk formulas, modeling claims, or supported data sources beyond tooling needed for release workflows.

Summary

  • Integration workflow: weekly workflow_dispatch / schedule runs include scripts/release_check.sh with COMPOSE_INTEGRATION=1 after the Compose bootstrap path.
  • Artifacts: optional upload of make export-calibration outputs (CSV + metadata.json) from scheduled/manual integration runs (best-effort; failures are non-blocking).
  • Self-hosted runners: documented in workflow comments and README — switch runs-on when you register your own runner for heavier Compose loads.
  • Issue templates: GitHub templates for bugs, ingestion/data-source failures, and calibration/model feedback (still not scientific validation claims).

Repairing legacy fn_alert_candidates overload drift

If Postgres errors with function analytics.fn_alert_candidates(...) is not unique (often after partial bootstrap or historic CREATE FUNCTION drift):

  1. Ensure dependent views are applied (make db-bootstrap-minimal or scripts/bootstrap_db.sh on a disposable DB).
  2. Run make repair-alert-function — reapplies integration, dispersion, and calibration SQL views and migration 013_phase14_canonical_alert_function.sql, which drops all overloads via pg_proc and installs the single 23-parameter canonical signature plus analytics.v_alert_candidates.
  3. Verify with make db-doctor (fn_alert_candidates:single_overload / param_count rows should be yes).

Fresh clones applying bootstrap_db.sh in order should not need repair; this path targets legacy dev volumes only.

Validation

Same as v1.0.0: make release-check, optional COMPOSE_INTEGRATION=1 / FULL_RELEASE_TEST=1 gates per docs/release/v1.0.0-checklist.md.