Repository navigation
chore(deps): update dependency Mergifyio/mergify-cli to 2026.11.8 - #28
Merged
Conversation
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
Contributor
Merge Protections🟢 All 6 merge protections satisfied — ready to merge. Show 6 satisfied protections🟢 🤖 Continuous Integration
🟢 👀 Review Requirements
🟢 Enforce conventional commitMake sure that we follow https://www.conventionalcommits.org/en/v1.0.0/
🟢 🔎 Reviews
🟢 📕 PR description
🟢 🚦 Auto-queueWhen all merge protections are satisfied, this pull request will be queued automatically. |
sileht
marked this pull request as ready for review
November 13, 2026 10:16
jd
approved these changes
Nov 13, 2026
Contributor
✅ Merged into
|
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
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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 aGitHub Actions job granted
id-token: writewith noMERGIFY_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@v1users get with it, besides that:mergify ci junit-processand the testclients 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
skippedstate: it refuses the request and the run goeswithout quarantine. The 2026.11.7 notes tell on-premise users to stay
on 2026.11.6; with
setup-cli@v1that now means settingmergify_cli_version: 2026.11.6. Renovate's own bump past 2026.11.6would carry the same change.
mergify auth statusexits 8 when Mergify refuses the key inMERGIFY_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