From c800f6b2b6042c54f23fff272f02faa6abe32dca Mon Sep 17 00:00:00 2001 From: Mehdi ABAAKOUK Date: Fri, 13 Nov 2026 10:38:55 +0100 Subject: [PATCH] chore(deps): update dependency Mergifyio/mergify-cli to 2026.11.8 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 (https://github.com/Mergifyio/gha-mergify-ci/pull/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 Change-Id: I04f9678d7499f94390bc9855a66e0b6f57eca45e --- .github/workflows/ci.yaml | 4 ++-- README.md | 2 +- action.yml | 2 +- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/.github/workflows/ci.yaml b/.github/workflows/ci.yaml index 3cdaa53..dc8fbff 100644 --- a/.github/workflows/ci.yaml +++ b/.github/workflows/ci.yaml @@ -85,7 +85,7 @@ jobs: id: pinned uses: ./ with: - mergify_cli_version: 2026.11.5 + mergify_cli_version: 2026.11.8 - name: Assert pinned install env: @@ -95,7 +95,7 @@ jobs: # the input) so the assertion checks against a fixed expectation. The # name is mergify-specific so the Renovate customManager that bumps it # cannot collide with any other digit-led env added here later. - EXPECTED_MERGIFY_CLI_VERSION: 2026.11.5 + EXPECTED_MERGIFY_CLI_VERSION: 2026.11.8 run: | # Compare against the expected literal requested version (not the # action's own readback), so a regression that installs the wrong diff --git a/README.md b/README.md index 5fc28ad..9f81fd0 100644 --- a/README.md +++ b/README.md @@ -43,7 +43,7 @@ Pin a specific `mergify-cli` version, or install the latest one: | Input | Type | Required | Default | Description | | --- | --- | --- | --- | --- | -| `mergify_cli_version` | string | false | `2026.11.5` | Version of mergify-cli to install. Use `latest` to install the latest released version without pinning. | +| `mergify_cli_version` | string | false | `2026.11.8` | Version of mergify-cli to install. Use `latest` to install the latest released version without pinning. | diff --git a/action.yml b/action.yml index 198e627..664b519 100644 --- a/action.yml +++ b/action.yml @@ -10,7 +10,7 @@ inputs: Version of mergify-cli to install. Use `latest` to install the latest released version without pinning. # renovate: datasource=github-releases depName=Mergifyio/mergify-cli versioning=pep440 - default: 2026.11.5 + default: 2026.11.8 outputs: mergify_cli_version: description: |