gsarantid / cloudbeat

76%

main: 76%

LAST BUILD ON BRANCH remove-mergify-version-bump-auto-merge

branch: remove-mergify-version-bump-auto-merge

CHANGE BRANCH

x

Reset

Sync Branches

• remove-mergify-version-bump-auto-merge
• 9.5
• bump-to-9.5.0
• bump-to-9.6.0
• bump-to-9.9.9
• fix-minor-bump-idempotency
• main

Build # 28863554778

Build Type

Pull #4

github

Committed by cloudsecmachine

Commit Message

ci: remove Mergify auto-merge for version bump PRs

GitHub's native merge queue is enforced on main. Mergify's `merge:`
action performs a direct merge that bypasses the queue, so GitHub
rejects it ("GitHub refused to merge the pull request"). This is the
second time this pattern has bitten:

- #5871 migrated most Mergify rules from `queue:` to `merge:` when
  moving to GitHub's native queue.
- #6678 (b035bd1f) did the same for the version-bump rule after it
  started failing with "Repository rule violations found: Changes must
  be made through the merge queue" — the same error we're seeing now
  on #7225.

The `merge:` action was a workaround that worked only until the
ruleset actually enforced the queue on main. Now that it does,
Mergify shouldn't be attempting the merge at all. GitHub's native
auto-merge (`gh pr merge --auto --squash` or the UI checkbox) and
"Merge when ready" flow already handle queued merges cleanly.

Scope: this PR only removes the `auto-merge version bump PRs` rule.
The `auto-merge Renovate PRs` and mergify-housekeeping rules use the
same `merge:` action pattern and will hit the same failure; they'll
be handled in follow-ups.

Co-authored-by: Cursor <cursoragent@cursor.com>

Pull Request Pull Request #4: [fork smoke test] ci: remove Mergify auto-merge for version bump PRs

Coverage Stats

10202 of 13406 relevant lines covered (76.1%)

15.9 hits per line