authentik
The first patch on 2026.8 is twenty-odd fixes and no new surface.
A side-by-side editorial comparison of Mergify and ToolJet — release velocity, themes, recent moves, and the top alternatives to consider.
Mergify's queue learned to merge stacked pull requests, then spent August tightening the edges.
Mergify automates merge queues for GitHub, and August was a mix of one real capability and a batch of contract cleanup. The queue can now merge GitHub-native stacked pull requests in order, speculative-check budgets apply per lane across dynamic scope sets, and conditions can match on whether a pull request came from a fork. Alongside that, the badge API was removed, pagination stopped advertising first and last links, and author-run commands were restricted to fork pull requests by default.
ToolJet is paying the migration bill for the Git branching it just shipped.
ToolJet runs two parallel release trains: an LTS line taking near-daily patches and a beta line where features land as large rollups. The beta line's headline release was Git sync phase 2, which put branching, unsynced-resource tracking, GitLab support and folder-level permissions into the product in one piece. The three tags since then are all migration and database-connection repair on that same change, including one where the shared migration transaction's locks made fresh installs and upgrades time out. On the LTS side the recent additions are narrower: personal access tokens and a startup fix for blocked RDS certificate downloads.
Mergify automates merge queues for GitHub, and August was a mix of one real capability and a batch of contract cleanup. The queue can now merge GitHub-native stacked pull requests in order, speculative-check budgets apply per lane across dynamic scope sets, and conditions can match on whether a pull request came from a fork. Alongside that, the badge API was removed, pagination stopped advertising first and last links, and author-run commands were restricted to fork pull requests by default.
Two threads. The queue is absorbing workflows that used to sit outside it - stacked pull requests, flaky-test detection and rerunning within a CI budget - which pushes Mergify from a merge gate toward owning the whole pre-merge pipeline. The other thread is a deliberate narrowing of surface: deprecated endpoints removed, the github_actions action marked for removal in March 2027, default command permissions tightened around forks. That is a product trimming what it maintains so the queue can take on more.
Expect more of the pre-merge pipeline to move inside the queue on the flaky-test pattern, and further deprecations of automation that overlaps with what GitHub Actions now does natively.
ToolJet runs two parallel release trains: an LTS line taking near-daily patches and a beta line where features land as large rollups. The beta line's headline release was Git sync phase 2, which put branching, unsynced-resource tracking, GitLab support and folder-level permissions into the product in one piece. The three tags since then are all migration and database-connection repair on that same change, including one where the shared migration transaction's locks made fresh installs and upgrades time out. On the LTS side the recent additions are narrower: personal access tokens and a startup fix for blocked RDS certificate downloads.
Two threads run through this feed. The first is enterprise governance — branching, permissions, restrict-query-run, personal access tokens — which lands in beta and then crosses to LTS. The second is per-connector AI query generation, added to data sources individually rather than as one assistant. Right now the governance thread dominates and is in its consolidation phase: a data-model change of this size is followed by weeks of migration fixes before the LTS crossing is safe.
The near-term releases should stay corrective until the migration path is stable, with the Git sync phase 2 work crossing into the LTS line once the fresh-install and upgrade failures stop recurring.
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 ToolJet.
The first patch on 2026.8 is twenty-odd fixes and no new surface.
Alert rate limits stop being per-source and start being per-tenant, by query.
The essay series keeps running ahead of the products it describes.
Both lines patch on the same day, and the reverted JSONata upgrade finally sticks.
The 3.x line finally ships function: authenticated secret writes and render patches.
Folder-level RBAC lands, and approvals finally get a webhook to talk to.
See all Mergify alternatives → · See all ToolJet 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 ToolJet 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Mergify and ToolJet 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.
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 ToolJet alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "ToolJet alternatives" section above for the current picks, or visit /alternatives/tooljet for the full list with editorial commentary on each.