Skip to content

build: Homebrew cask generation + brew install docs - #20

Open
tawAsh1 wants to merge 1 commit into
mainfrom
feat/homebrew-cask
Open

build: Homebrew cask generation + brew install docs#20
tawAsh1 wants to merge 1 commit into
mainfrom
feat/homebrew-cask

Conversation

@tawAsh1

@tawAsh1 tawAsh1 commented Jul 5, 2026

Copy link
Copy Markdown
Owner

Summary

Companion to the new tawAsh1/homebrew-tap: brew tap tawAsh1/tap && brew install --cask resolog.

  • .goreleaser.yaml gains a homebrew_casks section with skip_upload: true — GoReleaser renders the cask into dist/ on each release but never pushes it. Publishing to the tap stays a manual commit, deliberately: automating it would require a cross-repository write token in this repo's CI, a bigger attack surface than a two-minute manual step at this release cadence. (Casks, not the deprecated brews formulas — GoReleaser v2.10+ direction for precompiled binaries.)
  • The cask clears macOS's quarantine attribute post-install (binaries are provenance-attested but not Apple-notarized), per GoReleaser's documented pattern.
  • READMEs (en/ja): brew becomes the first install option.

The tap already carries a hand-written v0.4.0 cask matching this template; from the next release the flow is "copy dist/resolog.rb to the tap".

Test plan

  • Cask for v0.4.0 (same shape) installed locally: brew install --cask resologresolog version reports 0.4.0, Gatekeeper silent
  • goreleaser config is additive-only; release workflow untouched

🤖 Generated with Claude Code

skip_upload keeps the cross-repo write token out of CI; the generated cask
is committed to tawAsh1/homebrew-tap by hand. READMEs gain the brew install
path.
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