GravityKit
GravityKit folds every GravityView extension into one Pro plugin.
A side-by-side editorial comparison of Mergify and Payload CMS — release velocity, themes, recent moves, and the top alternatives to consider.
Mergify's merge queue now hunts the breaking PR by rerunning failed tests first
Mergify shipped more than a dozen changes in the last week of October. On the merge queue, failed batches now run the failing tests first in each split, stacked PRs enter the queue together, scope capacities work with Bazel, Pants and Turborepo scopes and patterns, and batch merge commits name the PRs they land. Test Engine gained Minitest, Jest and Mocha plugins and a setup path driven by a coding agent. Jinja2 expressions in configuration stopped being evaluated on October 31.
Payload's v4 beta.9 keeps every past image crop and raises the Node floor again.
Payload has tagged nine v4 betas since October 10. Beta.9 reads saved crops and focal points from the new _transforms store, serves historical upload variants when a version is restored, adds labels and device details to sessions, and exports standalone CSS tokens from the UI package. It also bumps the minimum Node version to 24.22.3, the second Node floor raise in the cycle.
Mergify shipped more than a dozen changes in the last week of October. On the merge queue, failed batches now run the failing tests first in each split, stacked PRs enter the queue together, scope capacities work with Bazel, Pants and Turborepo scopes and patterns, and batch merge commits name the PRs they land. Test Engine gained Minitest, Jest and Mocha plugins and a setup path driven by a coding agent. Jinja2 expressions in configuration stopped being evaluated on October 31.
Mergify is tying its merge queue to test data: Test Engine knows which tests fail, and the queue uses that to bisect faster with less CI. Monorepo build tools and stacked PRs are now first-class queue inputs.
More queue behavior driven by Test Engine results is likely, given that Fail First and the new test plugins shipped the same week.
Payload has tagged nine v4 betas since October 10. Beta.9 reads saved crops and focal points from the new _transforms store, serves historical upload variants when a version is restored, adds labels and device details to sessions, and exports standalone CSS tokens from the UI package. It also bumps the minimum Node version to 24.22.3, the second Node floor raise in the cycle.
Three betas in a row have reworked file uploads around one stored original plus replayable transforms, and two have tightened sign-in and sessions. The v4 cycle is now finishing those two systems rather than adding new surfaces, which is the usual shape of a beta nearing a release candidate.
Expect more betas that close out the transforms and session work, with a release candidate once the fix lists shrink; the entries do not show a date.
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 Payload CMS.
GravityKit folds every GravityView extension into one Pro plugin.
Nautobot 3.3 alpha 2 adds test helpers and a cable location filter after 3.2.9's token-leak fix.
Clair 4.10 RC can read SBOMs to match Java vulnerabilities.
Shuffle tags builds almost daily, but the notes are empty.
KrakenD's community edition is shipping only dependency bumps.
Velociraptor's recent releases are mostly about patching CVEs.
See all Mergify alternatives → · See all Payload CMS alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Mergify and Payload CMS are shipping at a similar cadence (velocity 5.0 vs 5.0, 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Mergify and Payload CMS are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
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.
Top Payload CMS alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Payload CMS alternatives" section above for the current picks, or visit /alternatives/payload for the full list with editorial commentary on each.