Skip to content

ci: auto-bump the Homebrew cask on release (disabled by default)#5

Merged
facundofarias merged 1 commit into
mainfrom
ci/auto-bump-cask
Jul 12, 2026
Merged

ci: auto-bump the Homebrew cask on release (disabled by default)#5
facundofarias merged 1 commit into
mainfrom
ci/auto-bump-cask

Conversation

@facundofarias

Copy link
Copy Markdown
Member

Keeps the Homebrew tap self-maintaining: on a published GitHub Release, this workflow computes the new .dmg sha256 and updates version + sha256 in the pixelvault-dev/homebrew-tap cask — so brew install --cask pixelvault-dev/tap/pixelvault always points at the latest build without manual edits.

Gated off by default

Runs only when HOMEBREW_AUTO_BUMP == 'true'; skipped entirely otherwise (no failures). To enable:

  1. Actions → Variables: HOMEBREW_AUTO_BUMP = true
  2. Actions → Secrets: HOMEBREW_TAP_TOKEN = a PAT (fine-grained or classic) with contents:write on pixelvault-dev/homebrew-tap (the default GITHUB_TOKEN can't push to another repo).

Triggers on release: published (which fires when you publish the draft), so the .dmg is final at that point.

🤖 Generated with Claude Code

On a published GitHub Release, compute the new .dmg sha256 and update version +
sha256 in the pixelvault-dev/homebrew-tap cask, so 'brew install --cask' stays
current without manual edits. Gated behind the repo variable HOMEBREW_AUTO_BUMP
(+ a HOMEBREW_TAP_TOKEN PAT with write access to the tap); the job is skipped
until enabled.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@facundofarias
facundofarias merged commit be3da59 into main Jul 12, 2026
2 checks passed
@facundofarias
facundofarias deleted the ci/auto-bump-cask branch July 12, 2026 16:02
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