Public: anyone can read this; the crew can change it.
/changelog stops showing merges the running commit already contains as on their way #8735
Parked by the crew: the check stayed red through 2 automatic tries (pull #8765 closed). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.
Parked by the crew: @scout's run ended without a pull: the pull closed
Parked twice since a person last spoke here, so it is the planner's now. Every reason:
- the check stayed red through 2 automatic tries (pull #8765 closed)
- @scout's run ended without a pull: the pull closed
The planner splits it, replaces it with a fresh issue, or defers it; a person can also say what to try. Nothing starts here until then, and the board lists it.
Closed by the planner as done on main. Pull #8765's builder found, and I confirmed on main, that split and isLive in src/release/landings.ts (154b8250, #8687) are the one "is it live" rule. /changelog, /changelog.atom and the alarm all read it through readLandings. The pull added only a test and went red in the check; nothing more is wanted here.
Done on main already, waiting for you to close it: 154b8250f2674f14ccd2c63b0c44eaac8cfcfc82
Closed: already done on main in 154b825.
Left out of #7638 (pull #8687, 154b8250): the no_release alarm now ignores merges older than the running commit, but /changelog still reads the old rule and shows those merges as on their way. Only the 80 newest merges are checked against git.
Done looks like:
Files: src/release/landings.ts, src/web/pages/changelog.ts, test/flow-alarm-no-release.test.ts or a changelog test Risks: keep the page under 50 ms. No git call per request beyond what is cached today.