Skip to content

chore(deps): update dependency Mergifyio/mergify-cli to 2026.11.8 - #28

Merged
mergify[bot] merged 1 commit into
mainfrom
devs/sileht/mrgfy-11495-setup-cli-2026-11-8/update-dep-mergifyio-mergify-cli-2026-11-8--04f9678d
Nov 13, 2026
Merged

mergify[bot] merged 1 commit into
mainfrom
devs/sileht/mrgfy-11495-setup-cli-2026-11-8/update-dep-mergifyio-mergify-cli-2026-11-8--04f9678d

Conversation

@sileht

@sileht sileht commented Nov 13, 2026

Copy link
Copy Markdown
Member

Bumps the default mergify-cli from 2026.11.5 to 2026.11.8 in the same
places Renovate updates (action.yml default, the README inputs table,
and the pinned install test in ci.yaml).

2026.11.8 is the first release where mergify ci scopes-send, in a
GitHub Actions job granted id-token: write with no MERGIFY_TOKEN,
warns and exits 0 when Mergify does not exchange the job's ID token,
instead of failing the step. gha-mergify-ci needs that before it can
hand scopes uploads to the CLI's exchange
(Mergifyio/gha-mergify-ci#375), so this skips
the 2 days minimumReleaseAge the renovate.json rule sets for
mergify-cli: 2026.11.8 came out today.

What setup-cli@v1 users get with it, besides that:

  • On-premise: from 2026.11.7, mergify ci junit-process and the test
    clients ask Mergify for the skipped tests along with the quarantined
    ones, and no on-premise Mergify released so far (8.18.0 included)
    serves the skipped state: it refuses the request and the run goes
    without quarantine. The 2026.11.7 notes tell on-premise users to stay
    on 2026.11.6; with setup-cli@v1 that now means setting
    mergify_cli_version: 2026.11.6. Renovate's own bump past 2026.11.6
    would carry the same change.
  • mergify auth status exits 8 when Mergify refuses the key in
    MERGIFY_TOKEN, an expired one included (2026.11.8).

Merging it is a push to main, so the release workflow cuts the next
v1 minor with 2026.11.8 as its default and moves v1 to it.

Related to MRGFY-11495

Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com

Bumps the default mergify-cli from 2026.11.5 to 2026.11.8 in the same
places Renovate updates (action.yml default, the README inputs table,
and the pinned install test in ci.yaml).

2026.11.8 is the first release where `mergify ci scopes-send`, in a
GitHub Actions job granted `id-token: write` with no `MERGIFY_TOKEN`,
warns and exits 0 when Mergify does not exchange the job's ID token,
instead of failing the step. gha-mergify-ci needs that before it can
hand scopes uploads to the CLI's exchange
(Mergifyio/gha-mergify-ci#375), so this skips
the 2 days minimumReleaseAge the renovate.json rule sets for
mergify-cli: 2026.11.8 came out today.

What `setup-cli@v1` users get with it, besides that:

- On-premise: from 2026.11.7, `mergify ci junit-process` and the test
  clients ask Mergify for the skipped tests along with the quarantined
  ones, and no on-premise Mergify released so far (8.18.0 included)
  serves the `skipped` state: it refuses the request and the run goes
  without quarantine. The 2026.11.7 notes tell on-premise users to stay
  on 2026.11.6; with `setup-cli@v1` that now means setting
  `mergify_cli_version: 2026.11.6`. Renovate's own bump past 2026.11.6
  would carry the same change.
- `mergify auth status` exits 8 when Mergify refuses the key in
  `MERGIFY_TOKEN`, an expired one included (2026.11.8).

Merging it is a push to main, so the release workflow cuts the next
v1 minor with 2026.11.8 as its default and moves v1 to it.

Related to MRGFY-11495

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Change-Id: I04f9678d7499f94390bc9855a66e0b6f57eca45e
@mergify
mergify Bot deployed to Mergify Merge Protections November 13, 2026 09:42 Active
@mergify

mergify Bot commented Nov 13, 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=all-greens

🟢 👀 Review Requirements

  • any of:
    • #approved-reviews-by>=1
    • author = dependabot[bot]
    • author = mergify-ci-bot
    • author = renovate[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 requested a review from a team November 13, 2026 09:43
@sileht
sileht marked this pull request as ready for review November 13, 2026 10:16
@mergify
mergify Bot merged commit 4c0a3dd into main Nov 13, 2026
9 checks passed
@mergify

mergify Bot commented Nov 13, 2026 •

Copy link
Copy Markdown
Contributor

✅ Merged into main as 4c0a3dd at 10:48 UTC

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

So far

  • ✅ Entered the queue Fri 13 Nov, 10:47 · rule default · triggered by merge protections
  • ✅ Checks skipped · PR is already up-to-date
  • ✅ Merged 10:48 · 4c0a3dd · squash
7 merge conditions met
  • 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:
    • #approved-reviews-by>=1
    • author = dependabot[bot]
    • author = mergify-ci-bot
    • author = renovate[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=all-greens · required by Merge Protections rule 🤖 Continuous Integration

Times in UTC · dashboard · how the merge queue works

@mergify
mergify Bot deleted the devs/sileht/mrgfy-11495-setup-cli-2026-11-8/update-dep-mergifyio-mergify-cli-2026-11-8--04f9678d branch November 13, 2026 10:48
@mergify mergify Bot added queued and removed queued labels Nov 13, 2026

This branch was successfully deployed

1 active deployment
Mergify Merge Protections — c800f6b2 Deployed Nov 13, 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.

2 participants