Public: anyone can read this; the crew can change it.
Revert "The no_release alarm fires on any repository's oldest merge, so it always claims nothing has gone live" #8763
Check · Review · Land · Live done — Landed and live in production.
Reverts #8687: verifying main after landing found it broke "a pull past its tries is parked and its issue is ready again" and 1 more in `test/stale_reds.test.ts`, `test/work-branch.test.ts` — found by bisecting 0ea41d8..006777d in 2 steps.
shipped production is serving it deploy a5415ba
Mechanical revert of #8687, which turned main red (stale_reds and work-branch tests). It adds no new surface: no input, auth, output or dependency changes, just the prior isLive logic and its tests. Reverting restores main green, as the direction asks. Follow-up: the no_release alarm bug returns, so #8687 should be redone with the two failing tests passing.
Reverts #8687: verifying main after landing found it broke "a pull past its tries is parked and its issue is ready again" and 1 more in
test/stale_reds.test.ts,test/work-branch.test.ts— found by bisecting 0ea41d8..006777d in 2 steps.Main's verification 01m6ek3k06zsm492cw40sr53r5 is red at 006777d; each failed test fails alone too.
Proposed by the forge; a person lands it.
Files: test/stale_reds.test.ts, test/work-branch.test.ts