Meilisearch
A week of walking back v1.52.0 while the sharding work ships on a parallel tag
A side-by-side editorial comparison of Argo CD and Manticore Search — release velocity, themes, recent moves, and the top alternatives to consider.
Argo CD is on RC4 of v3.4 while patching three live minor branches in parallel — disciplined maintenance posture.
Argo CD's recent activity is a textbook mature-OSS release pattern: v3.4.0 advancing through release candidates (RC1 mid-March, RC4 by March 27) while v3.1, v3.2, and v3.3 receive simultaneous patch releases. The 3.3.6, 3.3.5, and 3.3.4 patches are predominantly cherry-pick bug fixes from main — controller diff-detection corrections, cache installation-id fixes. v3.4.0-rc1 introduced real feature work (e.g., a Health field on ApplicationSet status); subsequent RCs are stabilization passes.
Six releases in a week: one new capability, one revert, the rest corrective
Manticore is cutting point releases every day or two, and the last six are maintenance — a snippet-highlighting markup fix, a thread-stack crash case, a per-index optimize_cutoff correction that now also governs KNN, two Buddy version bumps, and a revert of UTF-8 table and field name support that was merged by mistake.
Argo CD's recent activity is a textbook mature-OSS release pattern: v3.4.0 advancing through release candidates (RC1 mid-March, RC4 by March 27) while v3.1, v3.2, and v3.3 receive simultaneous patch releases. The 3.3.6, 3.3.5, and 3.3.4 patches are predominantly cherry-pick bug fixes from main — controller diff-detection corrections, cache installation-id fixes. v3.4.0-rc1 introduced real feature work (e.g., a Health field on ApplicationSet status); subsequent RCs are stabilization passes.
Argo CD is steady-stating as the de-facto Kubernetes GitOps controller with the disciplined release cadence of a CNCF graduated project. Multi-branch maintenance signals strong enterprise install-base support — operators pin to specific minors and won't accept being forced onto a new line. The 3.4.0 RC progression (RC1 → RC4 in two weeks) suggests careful enterprise-quality stabilization rather than feature scope-creep.
v3.4.0 GA likely lands within 2-4 weeks based on the RC cadence and lack of major late-cycle changes visible. Expect the 3.3.x line to keep receiving security and bug backports for several months after 3.4 GA, while 3.1.x continues as the longest-tail patch line.
Manticore is cutting point releases every day or two, and the last six are maintenance — a snippet-highlighting markup fix, a thread-stack crash case, a per-index optimize_cutoff correction that now also governs KNN, two Buddy version bumps, and a revert of UTF-8 table and field name support that was merged by mistake.
Cadence is high but the content is corrective. The only user-facing addition in this window arrives indirectly, as Unix socket support carried in by Buddy 4.4.0. The reverted UTF-8 identifier work is the one feature visible in flight, and the revert note says it landed before it was meant to rather than that it failed.
Expect UTF-8 table and field names to return in a later release once intentional, and the 28.9.x line to keep absorbing KNN and highlighting fixes at this pace.
Other DevOps 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 Argo CD or Manticore Search.
A week of walking back v1.52.0 while the sharding work ships on a parallel tag
Two branches running in parallel: 3.13 LTS on security patches, 3.14 promoting experiments to stable.
The blog has become a teaching channel, with the real releases arriving as Gateway API and deprecation notices.
Vitest 5 reaches RC after a beta line that reworked config, mocking defaults, and the browser runner.
A dependency-bump treadmill interrupted by the first real accessibility push in months.
Jenkins is shrinking its own war file and rebuilding its UI, one weekly release at a time
See all Argo CD alternatives → · See all Manticore Search alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Manticore Search is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. 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. Manticore Search is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other DevOps products to evaluate alongside.
Top Argo CD alternatives in DevOps are ranked by recent ship velocity. Browse the "Argo CD alternatives" section above for the current picks, or visit /alternatives/argocd for the full list with editorial commentary on each.
Top Manticore Search alternatives in DevOps are ranked by recent ship velocity. Browse the "Manticore Search alternatives" section above for the current picks, or visit /alternatives/manticoresearch for the full list with editorial commentary on each.