Skip to content

feat: add Homebrew distribution channel for vstack - #66

Merged
eschaar merged 2 commits into
eschaar:mainfrom
mdvanes:feature/publish_in_homebrew
Jun 2, 2026
Merged

feat: add Homebrew distribution channel for vstack#66
eschaar merged 2 commits into
eschaar:mainfrom
mdvanes:feature/publish_in_homebrew

Conversation

@mdvanes

@mdvanes mdvanes commented Jun 2, 2026

Copy link
Copy Markdown
Collaborator
  • Introduced a new publish-homebrew job in the CI/CD pipeline to support Homebrew distribution.
  • Updated documentation to reflect the new Homebrew tap, including architecture overview, design documents, and product requirements.
  • Added contract tests for the Homebrew publish workflow to ensure proper functionality and security checks.
  • Updated the roadmap to include Homebrew distribution as an active work item.
  • Prepare release version 3.5.0, enabling Homebrew as a secondary installation method for macOS and Linux users.

- Introduced a new `publish-homebrew` job in the CI/CD pipeline to support Homebrew distribution.
- Updated documentation to reflect the new Homebrew tap, including architecture overview, design documents, and product requirements.
- Added contract tests for the Homebrew publish workflow to ensure proper functionality and security checks.
- Updated the roadmap to include Homebrew distribution as an active work item.
- Released version 3.5.0, enabling Homebrew as a secondary installation method for macOS and Linux users.
@mdvanes
mdvanes requested a review from eschaar as a code owner June 2, 2026 13:09

@eschaar eschaar left a comment

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

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

Approved.

Great addition overall: the Homebrew publish path is well structured, runs after a successful PyPI publish, and includes solid checksum/contract validation.

I’m approving this now because the Homebrew path is currently protected by the feature flag (HOMEBREW_TAP_ENABLED=false), so this can merge safely without changing active release behavior.

I will open a small follow-up PR myself before enabling the flag, to finalize hardening and operational setup:

  1. Switch cross-repo dispatch auth to a GitHub App token (instead of PAT).
  2. Make dispatch signing/config fully required (not optional).
  3. Verify all related secrets and permissions are correctly configured.
  4. Update/extend workflow contract tests for the final auth/signing setup.

After that follow-up is merged and verified, the flag will be enabled.

@eschaar
eschaar merged commit 6939f31 into eschaar:main Jun 2, 2026
14 checks passed
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.

2 participants