Repository navigation
CapsuleCraft v1.8.1
CapsuleCraft v1.8.1 — a release pipeline that does not lose artifacts
Released 2026-10-27.
This is a patch release of the build system, not of the app. No application
code changed between v1.8.0 and v1.8.1 — the binaries are v1.8.0 features, built
by a pipeline that now actually delivers all of them.
Why this release exists
v1.8.0 was published without its Linux AppImage and without the macOS .app.zip.
The cause was a race, not a code bug: the native jobs finish in 2–3 minutes, and
they called gh release upload before tauri-action had created the GitHub
Release (7–10 minutes). The uploads died with 404 release not found, and the
release was published anyway, minus those files. The published checksums were
also overwritten by each job in turn, so SHA256SUMS.txt covered only one
platform.
PR #13 by @kobaltgit rebuilt the pipeline. This
release is the first one to run it.
What changed in the pipeline
create-releaseruns first and guarantees the GitHub Release exists before
any builder starts — the race is structurally impossible now. Release notes are
taken from this file (docs/releases/<tag>.md).- Native Windows build (
native-windows): a zero-dependency portable
CapsuleCraft_native_<version>_x64.zipcontainingCapsuleCraft.exe,
README.mdandLICENSE. No WebView2, no installer. finalize-releasewaits for every builder, downloads all assets, writes a
single authoritativeSHA256SUMS.txt, uploads it, and only then clears the
draft flag.- CI now tests the native shell (
cargo check+cargo test -j 1) on every
pull request and push tomain, next to the existing frontend and Tauri jobs. if-no-files-found: warnplus a complete bundle-path list, so the macOS
Tauri job stops failing because a Windows-only mask matched nothing.
Fixed during this release
- The AppImage's
appdata.xmlhad<release version="1.8.0" date="2026-10-26"/>
hardcoded in the workflow; it is now generated from the tag and the build date. finalize-releasepublished the release unconditionally (if: always()), even
when a build had failed. It now refuses to publish an incomplete artifact set
and leaves the release as a draft.- Manifest drift:
src-tauri/Cargo.tomlwas at1.5.0andpackage-lock.jsonat
1.4.0; both now matchpackage.json,tauri.conf.jsonandnative/Cargo.toml.
Artifacts
| Platform | File |
|---|---|
| Linux x64 | CapsuleCraft_1.8.1_amd64.AppImage, CapsuleCraft_1.8.1_amd64.deb, CapsuleCraft-1.8.1-1.x86_64.rpm |
| macOS arm64 | CapsuleCraft_native_1.8.1_arm64.app.zip, CapsuleCraft_1.8.1_aarch64.dmg |
| Windows x64 | CapsuleCraft_native_1.8.1_x64.zip, CapsuleCraft_1.8.1_x64_en-US.msi, CapsuleCraft_1.8.1_x64-setup.exe |
SHA256SUMS.txt covers every artifact above in a single file.
Upgrading
Nothing on disk changes: the .eml vault format, X-Capsule-* headers and the
app-data folder are untouched. v1.8.1 opens any vault written by v1.8.0 or
earlier, and the other way round.