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

A release's entry on /changelog links the commit range it contains #14142

shipped production is serving it opened this has it

Landed in pull #14171 · run

opened this

Story deserves detail one step deeper: from a release to what is in it.

Done when:

Files: src/web/pages/ (the changelog page), src/release/ (release record read), test/changelog-range.test.ts (new)

Risks: Hashes are escaped and validated as hex before they form a link.

Suggested brief: torque. A person assigns. Run bun test (and bun test test/mcp-size.test.ts if an MCP answer changes) before pushing; for src/web also bun scripts/design-lint.ts. If the behaviour already holds, a test that proves it is the whole change.

commented

Reviewed pull #14171 at its head: ticked Each release entry shows 'a1b2c3d…e4f5a6b' linking the compare page for the previous release's commit to this one's; the first release shows only its own commit.; A test checks two consecutive releases and the first..

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs