Skip to content

docs: correct tap token scope note + mention Homebrew tap-trust#7

Merged
sanketsudake merged 1 commit into
mainfrom
docs/tap-followups
Jul 16, 2026
Merged

docs: correct tap token scope note + mention Homebrew tap-trust#7
sanketsudake merged 1 commit into
mainfrom
docs/tap-followups

Conversation

@sanketsudake

Copy link
Copy Markdown
Owner

Two small doc follow-ups from the Homebrew tap setup (tap live, v0.1.0 released, cask auto-published, repo now public, install verified end to end).

  • .goreleaser.yaml — the HOMEBREW_TAP_GITHUB_TOKEN comment said a classic PAT with repo scope; it's actually a fine-grained PAT scoped to the homebrew-tap repo with Contents: read/write. Comment now matches reality.
  • README.md — recent Homebrew prints a tap-trust notice on first install from a third-party tap. Install still proceeds; added a one-line note plus the brew trust command to acknowledge it.

Docs only — no code or release-config behavior changes; goreleaser check still passes.

🤖 Generated with Claude Code

- .goreleaser.yaml: the HOMEBREW_TAP_GITHUB_TOKEN is a fine-grained PAT
  scoped to the tap repo (Contents: read/write), not a classic repo-scope
  PAT, as the previous comment implied.
- README: note that recent Homebrew may show a tap-trust notice on first
  install from a third-party tap, and how to acknowledge it.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@sanketsudake
sanketsudake merged commit 55bcd8b into main Jul 16, 2026
2 checks passed
@sanketsudake
sanketsudake deleted the docs/tap-followups branch July 16, 2026 14:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant