Artillery
Half the release notes are a Playwright version bump; the other half is cloud-runner damage control.
A side-by-side editorial comparison of Manticore Search and fish shell — release velocity, themes, recent moves, and the top alternatives to consider.
One real release hides inside a stream of per-commit tags: UUID document IDs arrive.
The feed carries two granularities at once — individual commit tags like a dependency bump or a revert, and a single curated release-notes post for 28.6.6 that gathers the actual user-facing work. That release is where the substance sits: UUID document IDs for real-time tables, including generated or explicit IDs and UUID-based filters, REPLACE, UPDATE, and DELETE, plus an ordered and limited GROUP_CONCAT() that keeps the top N values per group. Everything else in the window is version bumps to the Buddy sidecar and the backup tool, a revert, and compatibility repair.
Four minor versions in five months, and the shell's remaining work is almost all interaction detail.
fish is deep into the 4.x Rust-era grind: 4.4.0 through 4.8.1 land in roughly five months, each carrying 60-234 commits from a steadily widening contributor base with new committers in every release. The changes are overwhelmingly interactive — keybindings, completion pager behavior, prompt handling, color variables. Each minor release is followed within days or weeks by a patch cleaning up its own regressions.
The feed carries two granularities at once — individual commit tags like a dependency bump or a revert, and a single curated release-notes post for 28.6.6 that gathers the actual user-facing work. That release is where the substance sits: UUID document IDs for real-time tables, including generated or explicit IDs and UUID-based filters, REPLACE, UPDATE, and DELETE, plus an ordered and limited GROUP_CONCAT() that keeps the top N values per group. Everything else in the window is version bumps to the Buddy sidecar and the backup tool, a revert, and compatibility repair.
New surface area keeps arriving through the Buddy sidecar rather than the core daemon — the latest bump brings Unix socket support — which makes Buddy the component to watch for capability changes. The second thread is fallout from the authentication work: making USER a syntax token broke MySQL client status commands, and 28.6.6 had to restore USER() parsing. The 28.8.1 revert of UTF-8 table and field names, undone because it was merged by mistake, is a reminder that the tag stream is a working branch and not a curated changelog.
UTF-8 table and field names were pulled as an accidental merge rather than rejected on their merits, so the likeliest next move is that support returning deliberately in a later tagged release. Expect further SQL-compatibility patches in the same vein as the USER() fix as more of the auth surface meets real MySQL clients.
fish is deep into the 4.x Rust-era grind: 4.4.0 through 4.8.1 land in roughly five months, each carrying 60-234 commits from a steadily widening contributor base with new committers in every release. The changes are overwhelmingly interactive — keybindings, completion pager behavior, prompt handling, color variables. Each minor release is followed within days or weeks by a patch cleaning up its own regressions.
Two threads run underneath the interaction polish. One is shedding legacy C-era dependencies: terminfo and ncurses are gone for good, and 4.8.0 moves Rust-side translation off GNU gettext onto Fluent with purpose-built tooling. The other is fitting into a modern terminal environment rather than working around old ones — OSC 133 prompt marking, systemd run0's prompt variables, emoji width defaulting to 2. The project is trading compatibility with terminals nobody runs for fidelity in the ones people actually use.
Expect the gettext-to-Fluent migration to extend from Rust source into fish script messages, since 4.8.0 flags script translations as the remaining holdout, and expect the release-then-patch rhythm to continue given every minor in this window needed one.
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 Manticore Search or fish shell.
Half the release notes are a Playwright version bump; the other half is cloud-runner damage control.
A terminal Git client that ships release candidates roughly once a year.
A major version being built in the open, one breaking change at a time.
Alacritty ships twice a year and spends it on config syntax, Wayland and IME.
Mamba is adding the reproducibility controls conda users have been asking of the solver.
Swagger UI's release stream is dependency bumps and nothing else.
See all Manticore Search alternatives → · See all fish shell 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 2.5), 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 2.5), 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 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.
Top fish shell alternatives in DevOps are ranked by recent ship velocity. Browse the "fish shell alternatives" section above for the current picks, or visit /alternatives/fish-shell for the full list with editorial commentary on each.