Move releases to GitHub, with one bridge release on Gitea

GitHub has no generic package registry, so releases become GitHub
release assets. The updater and install.sh read releases/latest/download
and releases/download/<v>/, plain redirects with no API rate limit.
make release publishes a draft with all assets, then makes it latest.
make release-gitea publishes the same version to the old Gitea registry
for binaries that still update from there, and refuses until GitHub
serves it. See D33.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
2026-10-25 22:38:50 +01:00
co-authored by Claude Opus 5.5
parent c9932932bb
commit 1ee394cfdf
12 changed files with 182 additions and 93 deletions
+8 -3
View File
@@ -1,8 +1,13 @@
# Copy to .env (gitignored); the Makefile loads it automatically.
# Access token with write:package scope. Required for `make release`.
GITEA_TOKEN=
# GitHub token with contents:write on the repo, for `make release`.
# Not needed if `gh auth login` was run.
# GH_TOKEN=
# Optional overrides (defaults shown).
# Optional override (default shown).
# GITHUB_REPO=simonfranken/submarine
# Bridge release only (`make release-gitea`): token with write:package scope.
GITEA_TOKEN=
# GITEA_URL=https://git.simon-franken.de
# GITEA_OWNER=simonfranken