Move the cask to the org-wide tap and fail loudly without the token

[kaidesu]

What changed

• .goreleaser.yml: the cask now goes to ghost-language/homebrew-tap instead of ghost-language/homebrew-ghost.
• .goreleaser.yml: skip_upload is gone, so the push always happens.
• .github/workflows/release.yml: verify checks HOMEBREW_TAP_TOKEN is present on release events, before anything is built.
• Dropped a stale comment about deleting Formula/ghost.rb from the tap — that's done.

Why the shared tap

Lumen ships a cask in ghost-language/lumen#19, and a tap per project means users tap twice for two projects from the same org. One brew tap ghost-language/tap now covers both, and anything else that ships a binary later.

brew tap ghost-language/tap
brew install --cask ghost-language/tap/ghost

Why the silent skip had to go

skip_upload was derived from the presence of the token:

skip_upload: '{{ if .Env.HOMEBREW_TAP_TOKEN }}false{{ else }}true{{ end }}'

The intent was reasonable — don't fail a release whose binaries are already published. The effect was worse than a failure. v1.0.0-beta.3 released with no token set: the run went green, nine archives published, and the tap was never touched. Nothing in the log said so above debug level, and it only surfaced when brew install found nothing.

Checking in verify inverts that. A missing token now costs one job that hasn't built anything, and the error says exactly what to add.

For existing users

Anyone tapped on ghost-language/homebrew-ghost keeps the 1.0.0-beta.3 cask sitting there — it stays installable. They need to re-tap to receive anything newer:

brew untap ghost-language/ghost
brew tap ghost-language/tap

Given 1.0.0-beta.3 is a few hours old, that population is approximately nobody.

Note

HOMEBREW_TAP_TOKEN currently on this repo is scoped to homebrew-ghost. It needs re-scoping to homebrew-tap, or the first release after this merges fails in verify — loudly, which is the point.

🤖 Generated with Claude Code