Skip to content

chore(deps): update mergifyio/gha-mergify-ci action to v28 - #1920

Merged
mergify[bot] merged 1 commit into
mainfrom
renovate/mergifyio-gha-mergify-ci-28.x
Nov 11, 2026
Merged

mergify[bot] merged 1 commit into
mainfrom
renovate/mergifyio-gha-mergify-ci-28.x

Conversation

@renovate

@renovate renovate Bot commented Nov 11, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change Pending
Mergifyio/gha-mergify-ci action major v27 → v28 v29

Release Notes

Mergifyio/gha-mergify-ci

v28

Compare Source

Scopes now go to Mergify by commit. The action installs mergify-cli 2026.10.8 through Mergifyio/setup-cli v1.4.0, where v24 to v27 installed 2026.7.21.1, and the scopes and scopes-upload actions report the scopes against the pull request's head commit instead of its number. The per-pull-request scopes endpoint is deprecated and will be removed. A Mergify older than 8.18.0 (on-premise) answers 404 on the commit endpoint: the action then falls back to the pull request one, as before.

Before you upgrade

  • On-premise: junit-process reads quarantines from the test states endpoint, which Mergify serves from 8.18.0. On an older Mergify it can't read them, and a quarantined failure fails the run. Upgrade Mergify first, or set mergify_cli_version: 2026.7.21.1 until you do.
  • scopes may select a different set of scopes for the same change, so jobs gated on its scopes output may run differently:
    • a scope glob's * and ? stop at /, as Mergify reads them;
    • a scope with include: [] matches every file not excluded, where it matched nothing;
    • a renamed file counts against the scopes of both its paths;
    • on a merge queue draft, it returns the scopes the merge queue batched, read from its git note, instead of diffing the draft against its base.

Also in the CLI upgrade

  • scopes and scopes-git-refs read the merge queue's git note on push builds of a queue branch too, and no longer trust a merge queue title on a pull request from a fork.
  • The base input works on a shallow clone.
  • junit-process checks the results against Mergify's schema before uploading them, and refuses an upload Mergify would drop, such as one missing its branch, commit or pipeline name. It no longer stops when it can't tell which branch the run tests: it uploads with quarantine off and says so.

What's Changed

  • ci: add the Approved-by trailer to squash merges by @​jd in #​347
  • feat(scopes): report scopes on the pull request's head commit by @​sileht in #​364
  • ci: release the action when its setup-cli pin changes by @​sileht in #​366

Full Changelog: Mergifyio/gha-mergify-ci@v27...v28


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@mergify
mergify Bot deployed to Mergify Merge Protections November 11, 2026 17:51 Active
@mergify

mergify Bot commented Nov 11, 2026

Copy link
Copy Markdown
Contributor

Merge Protections

🟢 All 6 merge protections satisfied — ready to merge.

Show 6 satisfied protections

🟢 🤖 Continuous Integration

  • all of:
    • check-success=ci-gate

🟢 👀 Review Requirements

  • any of:
    • author = renovate[bot]
    • #approved-reviews-by>=1
    • author = dependabot[bot]
    • author = mergify-ci-bot

🟢 Enforce conventional commit

Make sure that we follow https://www.conventionalcommits.org/en/v1.0.0/

  • title ~= ^(fix|feat|internal|docs|style|refactor|perf|test|build|ci|chore|revert|ui)(?:\(.+\))?!?:

🟢 🔎 Reviews

  • #changes-requested-reviews-by = 0
  • #review-requested = 0
  • #review-threads-unresolved = 0

🟢 📕 PR description

  • body ~= (?ms:.{48,})

🟢 🚦 Auto-queue

When all merge protections are satisfied, this pull request will be queued automatically.

@mergify

mergify Bot commented Nov 11, 2026

Copy link
Copy Markdown
Contributor

🟠 Waiting for a batch

So far

  • ✅ Entered the queue Wed 11 Nov, 17:51 · rule dependencies · triggered by merge protections
  • 🟠 Waiting for a batch · 1 of 7 pull requests · proceeds at 17:56

Times in UTC · dashboard · how the merge queue works

@mergify

mergify Bot commented Nov 11, 2026 •

Copy link
Copy Markdown
Contributor

✅ Merged into main as 6c77fd6 at 17:58 UTC

6 min in the queue, with no time running CI.

So far

  • ✅ Entered the queue Wed 11 Nov, 17:51 · rule dependencies · triggered by merge protections
  • ✅ Checks skipped · PR is already up-to-date
  • ✅ Merged 17:58 · 6c77fd6 · fast-forward
8 merge conditions met
  • github-review-approved · required by GitHub branch protection and GitHub repository ruleset rule Require pull request for default branch
  • title ~= ^(fix|feat|internal|docs|style|refactor|perf|test|build|ci|chore|revert|ui)(?:\(.+\))?!?: · required by Merge Protections rule Enforce conventional commit
  • any of · required by Merge Protections rule 👀 Review Requirements:
    • author = renovate[bot]
    • #approved-reviews-by>=1
    • author = dependabot[bot]
    • author = mergify-ci-bot
  • body ~= (?ms:.{48,}) · required by Merge Protections rule 📕 PR description
  • #changes-requested-reviews-by = 0 · required by Merge Protections rule 🔎 Reviews
  • #review-requested = 0 · required by Merge Protections rule 🔎 Reviews
  • #review-threads-unresolved = 0 · required by Merge Protections rule 🔎 Reviews
  • check-success=ci-gate · required by Merge Protections rule 🤖 Continuous Integration

Times in UTC · dashboard · how the merge queue works

@mergify mergify Bot added the queued label Nov 11, 2026
@mergify
mergify Bot merged commit 6c77fd6 into main Nov 11, 2026
5 checks passed
@mergify mergify Bot removed the queued label Nov 11, 2026
@mergify
mergify Bot deleted the renovate/mergifyio-gha-mergify-ci-28.x branch November 11, 2026 17:58

This branch was successfully deployed

1 active deployment
Mergify Merge Protections — 6c77fd67 Deployed Nov 11, 2026 by mergify[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

0 participants