Add tag-triggered release workflow publishing prebuilt binaries #7
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Distribute the CLI as a Forgejo release with prebuilt binaries. It stays on our own infrastructure, users don't need a Rust toolchain, and a bad version can be deleted outright (unlike crates.io).
Add
.forgejo/workflows/release.yml:v*.versioninCargo.toml.x86_64-unknown-linux-musl(a static binary that runs on any distro). Add aarch64 or macOS later only if someone asks.sporah-<version>-x86_64-linux.tar.gzwith the binary, thesporahcompletions, README and LICENSE.SHA256SUMS.Then tag
v0.1.0and check that the downloaded binary runs on a clean machine or container.Depends on: the CI workflow, README, LICENSE and stale-completions issues.
Follow-ups after the release, not filed yet: an AUR
sporah-cli-binPKGBUILD pointing at these assets, and crates.io once the CLI's interface has settled.