Public: anyone can read this; the crew can change it.
/api/v1/changelog names the running commit's short id and when it went live instead of the word dev #13901
Check · Review · Land · Live done — Landed and live in production.
GET /api/v1/changelog now carries short and liveSince next to commit, and version is the release number or null, never "dev". I ran the changelog, MCP releases-card, status, OpenAPI and contract tests, plus tsc and the gate; they pass.
shipped production is serving it deploy 4adf612
6 earlier comments
GET /api/v1/changelog now carries short and liveSince next to commit, and version is the release number or null, never "dev". I ran the changelog, MCP releases-card, status, OpenAPI and contract tests, plus tsc and the gate; they pass. The gate asked for "Try", "No door" and "Looks" lines, and I put them in the last commit message. I did not run the full suite.
- Answer fields:
shortis the first 7 characters ofcommit, and null when no commit is stamped.liveSinceis the ISO time this build began serving, which is when the process booted. The change is insrc/release/answer.ts, and the contract text for the route now names the fields. - Same short id everywhere:
shortOf()insrc/kernel/version.tsis now the one place the 7 characters come from. llms.txt ("Running 1.2.3 at aaaaaaa") and the changelog answer use it./statuswithaccept: application/jsongainsversion,commitandshortfrom the same helper. - Tests:
test/changelog-api.test.tscovers the no-release case (versionnull,short, ISOliveSince). It also covers the release case, whereFORGE_VERSION=1.2.3makesversion"1.2.3" and/statusand llms.txt print the same short id. - Releases card: the MCP releases card read
versionas text and would have printed "live null". It now shows the number and the short id, or just the short id. I changed the assertion intest/mcp-releases-card.test.tsto match, because the old one expected the version string.
Left out:
launch.ts: I did not change it. Its "dev" is the fallback stamp that the health probe matches against, so changing it would break rollback detection. The word is hidden at the API boundary through the existingreleaseOf.- Atom feed and ETag: the changelog Atom feed and the ETag still use "dev" internally as a cache-key placeholder, so nothing outside shows it.
- Response schema: the OpenAPI contract describes this route in prose only, with no response-schema object, so the fields are named in that text.
To try it, open /api/v1/changelog on the preview and read short and liveSince. Then request /status with accept: application/json and check that it shows the same short.
<!-- look-pages 1aabc71c5cf7 --> Look pages for 1aabc71, from the gate:
look pages (inferred): "Looks: /changelog" is not a page of app.looks in forge.json; this pull changes src/web/feeds.ts, src/web/pages/changelog.ts, src/web/pages/status.ts and 2 more; the forge pictures / (src/web/feeds.ts), /docs (src/web/feeds.ts), /explore (src/web/feeds.ts) and 23 more, the pages whose routes import it. A "Looks: <path>" or "No look: <why>" line in a commit message overrides
The look-pages feedback is addressed: /api/v1/changelog now names the running commit's short id and when it went live, instead of the word dev. That feedback was about the look-pages line, not the code, so no code changed in this push.
The gate rejected my earlier Looks: /changelog line because /changelog isn't in app.looks in forge.json. That is a screenshot list, not a list of routes. I added a new empty commit with Looks: /releases, which is in the list. I didn't amend the old commit because that would need a force push. Every commit in the range is read for the override, so this should replace the inferred 26 pages.
/releases is the one page that changed visibly, since its card now shows the short id when the build has no release number. The other changes are JSON-only, on /api/v1/changelog and /status with accept: application/json. /changelog stays out of app.looks because it's a JSON-adjacent page and the screenshot list is curated.
To try it:
curl -H "authorization: Bearer $FORGE_TOKEN" https://lab--13901--forge-trevato-apps.open-platform.sh/api/v1/changelogand readshortandliveSince.- Open
/releaseson the same preview.
I didn't re-run the tests or type check, because nothing in the code changed.
<!-- look-pages 28fe4ad4e681 --> Look pages for 28fe4ad, from the gate:
look pages (named): this pull changes src/web/feeds.ts, src/web/pages/changelog.ts, src/web/pages/status.ts; a commit names /releases
GET /api/v1/changelog now names the running commit's short id and when it went live, instead of the word dev. The check failed because my earlier gate --fix had rewrapped comments I didn't write, in src/web/studio/cards.ts and two test files. I restored those three files to main, re-applied only the real edits, and pushed. After that:
bun scripts/gate.tsis clean, and its look-pages line names/releases.bun x tsc --noEmitis clean.test/changelog-api.test.tsandtest/mcp-releases-card.test.tspass, 18 tests.
I did not run the full suite.
What changed
- The changelog answer gives
versionas the release number, ornullfor a build that isn't a release; it is neverdevany more. - It also gives
short(the first 7 characters of the commit,nullwithout a commit) andliveSince(ISO time this build began serving). /statuswithaccept: application/jsoncarries the sameversion,commitandshort, and the/llms.txtline prints the same short id.- The releases card status line reads
live <version> · <short>, falling back to the short id alone, thenbuild. - The new test covers a release build, where
versionis the number andshortis the same on/statusand/llms.txt.
Left out: the page and terminal already printed the short id, so only the JSON answers changed. The /api/v1/changelog route's summary text in the contract now describes the new fields.
To try it: curl -H "authorization: Bearer $FORGE_TOKEN" https://lab--13901--forge-trevato-apps.open-platform.sh/api/v1/changelog and read short and liveSince. Open /releases on the same preview for the card.
<!-- look-pages 961d6900e466 --> Look pages for 961d690, from the gate:
look pages (named): this pull changes src/web/feeds.ts, src/web/pages/changelog.ts, src/web/pages/status.ts; a commit names /releases
The gate's note is informational, not a failure, and it needs no code change. bun scripts/gate.ts exits clean and prints the same line: look pages (named). It says the pull changes src/web/feeds.ts, src/web/pages/changelog.ts and src/web/pages/status.ts, and that a commit names /releases. /releases is in app.looks in forge.json, so the Looks: /releases line in commit 28fe4ad4e is valid. I made no changes and pushed nothing.
What the pull does: /api/v1/changelog now names the running commit's short id and when it went live (liveSince). version is the release number or null, never the word dev. The releases card shows the short id when the build has no release number.
What I left out: the page and the terminal already print the short id, so only the JSON answers change. GET /status with accept: application/json shows the same short id.
To try it: fetch /api/v1/changelog on the preview and read short and liveSince. For the visible change, open /releases.
One disagreement: the gate also notes three files with comment lines over 100 columns: src/web/studio/cards.ts, test/changelog-api.test.ts and test/mcp-releases-card.test.ts. I left them alone, because the note says the nightly rewrap handles them on main and my last commit deliberately kept the diff to the changed lines.
Checked on the preview: /api/v1/changelog returns version null, short 961d690 and an ISO liveSince. /status JSON returns the same short, and llms.txt says "Running a build from source at 961d690". No page markup changed, so the design principles are not touched. Next, two things: (1) add a real response schema for /api/v1/changelog so the new fields are machine-readable, since the summary prose is all that names them now; (2) in src/web/studio/cards.ts use the shared short id only and drop the commit.slice(0,7) fallback, so the 7-character rule lives in one place (shortOf).
GET /api/v1/changelognow carriesshortandliveSincenext tocommit, andversionis the release number ornull, never "dev". I ran the changelog, MCP releases-card, status, OpenAPI and contract tests, plustscand the gate; they pass. The gate asked for "Try", "No door" and "Looks" lines, and I put them in the last commit message. I did not run the full suite.shortis the first 7 characters ofcommit, and null when no commit is stamped.liveSinceis the ISO time this build began serving, which is when the process booted. The change is insrc/release/answer.ts, and the contract text for the route now names the fields.shortOf()insrc/kernel/version.tsis now the one place the 7 characters come from. llms.txt ("Running 1.2.3 at aaaaaaa") and the changelog answer use it./statuswithaccept: application/jsongainsversion,commitandshortfrom the same helper.test/changelog-api.test.tscovers the no-release case (versionnull,short, ISOliveSince). It also covers the release case, whereFORGE_VERSION=1.2.3makesversion"1.2.3" and/statusand llms.txt print the same short id.versionas text and would have printed "live null". It now shows the number and the short id, or just the short id. I changed the assertion intest/mcp-releases-card.test.tsto match, because the old one expected the version string.Left out:
launch.ts: I did not change it. Its "dev" is the fallback stamp that the health probe matches against, so changing it would break rollback detection. The word is hidden at the API boundary through the existingreleaseOf.To try it, open
/api/v1/changelogon the preview and readshortandliveSince. Then request/statuswithaccept: application/jsonand check that it shows the sameshort.Closes #13873