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 #6915

Parked opened this
Closed without merging

/changelog shows the last 30 releases, newest first, each with its date and the pulls it carries. Anyone can read it without signing in, and every page's footer links to it, so it is one tap from the feed. The branch is unchanged since the last attempt, so this push adds no new commits.

Notes

stopped parked by the crew deploy 13b4e3c

opened this

/changelog shows the last 30 releases, newest first, each with its date and the pulls it carries. Anyone can read it without signing in, and every page's footer links to it, so it is one tap from the feed. The branch is unchanged since the last attempt, so this push adds no new commits.

The earlier check failed on GET /settings/tokens names its phases and answers within its budget. That test is in test/settings-timing.test.ts, and /changelog doesn't touch the page it covers. The only shared piece is the footer link added to src/web/layout.ts. I take the failure to be a timing flake on a loaded check machine, not a defect in this change. I can't confirm that from here, since the check log wasn't available to me.

On this branch, test/changelog.test.ts and test/settings-timing.test.ts pass, bun x tsc --noEmit is clean, and the design lint passes. I did not run the full check, and I did not start the app to load /changelog in a browser.

I added no dependencies, and I left out pagination, filtering and an RSS feed. The route and page are in src/http/server.ts and src/web/pages/changelog.ts, and the path is reserved in src/core/reserved.ts.

To try it, open /changelog on the preview, or run bun test test/changelog.test.ts.

If the timing test fails again, it needs its own fix, either a looser budget or a retry. I'd rather that went in a separate pull than here.

Closes #6096

commented

/changelog shows the last 30 releases, newest first, each with its date and the pulls it carries. Anyone can read it without signing in, and every page's footer links to it, so it is one tap from the feed. The branch is unchanged since the last attempt, so this push adds no new commits.

The earlier check failed on GET /settings/tokens names its phases and answers within its budget. That test is in test/settings-timing.test.ts, and /changelog doesn't touch the page it covers. The only shared piece is the footer link added to src/web/layout.ts. I take the failure to be a timing flake on a loaded check machine, not a defect in this change. I can't confirm that from here, since the check log wasn't available to me.

On this branch, test/changelog.test.ts and test/settings-timing.test.ts pass, bun x tsc --noEmit is clean, and the design lint passes. I did not run the full check, and I did not start the app to load /changelog in a browser.

I added no dependencies, and I left out pagination, filtering and an RSS feed. The route and page are in src/http/server.ts and src/web/pages/changelog.ts, and the path is reserved in src/core/reserved.ts.

To try it, open /changelog on the preview, or run bun test test/changelog.test.ts.

If the timing test fails again, it needs its own fix, either a looser budget or a retry. I'd rather that went in a separate pull than here.

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