Skip to content

Drop the leftover updater tarball and clarify release asset names - #27

Merged
jonathanlaf merged 1 commit into
mainfrom
fix/release-artifact-naming
Sep 12, 2026
Merged

jonathanlaf merged 1 commit into
mainfrom
fix/release-artifact-naming

Conversation

@jonathanlaf

Copy link
Copy Markdown
Owner

Summary

  • removes "app" from tauri.conf.json's bundle.targets — this was the cause of KeyAura_aarch64.app.tar.gz showing up on every release even though there's no updater plugin configured to ever fetch it. Verified locally with a real cargo tauri build: the .dmg still builds correctly (the .app is still built as an internal intermediate step for dmg packaging, it's just no longer separately exposed/tarred as a release artifact)
  • renames each platform's installer to something self-explanatory: KeyAura_0.1.4_aarch64.dmg → KeyAura_0.1.4_macOS-AppleSilicon.dmg, KeyAura_0.1.4_x64-setup.exe → KeyAura_0.1.4_Windows-x64.exe, via a new platform_label matrix field a future Linux leg can extend with the same "OS-arch" naming rather than inventing something new
  • also manually cleaned up the already-published v0.1.4 release's assets to match (with explicit approval, since it's live, not a draft)

Verification

  • cargo fmt --check, cargo clippy --all-targets -- -D warnings (dev and release), cargo test — clean, 33 passing
  • real local cargo tauri build confirming the dmg still builds correctly and no .app.tar.gz/stray files remain in the bundle output
  • reviewed with /code-review (medium); found and fixed one real bug before this PR: the rename step originally used cp instead of mv, which would've left the bundler's original-named file behind — the next step's provenance-attestation glob (*.dmg/*.exe) would then match both files and attest over a name no longer even published

Removing "app" from bundle.targets stops Tauri from also exposing the raw
.app bundle as a release artifact — tauri-action was tarring it up as
KeyAura_aarch64.app.tar.gz on every release even though this app has no
updater plugin configured to ever consume it. Verified locally: dmg
packaging still builds the .app internally as an implicit intermediate
step, so the actual installer is unaffected.

Also renames each platform's installer from the bundler's default naming
(KeyAura_0.1.4_aarch64.dmg, KeyAura_0.1.4_x64-setup.exe) to something
self-explanatory (KeyAura_0.1.4_macOS-AppleSilicon.dmg,
KeyAura_0.1.4_Windows-x64.exe), via a per-matrix-leg platform_label field
that a future Linux leg can extend without inventing a new convention.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@jonathanlaf
jonathanlaf merged commit cd49116 into main Sep 12, 2026
3 checks passed
@jonathanlaf
jonathanlaf deleted the fix/release-artifact-naming branch September 12, 2026 03:47
jonathanlaf added a commit that referenced this pull request Sep 15, 2026
## Summary
Version bump only — the features shipping in this release (#27, #28)
were merged straight to `main` rather than through this release branch,
so the automated release-notes script won't pick them up. Noting them
here manually:

- #27 — drop the leftover updater tarball from releases, clearer
per-platform asset naming
- #28 — macOS auto-update: checks for updates on launch and via a tray
"Check for Updates…" item, with a
confirm-before-download/confirm-before-restart flow; signing key
generated and wired into CI

## Verification
- `cargo fmt --check`, `cargo clippy --locked --all-targets -- -D
warnings` (dev and release), `cargo test --locked` — clean, 33 passing
- `node --test ui/test/*.test.mjs` — 38 passing
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant