.gitea/workflows/release.yaml on a v* tag: stamp the workspace version into tauri.conf.json and ui/package.json, build the webview, run cargo tauri build for the Linux targets on rust-gtk3, and attach the artifacts to a Gitea release. Windows and macOS builders are a separate concern (a self-hosted runner on each, or a cross-build) and get their own child once the Linux path is proven.
Acceptance
Pushing a tag produces a Gitea release with an AppImage and a .deb whose --version prints the tag.
Parent: #5
## Scope
`.gitea/workflows/release.yaml` on a `v*` tag: stamp the workspace version into `tauri.conf.json` and `ui/package.json`, build the webview, run `cargo tauri build` for the Linux targets on `rust-gtk3`, and attach the artifacts to a Gitea release. Windows and macOS builders are a separate concern (a self-hosted runner on each, or a cross-build) and get their own child once the Linux path is proven.
## Acceptance
Pushing a tag produces a Gitea release with an AppImage and a `.deb` whose `--version` prints the tag.
## Depends on
#12 (green CI).
grenade
added the child label 2026-09-15 12:41:41 +00:00
Done by the v0.1.0 tag, release run 36. The Gitea release v0.1.0 carries the deb, the rpm, the AppImage with its .sig, the bare binary and SHA256SUMS. The downloaded AppImage matches its checksum and prints blackbeard-wallet 0.1.0.
Getting there took three fixes: the binary's name after the product rename and where the Tauri CLI runs (aa6ad55), and xdg-utils in the rust-gtk3 image (gongfoo b997f73), which the AppImage bundler copies in for the opener plugin. Run 35 failed on the last of these. This Gitea has no rerun API, so the tag was deleted and pushed again at the same commit; nothing had been released by the failed run.
Done by the `v0.1.0` tag, release run 36. The Gitea release [v0.1.0](https://git.lair.cafe/blackbeard/wallet/releases/tag/v0.1.0) carries the deb, the rpm, the AppImage with its `.sig`, the bare binary and `SHA256SUMS`. The downloaded AppImage matches its checksum and prints `blackbeard-wallet 0.1.0`.
Getting there took three fixes: the binary's name after the product rename and where the Tauri CLI runs (`aa6ad55`), and `xdg-utils` in the rust-gtk3 image (gongfoo `b997f73`), which the AppImage bundler copies in for the opener plugin. Run 35 failed on the last of these. This Gitea has no rerun API, so the tag was deleted and pushed again at the same commit; nothing had been released by the failed run.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Parent: #5
Scope
.gitea/workflows/release.yamlon av*tag: stamp the workspace version intotauri.conf.jsonandui/package.json, build the webview, runcargo tauri buildfor the Linux targets onrust-gtk3, and attach the artifacts to a Gitea release. Windows and macOS builders are a separate concern (a self-hosted runner on each, or a cross-build) and get their own child once the Linux path is proven.Acceptance
Pushing a tag produces a Gitea release with an AppImage and a
.debwhose--versionprints the tag.Depends on
#12 (green CI).
Done by the
v0.1.0tag, release run 36. The Gitea release v0.1.0 carries the deb, the rpm, the AppImage with its.sig, the bare binary andSHA256SUMS. The downloaded AppImage matches its checksum and printsblackbeard-wallet 0.1.0.Getting there took three fixes: the binary's name after the product rename and where the Tauri CLI runs (
aa6ad55), andxdg-utilsin the rust-gtk3 image (gongfoob997f73), which the AppImage bundler copies in for the opener plugin. Run 35 failed on the last of these. This Gitea has no rerun API, so the tag was deleted and pushed again at the same commit; nothing had been released by the failed run.