F
Fred Turkington
Imported from GitHub feature request.
Source issue:
Original context from GitHub:
Get added as a Homebrew Cask - at brew.sh. We can follow instructions at https://docs.brew.sh/Adding-Software-to-Homebrew
PR a .rb file into https://github.com/Homebrew/homebrew-cask/tree/main/Casks/t with with the GitHub URL of the released .dmg
Additional context from comments:
  • @prodrigues1912: Some context that might help whoever picks this up:
Pre-release status.
All current Tolaria releases are marked as pre-release (alpha builds, several per day).
homebrew/homebrew-cask
prefers stable releases, and
homebrew-cask-versions
— which used to host betas — was deprecated and archived in 2024.
brew audit
tends to flag alpha/pre-release artifacts, so a PR today would likely be rejected.
Two paths that usually work better in this situation:
  1. Self-hosted tap
    (e.g.
    refactoringhq/homebrew-tolaria
    ). Users install with
    brew install --cask refactoringhq/tolaria/tolaria
    . Full control over alpha cadence, and easy to migrate to the official tap later without breaking existing installs.
  2. Wait for a stable release channel
    and submit that to
    homebrew/homebrew-cask
    .
Asset format.
The issue mentions a
.dmg
, but current releases ship
Tolaria.app.tar.gz
plus a Sparkle-style
.sig
. A cask can reference a
.tar.gz
directly, so that works — it's mostly a question of whether to add a
.dmg
build step or keep the tarball as the canonical asset.
Sparkle.
If the app ships Sparkle auto-update, Homebrew usually wants it either disabled in the cask build or noted in
caveats
, since users expect
brew upgrade
to be the update path.
Would love to see this land too.