Changelog
GET /changelog is public. It lists the last 30 Release <version>: … commits on the default branch of the forge's own repository (FORGE_REPO), newest first. Each has a heading anchored #<version>, its date, and one link per pull named in the subject (title (#N);title (#N)). When FORGE_REPO is unset or its repository is private, the page answers 200 with "No releases yet". The footer links to it.
The terminal's palette has Changelog, the same read for anyone, a guest included. / takes a word and keeps only releases whose version or carried pull titles contain it, ignoring case; the header says how many match, and esc clears it. Enter on a release lists its pulls (#N title); a release whose subject names none shows "No pulls". Enter on a pull opens it, as Enter does on any pull. w reads the changelog by wave, as the page's "Read it by wave" link does: Enter on a wave opens its changes, Enter on a change opens its pull, and esc goes back to the row you left. It goes through sourceFor, so a repository the reader may not open stays closed. Tested in test/tui-changelog-waves.test.ts.
One bounded git log read, cached per head oid; Server-Timing names releases and render.
How close each open milestone is (#11409)
/changelog opens with one line per open milestone of the forge's own repository: its name (linked to its milestone page), N of M done and a progress bar. A deferred or closed milestone is left out, and the block is absent when none is open or when the reader may not open the repository (a guest on a private one). The terminal's Changelog screen shows the same lines above the releases (name, N of M done, at most five), under the same read check. Both read nearMilestones in web/pages/milestones_near.ts; the page's ETag includes them.
What went live (#7672)
/changelog lists the pulls merged into a default branch, newest first, grouped by UTC day: title, link, repository, when it landed. A pull to the forge's own repository (FORGE_REPO) counts only once the running commit (FORGE_COMMIT, the one /api/v1/health reports; the default branch head for a forge run from source) contains its merge commit, asked of git with merge-base --is-ancestor and kept while live. Landed but not yet contained shows above as "On its way". A pull to any other public repository is live when it lands. The top line says the live version and commit and how many shipped today. ?repo=all or ?repo=owner/name filters; the forge's own repository is the default.
The list is a live region (pull.merged, app.serving): it swaps in place without a reload. MCP releases with {shipped: true} answers the same list to anyone. The "no release" alarm reads the same record (release/landings.ts), refreshed each minute, and is silent until a read has happened. The older Release <version>: … commit read (release/changelog.ts) now serves only the terminal's Changelog screen.
Reads like a story (#10837)
Titles are shown plain (plainTitle in story/gather.ts): a leading small: and any test/… or src/… path are dropped, and a first plain word is capitalised (j/k is left as written). The pull keeps its real title on its own page. Within one UTC day, landings whose titles share a shape (the same words with one slot of up to three words changing, at least three words shared) gather into one line such as "j/k, enter, esc and ? on …", with the count and who built them said once; on the page the line is a <details> (a focusable <summary>, no script) that opens to each pull. A title naming a revert or a security fix is never gathered. The terminal's release pulls gather the same way (Enter on a gathered line lists its pulls), and /changelog.atom uses the plain titles. /api/v1/changelog keeps the raw titles.
Credit (#9181, #10259)
A squash keeps the people behind its commits: the landed message carries every distinct Co-authored-by its commits carried and each commit's author, except the crew's agents (@agents.invalid), once per address. /changelog then shows "With Jay Moran" on a row for everyone credited on the landed commit beyond whoever landed it (creditsOf in git/coauthors.ts, one git read, kept per commit); a landing with no one else shows nothing. Only the forge's own repository is read. A row also says who built it: "By Scout" is the author of the landed commit, "With Claude Sonnet 5.5" the names in its trailers (less the committer and the author), both as plain facts under the title, from the same one git read (buildersOf). At most the newest 80 landings of the forge's own repository are asked of git, and at most 500 commits are remembered, oldest dropped first. GET /api/v1/changelog carries by and with on a landing that has them. In the terminal, Enter on a release lists its pulls, and a pull the forge landed shows "by Scout, with Claude Sonnet 5.5" beside it.
For agents
GET /api/v1/changelog is the page's list as JSON, public, cached five seconds: {version, commit, live, onItsWay}, each landing {repo, number, title, at, live[, with]}. ?repo=all or ?repo=owner/name filters; the default is the forge's own repository, as on the page. MCP releases with {shipped: true, repo?} and GET /api/v1/releases?shipped=true[&repo=] answer the same rows with the same default. Only public repositories are read; concurrent requests share one read of git and the merged rows, so an anonymous caller costs no more than a page view. The page links the JSON with rel="alternate". The terminal's Changelog screen is the release-commit view (release/changelog.ts), told in chapters when there are any (see Chapters), and it reads by wave on w.
As a feed (#8213)
GET /changelog.atom is the same list as an Atom feed, public, for a feed reader. It holds the newest 20 live landings of the forge's own repository (FORGE_REPO, public only), newest first, one entry each titled Went live: <title> with a one-sentence summary (Landed in <repo> as pull #<n> on <date> and is live.) and linked to that release's row on the page, /changelog?release=release-<owner>-<name>-<n>#release-<owner>-<name>-<n> (the row's id, from release/anchor.ts). The release= part opens a gathered line that holds the row, so the link lands on a row you can see without any script. what has landed but is not yet live is left out. A landing a wave covers collapses into one entry per wave (not per release or per landing): the wave's headline is the title, its highlights the summary, the link goes to the wave's page, and the entry is dated at the wave's newest landing. Waves are read from the forge repository's default branch, so the ETag moves with that branch's tip as well as with the list. The tip is read on every request, the 304 path included; the five-minute cache is what keeps git off the hot path. The 20 is the feed's own cap (CHANGELOG_ENTRIES in web/feeds.ts); the page and /api/v1/changelog are not capped. It is cached for five minutes (cache-control: public, max-age=300) and carries a weak ETag, so a reader that sends If-None-Match gets a 304. The page links it with rel="alternate".
An agent reads the same data as JSON, not Atom: MCP releases with {shipped: true} or GET /api/v1/changelog (see above). The terminal has no screen for the feed, since a feed is for a reader program; its Changelog screen is the release-commit view, with w for the waves.
Chapters (#12695)
When a repository has chapters (open or closed, never a draft), /changelog tells its landed pulls under them, newest chapter first, the open one before the closed. Each chapter is a row of the page's usual list: its name linked to its page, and its closing day, or "open", as the trail; below it, one line per pull that served it, in the list's order. A chapter nothing landed in is kept and says "Nothing landed yet." on its row. Pulls that served no chapter come last under a "Between chapters" row of the same shape. With no chapter to show (none, or none the reader may read) the list is the flat days as before.
Which chapter a pull served is read from the chapter items, never from text or time (chapterOfPulls in core/chapters.ts): the chapter holding the pull's own issue, else the first chapter holding an issue its body closes (Closes #N, in the order written). A pull that closes issues in two chapters is therefore placed in the first match only, silently. Chapters of a repository the reader may not read are not drawn.
The terminal's Changelog screen tells the same story from the same code (release/chapter_groups.ts): a Chapter v1 line (open or closed 2026-10-25, and its pull count) with each pull indented under it as #N title, then Between chapters. Enter on a pull line opens that pull; / narrows by title or number, headings with no pull left drop away, and the empty state says "No pull matches". Whether the reader may see the repository goes through sourceFor, the door opening a pull uses. With no chapter the screen keeps its release rows.
The page's ETag holds one aggregate query (chapterStamp: chapter count, newest close, repository visibility, the item count and newest item, and a hash of which chapter holds each item, so moving an item between chapters moves the tag); the per-repository chapter reads run only after the tag has missed, so a 304 costs one query. The browser's day regrouping (localDaysJs) leaves a page with chapters alone. test/changelog-timing.test.ts holds the page to its budget with 500 pulls in chapters.
Months (#13545)
Days sit under month headings, newest first: an <h2> such as "November 2026" with the id 2026-11, its days <h3> beneath it, so a screen reader navigating by heading finds days inside their month. The heading is a link to itself: /changelog#2026-11 scrolls to that month, and the link copies as a shareable URL. A month with no landing has no heading. Months are UTC, and the browser's day regrouping keeps one heading per month, in front of its days.
Chapter-grouped views (see Chapters) carry no month headings, so /changelog#2026-11 finds nothing there and stays at the top; the chapter and day rows are the way in. The terminal's Changelog screen prints the same month line ("November 2026", with its release count) over its releases, newest first; / drops a month whose releases no longer match, and Enter on a month line does nothing. In chapters the terminal shows chapter lines instead, as the page does.
Older releases (#12987)
/changelog reads the newest 30 live releases, so the first page stays small however many have shipped (under 40 KB with 500 pulls; the first page answered in about 11 ms median in test/changelog-window.test.ts). Below them, inside the live region, a plain link reads "Older releases, before 12 Mar" (the UTC day of the last release shown): it goes to ?before=owner/name#number, the last pull shown, and that page holds the next 30 older ones. Follow it until it is gone; the last page has no link. Nothing is on its way past the first page.
The repository and bet filters apply while the page is read, so ?repo=owner/name or ?bet=name gives 30 matching releases a page, and the link is there only when more matching ones remain; a filter matching a few shows them on one page with no link. The filters ride along in the link. A cursor that names no public pull is the first page, never an error. The page's ETag holds the cursor. The feeds, /api/v1/changelog and MCP releases are not paged.
App releases (#13707)
Say where the app tells its version, under app in forge.json:
{ "app": { "run": "bun src/main.ts", "version": "/healthz" } }
version is a path the running app answers (/healthz, JSON with a version string, or one line of
text) or a file in the commit (VERSION, package.json). When production, deployed from the
default branch, first serves a version the repository has not had, the forge records a release:
the version, the commit, the commit's subject and body as the note, the tests' verdict (pending,
passed, failed, none) and the time from the push to serving. A redeploy of the same version
records nothing; an app with no version records nothing.
Read them:
/{owner}/{name}/releases: the page, for whoever may read the repository.GET /api/v1/repos/{owner}/{name}/releases:{ items: [...] }, newest first;limit, andbefore(thecursorof the last item seen, so releases sharing a time are not skipped).GET /api/v1/changelog: areleaseslist beside the landed pulls, public repositories only;
?repo=owner/name narrows it.
- The terminal: the palette's
<owner>/<name> — Releaseswhile that repository is open.
Releases are recorded from the day the forge carries this; earlier deploys are not backfilled.
A release still pending when the forge restarts is settled to none on boot: its verdict went with the process. Reads are capped: the app's answer at 4 KB (the stream is cancelled), a version file at 64 KB.
Nothing released yet
When no pull has landed, /changelog shows one sentence in place of the "Live:" line and "Nothing has shipped yet.": "Running <version · commit>; changes appear on release." A development build says "a development build" when no commit is known. The terminal's Changelog screen, with no releases, reads "No releases yet" and "Changes appear on release." The page is held to the first-view word budget in test/attention.test.ts, which is why the sentence is short. Tested in test/changelog.test.ts.