Skip to content

ci: auto-update Homebrew formula on new releases#19

Closed
naman485 wants to merge 1 commit into
mainfrom
feat/auto-update-homebrew
Closed

ci: auto-update Homebrew formula on new releases#19
naman485 wants to merge 1 commit into
mainfrom
feat/auto-update-homebrew

Conversation

@naman485
Copy link
Copy Markdown
Collaborator

@naman485 naman485 commented Apr 1, 2026

Summary

Adds an update-homebrew job to the release workflow so that every time a new version is tagged (v*), the Homebrew formula at NodeOps-app/homebrew-createos is automatically updated with the new version and SHA256 hashes.

How it works

  1. Release workflow builds binaries + SHA256 files (existing)
  2. New update-homebrew job runs after release job completes
  3. Downloads the 4 SHA256 files (darwin-arm64, darwin-amd64, linux-arm64, linux-amd64)
  4. Generates an updated Formula/createos.rb with new version + hashes
  5. Pushes to NodeOps-app/homebrew-createos

Setup required

Add a HOMEBREW_TAP_TOKEN secret to the createos-cli repo:

  • Create a GitHub PAT (fine-grained) with contents: write permission on NodeOps-app/homebrew-createos
  • Add it as a repo secret: Settings → Secrets → Actions → HOMEBREW_TAP_TOKEN

Test plan

  • Create HOMEBREW_TAP_TOKEN secret
  • Tag a test release (e.g., v0.0.4)
  • Verify homebrew-createos/Formula/createos.rb is auto-updated
  • brew upgrade createos picks up the new version

🤖 Generated with Claude Code

Adds an `update-homebrew` job to the release workflow that:
- Downloads SHA256 checksums from the just-published release
- Generates an updated Formula/createos.rb with new version + hashes
- Pushes to NodeOps-app/homebrew-createos

Requires HOMEBREW_TAP_TOKEN secret (PAT with repo scope for the tap repo).
Runs after binaries are uploaded, so SHA256 files are always available.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@BhautikChudasama
Copy link
Copy Markdown
Collaborator

Done.

@BhautikChudasama BhautikChudasama deleted the feat/auto-update-homebrew branch April 1, 2026 08:53
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