Skip to content

fix(ci): tap formula update via PR + auto-merge (branch protection on tap main) - #499

Open
Data-Wise wants to merge 1 commit into
devfrom
feature/tap-pr-flow
Open

fix(ci): tap formula update via PR + auto-merge (branch protection on tap main)#499
Data-Wise wants to merge 1 commit into
devfrom
feature/tap-pr-flow

Conversation

@Data-Wise

Copy link
Copy Markdown
Owner

Summary

Data-Wise/homebrew-tap enabled branch protection on main (PR-only, 2 required status checks), so this repo's release workflow's direct push to tap main now fails with GH006 (first seen on atlas v0.14.0, 2026-07-19).

The tap-push step now: commits on a per-version bot/ branch, opens a tap PR via gh (idempotent on re-runs), and enables auto-merge (squash) so it lands once the tap's required checks pass, with an immediate-merge fallback. Tap repo now has allow_auto_merge + delete_branch_on_merge enabled.

Same fix applied ecosystem-wide: atlas#101, homebrew-tap#168 (reusable workflow, repairs the 6 auto_merge: true callers), craft, flow-cli, folio, scribe.

Test plan

  • actionlint: clean for the changed step (pre-existing infos in untouched steps are baseline)
  • PR-path viability verified live by tap PR chore: release v4.8.1 #167 (same flow done manually: both required checks passed, merged)
  • Full E2E on the next release run

🤖 Generated with Claude Code

…ted main

Data-Wise/homebrew-tap enabled branch protection on main (PR-only + 2
required status checks), so the release workflow's direct push now
fails with GH006. Push a bot/flow-cli-<version> branch, open a PR via gh,
and enable auto-merge so it lands when the tap's required checks pass.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Data-Wise added a commit to Data-Wise/homebrew-tap that referenced this pull request Aug 24, 2026
url + sha256 for the v7.17.0 tag.

Done by hand because the automated path is broken: flow-cli's
homebrew-release workflow pushes the formula directly to this repo's main,
which is protected (PR required, 2 status checks), so it fails on every
release with 'protected branch hook declined'. Data-Wise/flow-cli#499 has
carried the fix since 2026-07-19 and is still open.

flow-cli is marked "generated": false in generator/manifest.json, so
hand-editing Formula/flow-cli.rb is the correct path here and does not
trip the regen drift check.

sha256 verified against the published tarball.

Co-authored-by: Test User <test@example.com>
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