Cupertino moved to Codeberg. Update your Homebrew tap.

Short version: Cupertino’s working distribution home is now Codeberg.

If you installed Cupertino from the old GitHub tap, brew upgrade can tell you that everything is current while leaving you on 1.4.1. That is not the current working release. The current release is 1.4.2, and it lives in the new Codeberg tap.

Update an existing install

Run this exactly:

brew tap cupertinohq/tap https://codeberg.org/CupertinoHQ/homebrew-tap.git
brew fetch cupertinohq/tap/cupertino
brew uninstall mihaelamj/tap/cupertino || true
brew install cupertinohq/tap/cupertino
brew untap mihaelamj/tap || true
cupertino --version

Expected output:

1.4.2

Then check your databases:

cupertino doctor

If you need to download the databases again:

cupertino setup

Fresh install

For a new Homebrew install:

brew tap cupertinohq/tap https://codeberg.org/CupertinoHQ/homebrew-tap.git
brew install cupertinohq/tap/cupertino
cupertino setup

The explicit Codeberg URL matters. If you run only:

brew tap cupertinohq/tap

Homebrew assumes GitHub. That is not where the working tap lives.

How to tell if you are still on the old path

Run:

brew info cupertino

If you see this:

From: https://github.com/mihaelamj/homebrew-tap/...
Tap: mihaelamj/tap
stable 1.4.1

you are still looking at the old GitHub tap.

The working tap should resolve to:

From: https://codeberg.org/CupertinoHQ/homebrew-tap.git/Formula/cupertino.rb
Tap: cupertinohq/tap
stable 1.4.2

What changed in 1.4.2

This is a distribution hotfix, not a corpus rebuild.

• Source moved to codeberg.org/CupertinoHQ/cupertino

• Homebrew moved to codeberg.org/CupertinoHQ/homebrew-tap

• The Homebrew formula downloads the 1.4.2 binary from Codeberg packages

• cupertino setup downloads the database bundle from cupertino-assets.fly.dev

• The database bundle is still version 1.4.0

• The schema is unchanged

That means your existing v1.4.0 databases remain valid. If cupertino doctor says all checks passed, you do not need to download the databases again.

Why brew upgrade was confusing

Homebrew compares your installed formula against the tap it knows about. If your machine is still tapped to the old GitHub formula and that formula says 1.4.1, Homebrew can report “nothing to upgrade” even though the working Codeberg tap has 1.4.2.

The fix is not just brew upgrade. The fix is switching taps.

The old GitHub setup path is obsolete

The old GitHub release asset can return 404. Cupertino 1.4.2 no longer depends on that path for setup.

The current setup path is:

https://cupertino-assets.fly.dev/releases/v1.4.0/cupertino-databases-v1.4.0.zip
https://cupertino-assets.fly.dev/apple-constraints.json

I tested the new path end to end: Homebrew installs 1.4.2, cupertino setup downloads the bundle, the constraints sidecar downloads, and all 8 databases verify.

Source installs

If you build from source, clone the Codeberg repo:

git clone https://codeberg.org/CupertinoHQ/cupertino.git
cd cupertino

The old GitHub URLs should be treated as legacy references. Codeberg is the working home now.