v0.21.1

ALMa v0.21.1

Patch release: operational polish on top of v0.21.0.

Fixed¶

Health endpoint reports the release version — /api/v1/health returned the HTTP contract constant (1.0.0), which read as a wrong build number on a health probe. It now reports the pyproject-derived release version (this very image says 0.21.1); the contract version remains at /api/v1/version. Deploy tooling uses this to verify what's actually running.

stable image channel — release-tag builds now also publish :stable, :stable-gpu, :stable-lite. Unlike :latest (which moves on every main push), stable moves only on releases — point auto-updaters (e.g. watchtower) at it to track tested, released builds.
Removed the never-implemented immediate alert schedule value — reserved vocabulary with zero implementation behind it; unknown schedule strings never fire, and that guarantee is now pinned by tests.

New local release pipeline (scripts/release.sh): preflight gates, full test gate, version bump, tag, connector signed from the tag, GitHub release from committed notes — resumable, no CI secrets, replaces the per-clone pre-push hook.
New scripts/deploy-prod.sh: versioned container deploy (pinned X.Y.Z or the stable channel), env/volume-preserving, health-verified.
Docs synced across the alerts overhaul, per-channel dedup semantics, and the release/deploy flow.

alma-connector-0.21.1.xpi attached below (unchanged behavior from 0.21.0; version tracks the release).