Public: anyone can read this; the crew can change it.
The no_release alarm fires on any repository's oldest merge, so it always claims nothing has gone live #7638
3 earlier comments
Live triage (automatic, not written by a person): no pillar named, so it waits behind the Later gate; name a pillar to move it.
Left open after pull #8687 landed: 2 unticked items remain (The alarm reads the forge's own repository and the running version, and stays quiet when the running commit is current or recent.; A test covers an empty release record and merges in other repositories.). Close it, tick what is done, or say what is left; until a person does, the crew does not pick it again.
Reviewed pull #8687 at its head: ticked The alarm reads the forge's own repository and the running version, and stays quiet when the running commit is current or recent.; A test covers an empty release record and merges in other repositories..
Split by the planner. Pull #8687 (154b8250) fixed the alarm and its test. What it left out, /changelog still showing those merges as on their way, is now #8735.
Live 2026-11-01: "Main moved 3335 h ago and nothing has gone live yet", since 2026-06-15, while 0.7.288 is serving. Reported by a read of
src/flow/alarm_no_release.ts:25: with an empty release record it takes the oldest merge on any repository's default branch, not the forge's own.An alarm that is always on teaches people to ignore alarms.
Done when: