Gitea holds the downloads made before the move, so the worker sums
both hosts' asset download counts (update manifests excluded). Gitea is
read with the same five-minute cache and a five-second limit; when it
is down or answers oddly, the count is GitHub's alone. Downloads stay
on GitHub only.
Co-Authored-By: Claude <noreply@anthropic.com>
The worker reads the newest release and download counts from GitHub's
API, with an optional GITHUB_TOKEN secret for the rate limit. Download
links go to GitHub's latest release, and the source link wears the
GitHub mark. The "not notarized" notice goes: macOS builds are signed
and notarized now.
Co-Authored-By: Claude <noreply@anthropic.com>
/release.json adds the sum of every release asset's downloads; the
update manifests are the apps' checks, not downloads.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A worker answers /release.json from the Gitea API (Gitea sends no
CORS headers, so the page cannot ask it directly).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
ZacharyZhang-NYandClaude