Skip to content

feat(build): publish Homebrew formula on release#1

Merged
howar31 merged 1 commit into
mainfrom
feat/homebrew-formula
Jul 4, 2026
Merged

feat(build): publish Homebrew formula on release#1
howar31 merged 1 commit into
mainfrom
feat/homebrew-formula

Conversation

@howar31

@howar31 howar31 commented Jul 4, 2026

Copy link
Copy Markdown
Owner

Adds Homebrew as a fourth install path, wired into the existing VERSION-driven release pipeline:

  • brews section in .goreleaser.yaml targeting howar31/homebrew-tap (Formula directory); skip_upload: auto keeps prereleases out of the stable tap formula
  • HOMEBREW_TAP_TOKEN passed to the goreleaser step in release.yml (repository secret already configured)
  • README install section and the generated skills install metadata now list brew install howar31/tap/dscrd

The formula itself lands in the tap on the next release (planned: 0.1.1 bump PR after this merges).

🤖 Generated with Claude Code

- goreleaser brews section (Formula dir, skip_upload auto for prereleases)
- pass HOMEBREW_TAP_TOKEN through the release workflow
- document brew install in README and the skills install metadata

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Code Review

This pull request adds Homebrew installation support by configuring GoReleaser to publish to a Homebrew tap, updating the README with installation instructions, and adding brew installer metadata to the skill templates and definitions. The reviewer identified an issue in both internal/skillgen/templates/index.md.tmpl and skills/dscrd/SKILL.md where the brew installer metadata incorrectly splits the tap and formula fields. To prevent installation failures, the metadata should use a single fully qualified formula name (e.g., howar31/tap/dscrd) in the formula field instead of a separate tap field.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

Comment on lines +16 to +19
- kind: brew
tap: howar31/homebrew-tap
formula: dscrd
bins: [dscrd]

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

medium

OpenClaw's brew installer expects the formula field to contain the fully qualified formula name (including the tap prefix, e.g., howar31/tap/dscrd), and does not support a separate tap field. If left as formula: dscrd, the installer will attempt to run brew install dscrd and fail because the formula is not in the official Homebrew core tap.

      - kind: brew
        formula: howar31/tap/dscrd
        bins: [dscrd]

Comment thread skills/dscrd/SKILL.md
Comment on lines +16 to +19
- kind: brew
tap: howar31/homebrew-tap
formula: dscrd
bins: [dscrd]

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

medium

OpenClaw's brew installer expects the formula field to contain the fully qualified formula name (including the tap prefix, e.g., howar31/tap/dscrd), and does not support a separate tap field. If left as formula: dscrd, the installer will attempt to run brew install dscrd and fail because the formula is not in the official Homebrew core tap.

Suggested change
- kind: brew
tap: howar31/homebrew-tap
formula: dscrd
bins: [dscrd]
- kind: brew
formula: howar31/tap/dscrd
bins: [dscrd]

@howar31
howar31 merged commit 76d72a7 into main Jul 4, 2026
1 of 2 checks passed
@howar31
howar31 deleted the feat/homebrew-formula branch July 4, 2026 08:30
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