Sonarr
Sonarr's 5.0 builds move from UI rework to safer restores and keyboard-friendly selects.
Comparison · Infra & APIs
Mergify vs Skipper
A side-by-side editorial comparison of Mergify and Skipper — release velocity, themes, recent moves, and the top alternatives to consider.
Mergify vs Skipper: at a glance
What is Mergify?
Mergify tightens merge queue controls with deployment pinning, per-lane capacity, and GitHub-native stacked PR support.
Mergify is shipping targeted capability additions to its merge queue around two themes: finer-grained deployment and scope controls, and tighter security around author permissions. Deployment conditions can now be pinned to specific apps, per-lane check capacity applies to dynamic scopes without enumerating scope names, and the stacked PR merge integration brings GitHub's native stacked PR feature into the merge queue. On the security side, head branch writes are now restricted to the originating repository and forks, preventing cross-repository writes.
What is Skipper?
Skipper adds raw-path routing predicates after a week of security and maintenance tags.
Skipper tags a release for nearly every merge. v0.28.39 adds four path predicates, prefix and regexp matching on either the normalized or raw request path, so routes can tell an encoded %2f from a slash, with benchmarks showing zero allocations. Just before it, v0.28.37 fixed security advisory GHSA-9hwf-c47m-j4pg in the cache() filter and v0.28.38 removed a direct syscall dependency. The rest of the week was test-certificate consolidation and dependency builds.
Mergify vs Skipper: editorial side-by-side
Mergify
6.3INFRA · APIS
Mergify tightens merge queue controls with deployment pinning, per-lane capacity, and GitHub-native stacked PR support.
◆ Current state
Mergify is shipping targeted capability additions to its merge queue around two themes: finer-grained deployment and scope controls, and tighter security around author permissions. Deployment conditions can now be pinned to specific apps, per-lane check capacity applies to dynamic scopes without enumerating scope names, and the stacked PR merge integration brings GitHub's native stacked PR feature into the merge queue. On the security side, head branch writes are now restricted to the originating repository and forks, preventing cross-repository writes.
◆ Where it's heading
Mergify is expanding its merge queue from a queue-and-merge tool toward a fully controllable CI/CD gating layer. The deployment condition pinning, per-lane capacity limits, and stacked PR support each address specific enterprise workflow gaps rather than adding breadth. The Datadog metrics retirement (replacing custom metrics with a cleaner `mergify.queue.*` set) and badge API removal signal an API consolidation pass running in parallel with feature additions.
◆ Prediction
Expect continued deepening of the deployment condition model — more condition attributes for filtering merge behavior based on deployment context and app identity. The stacked PR integration suggests GitHub's native stacked PR tooling is gaining enterprise adoption; Mergify may add more explicit stacked PR workflow controls beyond queue membership.
Skipper
6.3INFRA · APIS
Skipper adds raw-path routing predicates after a week of security and maintenance tags.
◆ Current state
Skipper tags a release for nearly every merge. v0.28.39 adds four path predicates, prefix and regexp matching on either the normalized or raw request path, so routes can tell an encoded %2f from a slash, with benchmarks showing zero allocations. Just before it, v0.28.37 fixed security advisory GHSA-9hwf-c47m-j4pg in the cache() filter and v0.28.38 removed a direct syscall dependency. The rest of the week was test-certificate consolidation and dependency builds.
◆ Where it's heading
Skipper keeps taking on edge responsibilities, from caching to identity, while tightening its hot path. Raw-path matching gives operators finer routing control over encoded URLs, a frequent source of proxy bypass bugs, and fits the recent security focus. The certificate refactor still points to TLS work ahead.
◆ Prediction
Expect a TLS-related feature built on the unified certificate setup, plus further cache-filter fixes. Otherwise more Dependabot tags.
Alternatives to Mergify and Skipper
Other Infra & APIs products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either Mergify or Skipper.
Cursor
Cursor puts its cloud agent environments behind an API and lets agents ship interactive canvases.
Railway
Railway is adding guardrails for teams moving off the dashboard and into code and the CLI.
Jackett
Jackett ships daily to keep hundreds of torrent indexers working as sites move and close.
CircleCI
CircleCI now sizes parallelism to the tests Smarter Testing actually selects.
GitHub
GitHub makes open source license compliance a ruleset-enforced GA for Enterprise Cloud.
See all Mergify alternatives → · See all Skipper alternatives →
Recent activity from Mergify and Skipper
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1d agoSkipperPath predicates that match normalized or raw (%2f) request paths
- 2d agoSkipperRefactor removes direct syscall signal dependency
- 2d agoSkipperSecurity fix for cache() filter advisory GHSA-9hwf-c47m-j4pg
- 3d agoSkipperUnifies test certificate setup ahead of new TLS work
- 3d agoSkipperBumps the Amazon Linux base image used for fuzzing
- 3d agoSkipperBumps the OSS-Fuzz Go builder image
- 1mo agoMergifyHead branch updates stay inside your repository and its forks
- 1mo agoMergifyDatadog integration: four merge queue metrics are being retired
- 1mo agoMergifyPin a deployment condition to the app that deployed
- 1mo agoMergifyRepository badge API removed
- 1mo agoMergifyPer-lane check capacity for dynamic scopes
- 1mo agoMergifyClearer reason when the merge queue can't create the draft pull request
Frequently asked questions
What is the difference between Mergify and Skipper?
They serve adjacent needs but don't currently overlap on shipped themes. Mergify and Skipper are shipping at a similar cadence (velocity 6.3 vs 6.3, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is Mergify better than Skipper?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Mergify and Skipper are shipping at a similar cadence (velocity 6.3 vs 6.3, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
What are the best alternatives to Mergify?
Top Mergify alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Mergify alternatives" section above for the current picks, or visit /alternatives/mergify for the full list with editorial commentary on each.
What are the best alternatives to Skipper?
Top Skipper alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Skipper alternatives" section above for the current picks, or visit /alternatives/skipper for the full list with editorial commentary on each.