Skip to content

Point Homebrew instructions at the v4 cask #191

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
robzolkos wants to merge 2 commits into from
Closed

Point Homebrew instructions at the v4 cask #191

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
a972ac3
Point Homebrew instructions at the v4 cask
robzolkos Jul 27, 2026
8ad8c34
Drop redundant brew trust step from 3.x upgrade path
robzolkos Jul 27, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 13 additions & 11 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -48,22 +48,24 @@ Use `fizzy doctor` any time you want a full health check of your install, config
yay -S fizzy-cli
```

**Homebrew (macOS):**

Latest stable Fizzy 3.x is available from the original tap:
**Homebrew (macOS and Linux):**

```bash
brew install robzolkos/fizzy-cli/fizzy-cli
brew install --cask basecamp/tap/fizzy
```

Fizzy 4 release candidates are available from [Releases](https://github.com/basecamp/fizzy-cli/releases).
Release candidates are not published to Homebrew. They are available from [Releases](https://github.com/basecamp/fizzy-cli/releases).

*Upgrading from Fizzy 3.x:* 3.x was distributed as the `fizzy-cli` formula from the `robzolkos/fizzy-cli` tap. That tap now points at this cask, so `brew update` will offer to move you across. If Homebrew reports that it cannot tap `basecamp/tap` automatically, finish the move yourself:
Comment thread
robzolkos marked this conversation as resolved.

@cubic-dev-ai cubic-dev-ai Bot Jul 27, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P3: This sentence is written as a guaranteed migration path, but migration depends on local tap/trust state. Using unconditional wording here can leave stale or inaccurate upgrade guidance; consider phrasing it conditionally (for example, "may offer to migrate you") and avoid asserting the tap’s current state as always true.

Prompt for AI agents 
Check if this issue is valid — if so, understand the root cause and fix it. At README.md, line 59:

<comment>This sentence is written as a guaranteed migration path, but migration depends on local tap/trust state. Using unconditional wording here can leave stale or inaccurate upgrade guidance; consider phrasing it conditionally (for example, "may offer to migrate you") and avoid asserting the tap’s current state as always true.</comment>

<file context>
@@ -48,22 +48,25 @@ Use `fizzy doctor` any time you want a full health check of your install, config
-Fizzy 4 release candidates are available from [Releases](https://github.com/basecamp/fizzy-cli/releases).
+Release candidates are not published to Homebrew. They are available from [Releases](https://github.com/basecamp/fizzy-cli/releases).
+
+*Upgrading from Fizzy 3.x:* 3.x was distributed as the `fizzy-cli` formula from the `robzolkos/fizzy-cli` tap. That tap now points at this cask, so `brew update` will offer to move you across. If Homebrew reports that it cannot tap `basecamp/tap` automatically, finish the move yourself:
+
+```bash
</file context>
Suggested change
*Upgrading from Fizzy 3.x:* 3.x was distributed as the `fizzy-cli` formula from the `robzolkos/fizzy-cli` tap. That tap now points at this cask, so `brew update` will offer to move you across. If Homebrew reports that it cannot tap `basecamp/tap` automatically, finish the move yourself:
*Upgrading from Fizzy 3.x:* 3.x was distributed as the `fizzy-cli` formula from the `robzolkos/fizzy-cli` tap. If your setup is eligible for migration, `brew update` may offer to move you across. If Homebrew reports that it cannot tap `basecamp/tap` automatically, finish the move yourself:


```bash
brew tap basecamp/tap
brew install --cask basecamp/tap/fizzy
brew uninstall --formula --force fizzy-cli
brew untap robzolkos/fizzy-cli
```

> [!WARNING]
> The Basecamp Homebrew tap command is for Fizzy 4 stable once it is released. Release candidates are not published to Homebrew.
>
> ```bash
> brew install --cask basecamp/tap/fizzy
> ```
Installing by fully-qualified name trusts the cask automatically, so no separate `brew trust` step is needed.

**Scoop (Windows):**
```bash
Expand Down