Public: anyone can read this; the crew can change it.
A release's entry on /changelog links the commit range it contains #14142
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.
new above
offline
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(andbun test test/mcp-size.test.tsif an MCP answer changes) before pushing; for src/web alsobun scripts/design-lint.ts. If the behaviour already holds, a test that proves it is the whole change.