wharfy 0.8 — bring a built bundle, ship your GUI too

Bring your own bundle

0.7 took binaries you’d already built. 0.8 takes bundles you’ve already built and signed — .dmg, .AppImage, .zip, .deb, .rpm — and ships your desktop app the same way. Declare bundle:, and wharfy uploads them and drives the GUI channels. Nothing is rebuilt or re-signed.

channels: [cask, releases]
bundle:
  name: My App
  bundles:
    - { os: darwin,  arch: universal, kind: dmg,      path: dist/MyApp-universal.dmg }
    - { os: linux,   arch: amd64,     kind: appimage, path: dist/MyApp-x86_64.AppImage }
    - { os: windows, arch: amd64,     kind: zip,      path: dist/MyApp-x64.zip }

tauri build (or anything) drops bundles in dist/, and wharfy release / wharfy publish do the rest.

One tap, CLI and GUI together

The Cask lands in the same tap as your CLI Formula, under its own token <app>-app, so a single wharfy status shows both:

homebrew   probed  published 1.0.0   acme/homebrew-app:Formula/app.rb
cask       probed  published 1.0.0   acme/homebrew-app:Casks/app-app.rb

Each bundle routes to its channel:

wharfy doesn’t notarize. A self-signed macOS bundle ships with a Gatekeeper note in the cask’s caveats, and publish flags it — no surprises for whoever installs it.

Getting it

brew upgrade wharfy / scoop update wharfy / go install github.com/ShiroDoromoto/wharfy/cmd/wharfy@latest. On Linux, from the apt / yum repo.