Archived
simonfrankenandClaude Opus 5.5
1ee394cfdf
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>
14 lines
423 B
Bash
14 lines
423 B
Bash
# Copy to .env (gitignored); the Makefile loads it automatically.
|
|
|
|
# GitHub token with contents:write on the repo, for `make release`.
|
|
# Not needed if `gh auth login` was run.
|
|
# GH_TOKEN=
|
|
|
|
# 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
|