One command
This is the whole release.
Why it exists
Shipping a Mac app is the part nobody tells you about.
You can build the app. Then comes code signing, hardened runtime, notarization, stapling, Gatekeeper, a Sparkle appcast, a Homebrew cask — and the dreaded “app is damaged and can’t be opened.”
Microsoft App Center hosted Sparkle feeds for years, then shut it down with nothing to replace it. Shipcast is that missing piece: the CLI does the signing dance on your machine, and the hosted feed keeps every installed copy updating itself.
What you get
Everything between “it builds” and “it’s installed.”
Sign & notarize
Developer ID signing, hardened runtime, notarization, and stapling — or ad-hoc signing when you don't have an Apple account yet. Your certificates never leave your machine.
A hosted update feed
Shipcast hosts your Sparkle appcast at a stable URL. Ship a new tag and every installed copy sees the update — no server to run, no App Center to replace.
Homebrew, automatically
Every release generates a Homebrew cask and opens the pull request for you. Users install and update with brew, and the “app is damaged” prompt is handled.
One command, or your CI
Run the whole pipeline locally with shipcast release, or drop the GitHub Action into your repo and let a pushed tag do it. Same result either way.
Pricing
The CLI is free forever. The hosting is free during beta.
Shipcast CLI
Free
forever · MIT licensed
The entire build, sign, notarize, package, and cask pipeline is open source. Self-host your appcast and you never pay a cent.
Hosted feed
Free during beta
then ~$9/mo per app
The update URL and adoption dashboard. You already pay Apple for the certificate — this is the part that puts the app in your users’ hands and keeps it current.
Your next release could install with brew.
brew install mafex11/tap/shipcast