Skip to content

2026.10.4

Choose a tag to compare

View all tags
@mergify-ci-bot mergify-ci-bot released this 08 Oct 15:45
· 2 commits to main since this release
Immutable release. Only release title and notes can be modified.
2026.10.4
fbb83e3
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

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.
Assets 43
Loading