[renovate]

This PR contains the following updates:

Package	Update	Change	Pending
Mergifyio/mergify-cli	minor	2026.7.21.1 → 2026.10.8	2026.10.9

---

Release Notes

Mergifyio/mergify-cli

v2026.10.8

Compare Source

minitest-mergify is out: Minitest suites, Rails' included, report to Test Engine without a JUnit file and get the quarantine, flaky detection and Fail First. rspec-mergify now names each example by its file, groups and description instead of its position, and Fail First no longer needs a variable on each job. Read the first section before you upgrade.

Before you upgrade

• rspec-mergify names each example <file> > <groups> > <description>, where it used RSpec's id (./spec/models/user_spec.rb[1:2]), which numbers an example by its place: adding an example renamed every one after it, and handed its quarantine entry and its history to its neighbour. Mergify's lists keep matching after the upgrade: an example quarantined, known flaky or known unhealthy under its id is still treated that way, and the upgrade's pull request takes no example for a new one. A repository moving from a JUnit upload keeps its entries too, under the names that upload gave, except that flaky detection takes an example without a description for a new one on the pull request that switches. Two things do change. Each example's history on the dashboard starts over under its new name. And an entry made under an id still follows that place rather than the example, so quarantine those examples again under their new names.
• rspec-mergify now runs on mergify-ci-core, a new gem that holds the part compiled for each platform. Bundler installs it with rspec-mergify, at the same version, precompiled for Linux (glibc and musl), macOS and Windows. A gem mirror that serves an allowlist needs it too.
• Fail First is on by default. Every merge-queue batch build that can be a bisection step asks Mergify for the tests that failed in the batch it was split from, without MERGIFY_TEST_SELECTION_ENABLE=true on the job. MERGIFY_FAIL_FIRST_ENABLE=false turns it off for a job. MERGIFY_TEST_SELECTION_ENABLE is still read while the new variable is unset, and the report names it deprecated.
• A test quarantined on the dashboard for one pipeline or one job is now quarantined there only. Every reporter used to absorb its failure in every job of the branch, the jobs meant to keep failing on it included.

Minitest

• minitest-mergify is a Minitest plugin, for Minitest 5.19 and later on Ruby 3.1 and later, and Minitest 6 on Ruby 3.2 and later. Add it to your Gemfile, and require it where your suite sets Minitest up, before its tests are defined, such as in test/test_helper.rb:

  require 'minitest/mergify'

• It reports runs in one process, in Minitest's threads (parallelize_me!) and in Rails' parallel workers (parallelize), and keeps the reporters you already use, minitest-reporters included. A quarantined failure doesn't fail the run, and reads as a skip in Minitest's summary. New tests are rerun on a pull request to catch a flaky one before it merges, and a merge queue bisection step runs its batch's failures first.

• A test in a class is named as Minitest names it, UserTest#test_valid; one in a describe block by its file, its describes and its text. A test quarantined under the name a JUnit upload gave it (UserTest.test_valid, from minitest-junit or minitest-reporters) stays quarantined.

Test clients

• Fail First asks only in a merge-queue batch build, the only build that can be a bisection step, and every other build asks nothing. A run Mergify has nothing to say about prints no Fail First block.

mergify CLI

• mergify tests runs lists the test runs Mergify received for a commit, one line per job name they arrived under: how many runs and re-runs, how many arrived whole, the plugin or report that sent them and its version, and their test counts. A results upload that fails leaves its job green, so this is where a missing or misnamed job shows. It takes the commit under test by default, or --sha, --pr or --branch, and --json prints the API's answer.
• A new agent skill, mergify-test-engine-setup, sets Test Engine up in a repository: it finds the frameworks and CI jobs, installs the plugin or wires a JUnit upload, opens the pull request, then checks that pull request's runs before reporting. Load it with npx skills use Mergifyio/mergify-cli --skill mergify-test-engine-setup.

v2026.10.7

Compare Source

@mergifyio/jest and @mergifyio/mocha are out, so Jest and Mocha get what the Vitest and Playwright reporters already do: traces uploaded as the tests run, with no JUnit file to write and upload afterwards, the quarantine, flaky detection's reruns and Fail First. This release also fixes @mergifyio/vitest and @mergifyio/playwright 2026.10.6 failing a green run when flaky detection planned more than a minute of reruns.

Before you upgrade

• The JavaScript reporters need Node.js 22 or later, and now check it. On an older Node.js they send nothing and say so in their report: "Mergify needs Node.js 22 or later (this is 20.14.0), so nothing will be sent." A run on Node.js 20 installed with npm, which could still upload when the native binding happened to load, sends nothing now. Your tests pass or fail as they did.

Jest and Mocha

• @mergifyio/jest is a Jest reporter, for Jest 29 or later. Wrap your config with withMergify, in a jest.config.js (or .ts, .mjs, .cjs):

  const { withMergify } = require('@mergifyio/jest');
  
  module.exports = withMergify({
    testEnvironment: 'node',
  });

• @mergifyio/mocha is a Mocha plugin, for Mocha 10 or later. Have Mocha require it, with require: ['@mergifyio/mocha'] in your .mocharc or mocha --require @mergifyio/mocha. It takes up no reporter, so spec, mocha-junit-reporter or mochawesome stay as they are, and it covers --parallel runs.

• Both keep a quarantined test's failure from failing the run, rerun new tests on a pull request to catch a flaky one before it merges, and run a merge queue bisection step's failures first. Set MERGIFY_TOKEN in CI. Each package's README lists the setups it supports.

Test clients

• @mergifyio/vitest and @mergifyio/playwright: when flaky detection planned more than a minute of reruns, the run failed after all its tests had passed, with RangeError: The value of "timeout" is out of range. The reruns now start.
• @mergifyio/vitest: a project whose Vitest config loads as CommonJS (a vitest.config.ts in a package that is not "type": "module") no longer fails every test file with "Vitest cannot be imported in a CommonJS module using require()".
• Mergify no longer reduces a merge queue retry to the tests that failed. A reporter that still receives such an answer from an older Mergify, or one asking it to run nothing or to stop, now runs the whole suite and says so in its report. Fail First is unchanged.

v2026.10.6

Compare Source

pytest-mergify, rspec-mergify, @mergifyio/vitest and @mergifyio/playwright now make every decision (quarantine, flaky detection's reruns, Test Selection, the run's verdict) in one shared core, so the four reporters behave alike and end the run with the same report. Some runs that passed with 2026.10.5 can fail with this release: read the first section before you upgrade.

Before you upgrade

• pytest-mergify needs Python 3.10 or later. Python 3.8 and 3.9 are both end of life, and pip on them keeps installing 2026.10.5.
• A test your framework retried (Playwright's retries, Vitest's retry, rspec-retry, pytest-rerunfailures) now reaches Mergify with every attempt, where it used to reach it as its last one. On a pull request, a new test that the framework's retry rescued is flaky, and fails the run as one that flaky detection's reruns caught does.
• @mergifyio/playwright: on a pull request, a new test that fails one of flaky detection's reruns now fails the run, as it already did with the other three reporters. It used to be reported as flaky while the run stayed green.
• @mergifyio/playwright: on push and scheduled runs, the tests Mergify lists as unhealthy are no longer treated as quarantined. Their first attempt decides the run, as in the other reporters, and only the tests you quarantined are absorbed.
• @mergifyio/vitest names each test with its file, <file> > <suites> > <title>, as the other reporters do. Two tests with the same suites and title in two files used to be one test to Mergify. A test quarantined under its former name stays quarantined, and flaky detection still recognizes it, but each test's history on the dashboard starts over under its new name.

Test clients

• A quarantined test that fails is now uploaded as failed, with its error, and still doesn't fail the run. pytest-mergify and rspec-mergify used to upload it as skipped, and @mergifyio/vitest as passed, so a quarantined test that kept failing could show as recovered, and Vitest's could even be unquarantined by unquarantine_when_healthy.
• Every reporter ends the run with one Mergify CI report, the same blocks in the same order in all four: deprecated variables, flaky detection, test retry, the quarantine, Test Selection, the verdict, then the upload and its run ID.
• Fail First, for merge queue bisection: when Mergify hands a bisection step the tests that failed in the run it was split from, every reporter runs them first and stops the run as soon as one fails again, so the queue can split again without waiting for the rest of the suite. When they pass, the whole suite runs as usual.
• Failures reach Mergify as plain text, without terminal colour codes, from every reporter and from mergify ci junit-process. @mergifyio/playwright sends a failure's type and message as the test raised them (TypeError, then its message), where it sent Error and the whole line.
• pytest-mergify no longer keeps pytest-rerunfailures from retrying: --reruns, --only-rerun and the flaky marker work as they do without pytest-mergify. A test that failed once used to fail the job. When the plugin's attempts all fail, Mergify's test retry still gets its turn.
• pytest-mergify under pytest-xdist reports one run: the workers join the controller's session instead of each detecting CI, starting a run and uploading a trace of their own. When it withholds the run's verdict (a worker crashed, the workers collected different tests), it now says why, as the other reporters do.
• pytest-mergify times each test on its own clock, so a test that freezes time with freezegun is rerun by flaky detection and retried like any other.
• pytest-mergify: on an output that can't encode emoji, such as a Windows runner's piped stdout in cp1252, the report is written in plain ASCII instead of one long escaped line.
• @mergifyio/vitest: Vitest 3 runs upload their traces again. A missing file path on Vitest 3 had made every upload fail silently.
• @mergifyio/vitest: flaky detection reruns its tests once the run is over, on one budget for the whole run, where it used to plan a budget per test file before the tests ran. A run with no Vitest configuration file can't be rerun and says so. Browser projects, the Cloudflare Workers pool and type checks are not rerun.
• @mergifyio/playwright: flaky detection's reruns no longer overwrite your JUnit and HTML reports, your test-results directory or the record --last-failed reads, and they run in the directory the run started in, so a new test that reads a relative path is no longer found flaky.
• @mergifyio/playwright no longer writes under node_modules/.cache. Where node_modules is read-only (Nix, a Bazel sandbox, a read-only image layer), its workers could miss the quarantine and fail on a quarantined test.
• @mergifyio/playwright: a run whose tests passed but whose global teardown threw no longer sends Mergify a verdict that reads as green, so a merge queue retry runs the whole suite instead of nothing.
• The settings every reporter has now take one name on all four: MERGIFY_CI_ENABLE turns a reporter on outside CI, and MERGIFY_CI_DEBUG makes it print instead of upload. PLAYWRIGHT_MERGIFY_INCLUDE_PROJECT_IN_TEST_NAME becomes MERGIFY_PLAYWRIGHT_INCLUDE_PROJECT_IN_TEST_NAME. The old names (PYTEST_MERGIFY_ENABLE, RSPEC_MERGIFY_DEBUG and the like) still work, and the report names the replacement of any you set. RSPEC_MERGIFY_DEBUG is now read as a boolean like the others, so RSPEC_MERGIFY_DEBUG=false no longer turns debug mode on.
• The release carries environment-variables.json, the list of every variable the reporters and the CLI read.

mergify CLI

• mergify ci junit-process checks the test results against the schema Mergify publishes before uploading them, and refuses an upload Mergify would drop, such as one missing its branch, commit or pipeline name. The report lists each problem, and GitHub Actions gets an error annotation. When the schema can't be fetched within 10 seconds, the upload goes ahead unchecked.
• mergify ci junit-process no longer stops when it can't tell which branch the run tests: it uploads the results, turns quarantine off for that run and says so.
• mergify ci junit-process: the all-green verdict no longer says "no quarantine needed" under a list of quarantined tests.
• mergify ci git-refs and mergify ci scopes read the merge queue's git note on push builds of a queue branch too (a GitHub push event, a Buildkite branch build), so they diff against the batch's base and return the scopes the merge queue decided. A push that creates a branch is diffed against the default branch, since its before names no commit.
• mergify ci scopes: a scope with include: [] matches every file not excluded, as Mergify reads it. It used to match nothing. Scope globs are now matched by the same code Mergify uses.
• The CLI reads YAML the way Mergify does: << merge keys are expanded, and yes, no, on and off are booleans.
• mergify queue status shows the batches being formed, in a Forming section above the waiting list.
• mergify queue show: an unmet condition group is summarized with its own logic (all of joined with and, any of with or, a not kept), and the members that decide it come first. Every group used to read as or.
• mergify stack push:
  • a pull request that moves onto another base (a change inserted below it, a reorder, a dropped commit) moves before its head is pushed, so the CI run the push starts sees its real base rather than the trunk;
  • the branches land even when the remote refuses the stack notes, and the push finishes when a dropped commit's branch can't be deleted, with a warning naming the pull request to close;
  • stack push, list, sync and checkout work behind a proxy that refuses a path ending in /, such as Claude Code on the web's.
• mergify self-update no longer takes a pre-release back to the last final. --force still does.

v2026.10.5

Compare Source

mergify CLI

• mergify ci scopes now accepts a glob with a [ inside a character class (e.g. [a[:alpha:]]/b), reading it as a literal character, the way Mergify does. It used to reject it as a configuration error.

Test clients

• @mergifyio/playwright: when a CI job is cancelled, a test that never started is now reported as skipped instead of failed, so cancelled runs no longer mark tests as broken or flaky.

v2026.10.4

Compare Source

New license. From this release on, the Mergify CLI, its agent skills and the test clients (pytest-mergify, rspec-mergify, @mergifyio/*) are proprietary. Each package ships a LICENSE that lets you install and run it, unmodified, with the Mergify service, including as a dependency of your project and in internal mirrors, container images and CI. It also ships a THIRD_PARTY_LICENSES file with the notices of the open-source components it bundles. Earlier versions keep the license they were released under, and nothing changes in how you install or update.

mergify CLI

• mergify tests quarantines list, get and remove now follow pagination, so they see every quarantined test, not only the first page.
• mergify tests show no longer fails on a test that has no last conclusion recorded.
• mergify ci junit-process now records the test framework (--test-framework) and each test case's function name.
• The CLI works on images without a CA store (distroless, busybox, Alpine without ca-certificates): it trusts its bundled root certificates alongside the system ones.
• Requests carry the CLI's release version in their User-Agent.
• Retries follow one policy for every command: timeouts (408), throttling (429, honouring Retry-After) and rate-limited 403s are retried, within a bounded time.
• Pushing a stack of a single change no longer prints not registered on GitHub.
• Messages and the plugin manifests say Test Engine instead of Test Insights. The annotation title, command names, flags and environment variables are unchanged.

Test clients

• rspec-mergify: pending and skipped examples (skip, xit, pending, and quarantined failures) are now uploaded as skipped. They were dropped before.
• A test session over 20 MiB is split into parts that Mergify puts back together, instead of halves that each looked like a complete run.
• A test whose name is over 64 KiB is left out of the upload and reported as lost, and an upload is bounded at one minute.
• An upload carries on past a part that fails, and retries throttling (429).

CLI and test clients

• CI detection is shared between the CLI and the test clients, so they describe a job the same way:
  • Jenkins change-request builds report their target branch, so quarantine and flaky detection use the pull request's base branch;
  • a CI variable set to an empty string is treated as unset;
  • a detached checkout no longer reports HEAD as its branch.

v2026.10.3

Compare Source

The mergify CLI now ships with the test clients. From this release on, mergify-cli (PyPI, the binaries below, install.sh, mergify self-update, Homebrew) and the test-client packages (pytest-mergify, rspec-mergify, @mergifyio/*) are released together, under one YYYY.M.N version. Nothing changes in how you install or update either.

The CLI goes from 2026.10.1 to 2026.10.3: 2026.10.2 was a test-clients-only release.

mergify CLI (since 2026.10.1)

• mergify auth login --device-name overrides the hostname the login is registered under.
• mergify ci scopes:
  • scope globs are now compiled exactly as the Mergify engine compiles them;
  • --base origin/main works on a shallow clone;
  • it no longer panics on a non-ASCII base or head ref;
  • paths that aren't valid UTF-8 are matched under the name GitHub reports for them.
• A merge queue title coming from a fork is no longer trusted.
• The stack documentation no longer calls GitHub-native stacks experimental.
• Built with Rust 1.99.

Test clients (since 2026.10.2)

• No functional change.
• The native extensions are built with napi-rs 3.14.2 (@mergifyio/ci-native) and updated patch releases of their TLS and error-handling dependencies (rustls 0.23.45).

v2026.10.2

Compare Source

No functional change in any client: this release updates package metadata and dependencies.

All clients

• Package pages now link to each client's documentation, and to Mergifyio/mergify-cli issues for bug reports:
  • pytest-mergify: https://docs.mergify.com/test-insights/test-frameworks/pytest/
  • rspec-mergify: https://docs.mergify.com/test-insights/test-frameworks/rspec/
  • @​mergifyio/vitest: https://docs.mergify.com/test-insights/test-frameworks/vitest/
  • @​mergifyio/playwright: https://docs.mergify.com/test-insights/test-frameworks/playwright/
• The npm packages and the gem no longer link to a source repository.

@​mergifyio/* (npm)

• The native binding is built with napi-rs 3.14.1.
• From this release on, the npm packages are published without npm provenance statements. They are still published by our CI through npm Trusted Publishing.

v2026.10.1

Compare Source

What's Changed

• feat(plugin): mark the Codex plugin as requiring a local executor by @​jd in #​1835
• fix(plugin): fit the Codex subtitle in 30 characters by @​jd in #​1836
• chore(deps): bump flate2, quick-xml, jsonschema (minor/patch) by @​jd in #​1834
• refactor(tui): resolve the color env overrides at the CLI entry point by @​sileht in #​1837
• feat(core): read the environment through one funnel, with a hermetic test overlay by @​sileht in #​1838
• refactor(ci): read the CI environment through the funnel by @​sileht in #​1839
• refactor(stack): read the environment through the funnel by @​sileht in #​1840
• refactor(cli): assert the clap env hook is absent without mutating the environment by @​sileht in #​1841
• feat(stack): hand the stack's member list to GitHub's native UI by @​jd in #​1851
• refactor(auth): read the environment through the funnel by @​sileht in #​1842
• chore(lint): make the next process-environment read fail the build by @​sileht in #​1843
• feat(plugin): publish the Codex plugin as 1.1.0 by @​jd in #​1854
• feat(config): find the configuration under the .yaml spelling by @​jd in #​1855
• ci: run the GitHub-hosted Linux jobs on ubuntu-26.04 by @​jd in #​1859
• feat(ci): return the merge queue batch's scopes on a merge queue draft by @​sileht in #​1860
• build(wheels): publish musllinux wheels for x86_64 and aarch64 by @​kozlek in #​1863
• build(wheels): stop publishing the source distribution by @​kozlek in #​1864
• ci(release): switch to YYYY.M.N calver by @​kozlek in #​1868
• fix(stack): discover a stack's pull requests without the Search API by @​jd in #​1862
• feat(ci): Fetch quarantines from the list endpoint in junit-process by @​remyduthu in #​1871

Full Changelog: Mergifyio/mergify-cli@2026.9.16.1...2026.10.1

v2026.9.16.1

Compare Source

What's Changed

• feat(core): use the stored credential, deprecate GITHUB_TOKEN by @​sileht in #​1807
• chore(rust): bump toolchain to 1.98 by @​jd in #​1824
• fix(core): never send a Mergify user token to GitHub by @​sileht in #​1808
• docs(core): give key_for the reason that still holds by @​sileht in #​1823
• feat(cli): open the browser on auth login by @​sileht in #​1827
• feat(cli): name the machine on the approval page by @​sileht in #​1828
• feat(stack): register with GitHub native stacks by default by @​jd in #​1833

Full Changelog: Mergifyio/mergify-cli@2026.9.10.1...2026.9.16.1

v2026.9.10.1

Compare Source

What's Changed

• feat(ci): report scopes against the pull request head by @​sileht in #​1794
• refactor(core): split Mergify and GitHub token resolution by @​sileht in #​1802
• fix(live-tests): move tests show onto the admin token by @​jd in #​1798
• docs(live-tests): drop the mirror claims for deleted Python files by @​jd in #​1799
• test(live): cover the quarantine add/remove round-trip by @​jd in #​1801
• docs(release): add a maintainer skill for cutting a release by @​jd in #​1795
• fix(ci): skip a test whose name is too large and say which one by @​sileht in #​1793
• feat(core): store the Mergify credential in the OS keychain by @​sileht in #​1803
• feat(ci): declare how many uploads make up a test session by @​AlexandreGaubert in #​1816
• feat(core): let a caller read an endpoint's rejection body by @​sileht in #​1804
• feat(auth): the device authorization grant, client side by @​sileht in #​1805
• fix(core): send API requests under the base URL's path prefix by @​jd in #​1819
• feat(cli): mergify auth login, logout and status by @​sileht in #​1806

Full Changelog: Mergifyio/mergify-cli@2026.8.28.1...2026.9.10.1

v2026.8.31.1

Compare Source

What's Changed

• feat(plugin): package the skills as a Codex plugin by @​jd in #​1774
• fix(deps): update h2 to 0.4.17 for RUSTSEC-2026-0258 by @​jd in #​1778
• fix(stack): strip current-format Change-Id suffixes from branch refs by @​jd in #​1775
• feat(stack): drop the Depends-On header once GitHub holds the stack by @​jd in #​1780
• feat(stack): check out a stack by branch or pull request URL by @​jd in #​1776
• fix(ci): reject a checking_base_sha that is not a git object name by @​sileht in #​1785
• refactor(ci): share one $GITHUB_OUTPUT heredoc writer by @​sileht in #​1786
• fix(ci): write git-refs base/head through the heredoc writer by @​sileht in #​1787
• fix(stack): escape the HTML-comment delimiters in the revision marker by @​JulianMaurin in #​1791

Full Changelog: Mergifyio/mergify-cli@2026.8.11.1...2026.8.31.1

v2026.8.28.1

Compare Source

What's Changed

• feat(plugin): package the skills as a Codex plugin by @​jd in #​1774
• fix(deps): update h2 to 0.4.17 for RUSTSEC-2026-0258 by @​jd in #​1778
• fix(stack): strip current-format Change-Id suffixes from branch refs by @​jd in #​1775
• feat(stack): drop the Depends-On header once GitHub holds the stack by @​jd in #​1780
• feat(stack): check out a stack by branch or pull request URL by @​jd in #​1776
• fix(ci): reject a checking_base_sha that is not a git object name by @​sileht in #​1785
• refactor(ci): share one $GITHUB_OUTPUT heredoc writer by @​sileht in #​1786
• fix(ci): write git-refs base/head through the heredoc writer by @​sileht in #​1787
• fix(stack): escape the HTML-comment delimiters in the revision marker by @​JulianMaurin in #​1791

Full Changelog: Mergifyio/mergify-cli@2026.8.11.1...2026.8.28.1

v2026.8.11.1

Compare Source

What's Changed

• fix(tui): gate color on the CLI entry point, not cfg!(test) by @​jd in #​1765
• feat(events): cap the default page at one API page by @​jd in #​1766

Full Changelog: Mergifyio/mergify-cli@2026.8.7.1...2026.8.11.1

v2026.8.7.1

Compare Source

What's Changed

• chore(release): exclude renovate[bot] from generated release notes by @​jd in #​1744
• docs(queue): make the merge-queue skill usable for a dequeued PR by @​jd in #​1746
• fix(stack): read replay diff-tree NUL-delimited so non-ASCII paths survive by @​sileht in #​1751
• feat(queue): tell a dequeued PR apart from a never-queued one in queue show by @​jd in #​1747
• fix(ci): bound scope glob * and ? at / to match the engine by @​sileht in #​1752
• feat(queue): show when a queued PR's checks will time out by @​jd in #​1748
• chore: clean gitignore by @​jd in #​1761
• feat(stack): opt-in emission of GitHub-native stacks by @​jd in #​1762
• feat(events): add a shared activity-log client crate by @​jd in #​1758
• refactor(queue): port queue show's dequeue diagnosis onto mergify-events by @​jd in #​1759
• feat(events): add mergify events, a timeline over the activity log by @​jd in #​1760

Full Changelog: Mergifyio/mergify-cli@2026.7.29.1...2026.8.7.1

v2026.7.29.1

Compare Source

What's Changed

• chore(deps): update cargo minor/patch updates by @​renovate[bot] in #​1736
• chore(deps): update actions/setup-python action to v7 by @​renovate[bot] in #​1738
• chore(deps): update mergifyio/gha-mergify-ci action to v24 by @​renovate[bot] in #​1741
• fix(ci): count a renamed file against both of its scopes by @​sileht in #​1739
• fix(ci): read changed paths NUL-delimited so non-ASCII names match by @​sileht in #​1740

Full Changelog: Mergifyio/mergify-cli@2026.7.21.1...2026.7.29.1

---

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]

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:
  • 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]

✅ Merged into main as 17a1c28 at 09:16 UTC

Merged together with #19, #20, #21. 6 min in the queue, 1 min of it CI.

So far

• ✅ Entered the queue Tue 27 Oct, 09:11 · rule dependencies · triggered by merge protections
• ✅ Passed · draft merge queue: merged #19, #20, #21, #22: chore(deps): update actions/checkout digest to d23441a (+3 more) #24
• ✅ Merged 09:16 · 17a1c28 · fast-forward

Merge conditions: 7 of 7 met

This pull request

	Condition	Required by
✅	title ~= ^(fix|feat|internal|docs|style|refactor|perf|test|build|ci|chore|revert|ui)(?:\(.+\))?!?:	Merge Protections rule Enforce conventional commit
✅	any of: author = renovate[bot], #approved-reviews-by>=1, author = dependabot[bot], author = mergify-ci-bot	Merge Protections rule 👀 Review Requirements
✅	body ~= (?ms:.{48,})	Merge Protections rule 📕 PR description
✅	#changes-requested-reviews-by = 0	Merge Protections rule 🔎 Reviews
✅	#review-requested = 0	Merge Protections rule 🔎 Reviews
✅	#review-threads-unresolved = 0	Merge Protections rule 🔎 Reviews

The batch, tested on draft #24

	Condition	Required by
✅	check-success=all-greens	Merge Protections rule 🤖 Continuous Integration

_{Times in UTC · dashboard · how the merge queue works}