Homebrew support

[flatsponge]

Problem

not on homebrew

Requested behavior

publish on homebrew

Why it belongs in Zero

easier updates

Alternatives or workarounds considered

No response

Examples, screenshots, or prior discussion

No response

[vshuraeff]

==> zero ✘: stable 0.1.0 (bottled), HEAD
Terminal coding agent you own
https://zero.gitlawb.com/
Not installed
From: https://github.com/Homebrew/homebrew-core/blob/HEAD/Formula/z/zero.rb
License: MIT
==> Options
--HEAD
	Install HEAD version
==> Analytics
install: 44 (30 days), 44 (90 days), 44 (365 days)
install-on-request: 44 (30 days), 44 (90 days), 44 (365 days)
build-error: 0 (30 days)

[Vasanthdev2004]

There is a formula in homebrew-core already, as the output above shows, but it is pinned at 0.1.0 while the project has moved a long way past that, so anyone running brew install zero today gets something very old.

Keeping this open and rescoping it: the ask is no longer "publish on Homebrew", it is keeping the homebrew-core formula current. That needs whoever owns publishing, so flagging @kevincodex1.

Sorry this sat unanswered for a month.

[Vasanthdev2004]

Opened #910 for this, and it is deliberately not the whole thing.

What is in it: zero upgrade now recognises a Homebrew install and refuses, naming brew upgrade zero, instead of rewriting the binary inside the keg and leaving Homebrew describing a version that is no longer on disk. Detection is the keg shape rather than the Homebrew prefix, because /usr/local is a prefix on Intel Macs and also where people put hand-installed binaries, so matching the prefix would refuse updates for installs Homebrew never touched.

That ordering is the point. Publishing a tap first would have shipped that bug on day one, and it is the thing nobody asks for in a "please add Homebrew" thread.

Also in it, since the same thread kept asking for alternatives to npm: mise and go install both already worked and were simply never written down. INSTALL.md now opens with every method and how each one updates, rather than leading with npm.

Also in it: packaging/homebrew/zero.rb, a draft formula that installs nothing. Real checksums from the published v0.7.0 assets, so it can be exercised with brew install --build-from-source and brew audit today.

What is NOT in it, and why this issue stays open: the tap itself, and teaching the release workflow to bump the version and the four checksums on each tag. Both are release decisions and those are not mine to make. Whoever owns that has a working formula and an updater that already knows what to do.

[Vasanthdev2004]

Closing this as done. Checking it today rather than assuming, both halves are in place.

The formula is current. Homebrew/homebrew-core ships Formula/z/zero.rb at v0.8.0, which is the latest release (published 2026-08-21), with bottles for arm64_tahoe, arm64_sequoia, arm64_sonoma, sonoma, arm64_linux and x86_64_linux. @vshuraeff's paste showing stable 0.1.0 is what the rescope in this thread was about, and that gap is gone.

The repo half landed in #910. zero upgrade now recognises a Homebrew install and refuses rather than rewriting the binary inside the keg:

this zero was installed with Homebrew (%s); run `brew upgrade zero` instead,
so Homebrew's records match the binary on disk

Detection is by keg shape rather than by prefix (installmethod.go:53), which matters because /usr/local is a Homebrew prefix on Intel Macs and an ordinary install location everywhere else.

So brew install zero gets a current build and brew upgrade zero is the supported update path. That is the ask.

One leftover worth naming rather than leaving implied: packaging/homebrew/zero.rb is still in the tree at version "0.7.0" under a header saying NOT PUBLISHED, written as a draft for a Gitlawb/homebrew-tap that was never created. Nothing installs from it, so it is not a correctness problem, but it will drift further every release and someone will eventually read it as authoritative. Whether to delete it or stand up the tap is a release decision and belongs with whoever owns publishing, not in this issue.

Thanks @flatsponge for raising it and @vshuraeff for the version evidence that made the real problem clear.

[kostadin-damyanov-prime]

@Vasanthdev2004 Hi, thanks for working on homebrew support. It would be nice to update the README.md file with homebrew installation instruction so more people know that it is available there.