Public: anyone can read this; the crew can change it.
The changelog shows what actually shipped: every landing that went live, as it happens #7676
/changelog now lists what went live, read from the running commit instead of the empty release table. It shows the live version and commit at the top and how many pulls shipped today. I ran changelog, the alarm tests, pillars, mcp-releases, mcp-size and the docs-mcp tests (34 pass), plus tsc and the design lint.
stopped closed without shipping deploy 6e1b15f
2 earlier comments
/changelog now lists what went live, read from the running commit instead of the empty release table. It shows the live version and commit at the top and how many pulls shipped today.
I ran changelog, the alarm tests, pillars, mcp-releases, mcp-size and the docs-mcp tests (34 pass), plus tsc and the design lint. I did not run the full suite; the forge's check does that on push. mcp-size passes, and no ceiling was raised. I have not looked at the page in a browser or on a phone.
What changed
- New record,
src/release/landings.ts: it lists merged pulls from public repositories. A pull to the forge's own repo is live once the running commit (FORGE_COMMIT, the one health reports) contains its merge commit. It asks git withmerge-base --is-ancestorand keeps a "live" answer in memory. When no commit is stamped, it uses the default-branch head. A pull to any other repo counts as live when it lands. A merged pull with no recorded merge commit is judged by its merge time against the running commit's date. - Page (
src/web/pages/changelog.ts):- Live pulls are grouped by UTC day, newest first, each with title, link, repo and time.
- Landed-but-not-contained pulls sit apart under "On its way".
- The forge's own repo is the default view.
?repo=allor?repo=owner/namefilters, and an unknown value falls back to the default. - The list is a region the existing live client swaps in place on
pull.mergedandapp.serving, so new entries arrive without a reload. - The empty state shows only when nothing has shipped.
- MCP:
releasestakes{shipped: true}and returnsversion,commit,liveandonItsWay, with no new tool.docs/MCP.mdis regenerated. - #7638:
noReleaseAlarmnow reads the same record. It fires when the oldest landing not in the running commit is more than 90 minutes old.main.tsrefreshes the record every minute, and the alarm says nothing until a first read has happened. - Tests: I rewrote
test/changelog.test.tsfor the new page (the old assertions were aboutRelease <version>:commits) and adapted the two alarm tests to set the running commit directly. The page, filters, private-repo exclusion, MCP parity and the empty state are covered.
What I did not do
- "When it went live" is the merge time. The forge keeps no moment at which production began serving a commit. Recording one would need a new table, so I left it for a follow-up.
- The terminal's Changelog screen is unchanged. It still reads the old
Release <version>:commits throughrelease/changelog.ts, so it stays empty. I did not touch it;docs/features/changelog.mdsays so. - Backfill is whatever the pull table holds. The most recent 300 merged pulls show, and none of them need a separate import.
Try it: open /changelog and /changelog?repo=all, or call MCP releases with {"shipped": true}. Run bun test test/changelog.test.ts test/flow-alarm-no-release.test.ts.
/changelog now lists what went live from merged pulls, newest first and grouped by UTC day. The branch already held this work (commit 6e1b15f7), and I added nothing new this turn. bun x tsc --noEmit is clean, the changelog and alarm tests pass (13 tests), and design-lint is clean. I didn't run the whole suite, and I didn't start the app to look at the page.
What changed
- Source: the new
src/release/landings.tsreads merged pulls from the database. A pull to the forge's own repository counts as live only once the running commit, the one/api/v1/healthreports, contains its merge commit. Git answers that withmerge-base --is-ancestor, and the answer is kept while it holds. A pull to any other public repository counts as live when it merges. - Page: each entry shows the pull's title, a link to it, the repository and when it landed. Pulls merged but not yet in the running commit sit apart under "On its way". The top line gives the live version and commit and how many shipped today.
- Filters: the page defaults to this forge's own work.
?repo=allshows everything, and?repo=owner/nameshows one repository. - Live updates: the list refreshes without a reload when a pull merges or production serves a new commit.
- Empty and backfill: the page reads merged pulls straight from the database, so it is full on first load. It is empty only when nothing has shipped.
- MCP and alarm: MCP
releaseswith{shipped: true}returns the same list to anyone. The falseno_releasealarm (#7638) now reads the same record. - Docs and tests:
docs/features/changelog.mdanddocs/MCP.mdare updated, andtest/changelog.test.tsis rewritten.
Not done
- The older
Release <version>: …commit read stays, because the terminal's Changelog screen still uses it. - The page offers at most 6 other repositories as filter chips.
- Only the newest 300 merged pulls are read.
- The alarm stays silent until the first read of the record has happened.
Try it: open /changelog, then /changelog?repo=all. Or call MCP releases with {"shipped": true}.
The issue sits behind the Later gate because no pillar is named. I changed nothing for that, and a person has to name one.
Closed by the crew: superseded, its change is already on main in 05da7cd9.
/changelognow lists what went live, read from the running commit instead of the emptyreleasetable. It shows the live version and commit at the top and how many pulls shipped today.I ran
changelog, the alarm tests,pillars,mcp-releases,mcp-sizeand thedocs-mcptests (34 pass), plustscand the design lint. I did not run the full suite; the forge's check does that on push.mcp-sizepasses, and no ceiling was raised. I have not looked at the page in a browser or on a phone.What changed
src/release/landings.ts: it lists merged pulls from public repositories. A pull to the forge's own repo is live once the running commit (FORGE_COMMIT, the one health reports) contains its merge commit. It asks git withmerge-base --is-ancestorand keeps a "live" answer in memory. When no commit is stamped, it uses the default-branch head. A pull to any other repo counts as live when it lands. A merged pull with no recorded merge commit is judged by its merge time against the running commit's date.src/web/pages/changelog.ts):?repo=allor?repo=owner/namefilters, and an unknown value falls back to the default.pull.mergedandapp.serving, so new entries arrive without a reload.releasestakes{shipped: true}and returnsversion,commit,liveandonItsWay, with no new tool.docs/MCP.mdis regenerated.noReleaseAlarmnow reads the same record. It fires when the oldest landing not in the running commit is more than 90 minutes old.main.tsrefreshes the record every minute, and the alarm says nothing until a first read has happened.test/changelog.test.tsfor the new page (the old assertions were aboutRelease <version>:commits) and adapted the two alarm tests to set the running commit directly. The page, filters, private-repo exclusion, MCP parity and the empty state are covered.What I did not do
Release <version>:commits throughrelease/changelog.ts, so it stays empty. I did not touch it;docs/features/changelog.mdsays so.Try it: open
/changelogand/changelog?repo=all, or call MCPreleaseswith{"shipped": true}. Runbun test test/changelog.test.ts test/flow-alarm-no-release.test.ts.Closes #7672