Archived
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:
+2
-2
@@ -20,12 +20,12 @@ bare commit hash.
|
||||
## Install
|
||||
|
||||
```sh
|
||||
curl -fsSL https://git.simon-franken.de/simonfranken/submarine/raw/branch/main/install.sh | sh
|
||||
curl -fsSL https://raw.githubusercontent.com/simonfranken/submarine/main/install.sh | sh
|
||||
```
|
||||
|
||||
Installs `submarine` and the alias `sub` (linux/macOS, amd64/arm64) to
|
||||
`~/.local/bin`. Update with `submarine update`. Maintainers publish with
|
||||
`GITEA_TOKEN=… make release` (see [architecture](architecture.md#distribution)).
|
||||
`make release NOTES=…` (see [architecture](architecture.md#distribution)).
|
||||
|
||||
## Status
|
||||
|
||||
|
||||
Reference in New Issue
Block a user