Skip to content

Issue 31 homebrew install#32

Merged
ernestoongaro merged 5 commits into
mainfrom
issue-31-homebrew-install
Apr 16, 2026
Merged

Issue 31 homebrew install#32
ernestoongaro merged 5 commits into
mainfrom
issue-31-homebrew-install

Conversation

@ernestoongaro
Copy link
Copy Markdown
Collaborator

see #31

Homebrew Rollout Plan

  1. Phase 1: ExploreOmni tap. Publish a tap-only formula to exploreomni/homebrew-tap from the release workflow. GoReleaser is still used for GitHub release artifacts and checksums, but not for the Homebrew formula itself. This supports brew install exploreomni/tap/omni, and brew tap exploreomni/tap && brew install omni until homebrew/core exists.
  2. Phase 2: homebrew/core. Submit a separate curated formula to homebrew/core so fresh installs can use brew install omni with no tap step.
  3. Migration window: keep the tap formula working even after the core formula lands so brew install omni resolves to homebrew/core, while brew install exploreomni/tap/omni remains valid while docs and downstream skills catch up.

The phase-1 tap formula is intentionally separate from the eventual homebrew/core formula. GoReleaser handles release packaging only. The release workflow then renders the tap formula directly from the published release checksums instead of using GoReleaser's deprecated brews integration, and the core formula will still be maintained separately.

Updated Homebrew installation instructions for clarity and removed outdated information.
Copy link
Copy Markdown
Contributor

@jacksweeney5 jacksweeney5 left a comment

Choose a reason for hiding this comment

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

lgtm

Copy link
Copy Markdown
Contributor

@n8agrin n8agrin left a comment

Choose a reason for hiding this comment

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

Would appreciate some cleanup here but otherwise lgtm

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.

This is kind of weird. Should probably either have a new plan file for this work, or delete this file and put the release instructions in a release.md file

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

Done in f745e3c

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.

Typically these are in bin/ dirs if they’re executable by humans and bots

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

Done in f745e3c

Comment thread DEVELOPMENT.md
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.

Let’s pls have these instructions in one place not two

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

Done in f745e3c

- Move scripts/render-homebrew-formula.sh to bin/ (executable scripts convention)
- Update .gitignore to ignore bin/omni binary only, not the whole bin/ dir
- Update references in DEVELOPMENT.md and release.yml
- Delete docs/superpowers/specs/2026-04-01-release-strategy-design.md (superseded by DEVELOPMENT.md)

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@ernestoongaro ernestoongaro merged commit 0de6c87 into main Apr 16, 2026
2 checks passed
@ernestoongaro ernestoongaro deleted the issue-31-homebrew-install branch April 16, 2026 00:15
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.

3 participants