v0.3.3

This patch release improves alerting reliability. The v0.3.2 SLO alerting introduced a few edge cases — burn rate dashboards could show false 100% spikes on low-traffic endpoints, an alert configuration accidentally silenced unrelated warnings cluster-wide, and a leftover blackhole route was interfering with alert delivery. All three are now fixed.

What's Fixed

• False burn rate spikes are gone. Low-traffic SLO endpoints (metadata, audit queries, activity queries) no longer show phantom 100% error ratios during brief traffic pulses.
• Warning alerts are no longer silenced cluster-wide. A severity-based inhibit rule was scoped too broadly — it now only applies to activity system alerts as originally intended.
• Alert delivery is no longer blocked by a dummy route. A leftover blackhole-style receiver in the AlertmanagerConfig was interfering with alert routing and has been removed.

PRs Included

Alerting Fixes

• #167 — Fix false 100% burn rates for low-traffic SLO endpoints
• #174 — Remove blackhole route from alert inhibitions config
• #178 — Fix inhibit rule silencing all warning alerts

Dependencies

• #161 — Update monaco-editor to ^0.52.0 || ^0.55.0
• #163 — Update golang.org/x/term to v0.41.0
• #164 — Update golang.org/x/time to v0.15.0
• #168 — Update actions/checkout to v6
• #169 — Update @rollup/plugin-commonjs to v29
• #172 — Update k8s.io/kube-openapi digest

Full Changelog: v0.3.2...v0.3.3