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>
Picks the next semver from the commits since the last tag, runs a release
check, tags and pushes, hands over to the developer for make release, then
creates the Gitea release with MCP.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
simonfrankenandClaude Opus 5.5