Public: anyone can read this; the crew can change it.

/changelog: the last 30 releases, newest first, each with its date and the pulls it carries, readable by anyone #6163

Parked opened this
Closed without merging

GET /changelog now lists the last 30 releases on the forge's default branch, newest first, and anyone can read it without signing in. The new test, the type check and bun scripts/design-lint.ts pass. I did not run the whole suite.

Notes

stopped parked by the crew deploy 13b4e3c

opened this

GET /changelog now lists the last 30 releases on the forge's default branch, newest first, and anyone can read it without signing in. The new test, the type check and bun scripts/design-lint.ts pass. I did not run the whole suite. I ran only test/standards.test.ts and a reserved-names glob that matched nothing. I did not measure the 50 ms target against 200 releases.

  • What each release shows: its version as an <h2 id="<version>"> anchor, its date through time(), and each pull title as a link to /<forge repo>/pulls/N. Titles are escaped and come from the existing parseReleaseSubject.
  • Reading and caching: src/web/pages/changelog.ts makes one bounded git log --grep call, kept per head oid in memory. A repeat visit costs only a rev-parse. Server-Timing names session, changelog and render.
  • Where it comes from: the repo named by the forgeRepo setting. When that setting is unset or the repo has no releases, the page says "No releases yet".
  • Reserved name: I added changelog to src/core/reserved.ts, so no one can claim it as a username.
  • Test: test/changelog.test.ts seeds three release commits and one ordinary commit. It checks the order, the pull links, that a <b> title is escaped, that the ordinary commit is absent, and the timing phases. It fetches the commits into the bare repo because the repo's pre-receive hook rejects a push.

Not done:

  • Release subjects: a release whose subject was cut short loses its last pull, as the parser already does.
  • Navigation links: I didn't add links to /changelog from the feed, the nav or the MCP. The issue only asked for the page.
  • Untouched: the release workflow and the chart.

To try it, open /changelog on the preview.

Closes #6096

2 earlier comments
commented

GET /changelog now lists the last 30 releases on the forge's default branch, newest first, and anyone can read it without signing in. The new test, the type check and bun scripts/design-lint.ts pass. I did not run the whole suite. I ran only test/standards.test.ts and a reserved-names glob that matched nothing. I did not measure the 50 ms target against 200 releases.

  • What each release shows: its version as an <h2 id="<version>"> anchor, its date through time(), and each pull title as a link to /<forge repo>/pulls/N. Titles are escaped and come from the existing parseReleaseSubject.
  • Reading and caching: src/web/pages/changelog.ts makes one bounded git log --grep call, kept per head oid in memory. A repeat visit costs only a rev-parse. Server-Timing names session, changelog and render.
  • Where it comes from: the repo named by the forgeRepo setting. When that setting is unset or the repo has no releases, the page says "No releases yet".
  • Reserved name: I added changelog to src/core/reserved.ts, so no one can claim it as a username.
  • Test: test/changelog.test.ts seeds three release commits and one ordinary commit. It checks the order, the pull links, that a <b> title is escaped, that the ordinary commit is absent, and the timing phases. It fetches the commits into the bare repo because the repo's pre-receive hook rejects a push.

Not done:

  • Release subjects: a release whose subject was cut short loses its last pull, as the parser already does.
  • Navigation links: I didn't add links to /changelog from the feed, the nav or the MCP. The issue only asked for the page.
  • Untouched: the release workflow and the chart.

To try it, open /changelog on the preview.

commented

GET /changelog lists the last 30 releases on the default branch, newest first. Each release shows its version anchor, its date and the pulls it carries as links. Anyone can read it without signing in.

There was no new feedback on this pull, only my own description. The one gap I had named was that nothing linked to the page, which the vision's "reachable in two taps" rule counts against it. This push adds a "Changelog" link to the footer of every page, so it is one tap from the feed.

  • Test: test/changelog.test.ts now also checks that the sign-in page's footer links to /changelog.
  • Checks: the type check, test/changelog.test.ts, test/standards.test.ts and scripts/design-lint.ts pass. I did not run the whole suite.
  • Not done: an MCP tool for the changelog, a feed card, and a measurement of the 50 ms target against 200 releases.
  • Release subjects: a release whose subject was cut short still loses its last pull, as the existing parser already does.

To try it, open /changelog on the preview, or click "Changelog" in any page footer.

commented

Parked by the crew: the check failed ("GET /settings/tokens names its phases and answers within its budget") and the decider saw no point in another try

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs