OpsWarden v1.0.12

OpsWarden v1.0.12 completes the Alertmanager lifecycle contract introduced
in v1.0.11.

Alert lifecycle

• Each alert in an Alertmanager notification group is handled independently.
• firing and resolved alerts produce distinct alert_firing and
  alert_resolved events, including mixed-status groups.
• Semantic idempotency ignores retries whose JSON formatting, labels,
  annotations or provisional firing endsAt changed, while preserving genuine
  lifecycle transitions.
• Receiving alert_resolved does not implicitly close an Incident. Teams
  choose the reaction attached to that event.

Operations and verification

• /metrics exposes bounded Alertmanager delivery counters for accepted,
  rejected, duplicate, ignored and failed outcomes.
• HTTP and persistence tests cover the 1 MiB limit, authentication, provider
  mismatch, disabled rules, Team isolation and failed reactions.
• The critical E2E configures the official Alertmanager v0.32.1 image pinned
  by digest and proves a firing alert followed by its resolution as two durable
  automation runs.

The feature CI and the post-merge main gate passed before this release was
prepared.

Install

Platform	Artifact
Linux (Debian/Ubuntu)	OpsWarden_1.0.12_amd64.deb
Linux (portable)	OpsWarden_1.0.12_amd64.AppImage
Windows	OpsWarden_1.0.12_x64-setup.exe
macOS	OpsWarden_1.0.12_aarch64.dmg

Verify a download against SHA256SUMS. Every artifact carries a GitHub
build-provenance attestation.

Server image

ghcr.io/opswarden-git/opswarden-server@sha256:6468bd3eb43b410ccc911c3dab0cade0696180932e765559df34bd88f2ead026

Production pins this digest, never a mutable tag.

What's Changed

• Document Alertmanager and remaining roadmap by @RomeoCavazza in #127
• feat: complete Alertmanager lifecycle handling by @RomeoCavazza in #128
• Release v1.0.12 by @RomeoCavazza in #129

Full Changelog: v1.0.11...v1.0.12