Skip to content

fix(frontend): serve version history from release.json - #45

Merged
voltcrash merged 15 commits into
mainfrom
t3/diagnose-version-history-fetch
Oct 6, 2026
Merged

voltcrash merged 15 commits into
mainfrom
t3/diagnose-version-history-fetch

Conversation

@voltcrash

Copy link
Copy Markdown
Owner

Description

Opening version history currently makes unauthenticated GitHub API requests and fails with 403 when the network's shared quota is exhausted. Serve the latest ten public releases from /release.json instead, including the footer version. The modal displays this bounded list and links to GitHub releases for older history.

Daily production and manual frontend release flows regenerate the snapshot before building, including the release being deployed so history does not lag behind GitHub publication. Exclude drafts/prereleases, retain only names, tags, dates and Markdown notes, and bypass persistent hosting/service-worker caches. The checked-in snapshot contains all three currently published releases.

Checks

  • 55 tests across six focused suites: snapshot generation, daily deployment, JSON fetching, Markdown rendering, history modal and Worker asset serving.
  • pnpm oxlint --type-aware --type-check --format agent.
  • Frontend production build with the public Turnstile test key, backend build, and Worker site asset assembly; bundled release.json matches the source.
  • JSON lint and git diff --check.
  • Browser: footer and history load the local snapshot, no GitHub API requests, scrolling adds no requests, and the older-release link points to GitHub with a new-tab target.

@voltcrash
voltcrash merged commit 598d7f1 into main Oct 6, 2026
11 checks passed
@voltcrash
voltcrash deleted the t3/diagnose-version-history-fetch branch October 6, 2026 04:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant