Lima
Lima 2.3 nears release, with a Windows path that drops QEMU and a new TUI
A side-by-side editorial comparison of Gitness and Talos Linux — release velocity, themes, recent moves, and the top alternatives to consider.
Harness Open Source last shipped in August 2025, on this feed at least
The feed holds two releases of Harness Open Source, tracked here as Gitness. v3.2.0 in May 2025 added Git LFS, default reviewers through branch rules and a Revert PR option; v3.3.0 that August added tag rules, a PR dashboard upgrade with favourite repositories, and a fix for a Git LFS upload path flaw. Nothing newer appears here.
Talos 1.15's alpha keeps moving: a silent containerd config trap and declarative CPU control
Talos is on v1.15.0-alpha.2 while stable branches keep receiving maintenance releases such as v1.13.12. The alpha adds boot partition waiting for late-enumerated disks, container swap limits and a declarative CPUScalingConfig document. It also generates containerd configuration version 4, under which settings that moved between versions are silently ignored in custom CRI configs apart from a logged warning.
The feed holds two releases of Harness Open Source, tracked here as Gitness. v3.2.0 in May 2025 added Git LFS, default reviewers through branch rules and a Revert PR option; v3.3.0 that August added tag rules, a PR dashboard upgrade with favourite repositories, and a fix for a Git LFS upload path flaw. Nothing newer appears here.
Both releases deepen code-hosting governance: branch rules, then tag rules, plus review routing through Code Owners. That is parity work against established Git hosts rather than a new direction. With entries more than a year old, the feed shows where the project was heading in 2025, not where it is now.
The entries do not support a confident call: there is no release in this feed after v3.3.0, so it is unclear whether the project slowed or the feed stopped tracking it.
Talos is on v1.15.0-alpha.2 while stable branches keep receiving maintenance releases such as v1.13.12. The alpha adds boot partition waiting for late-enumerated disks, container swap limits and a declarative CPUScalingConfig document. It also generates containerd configuration version 4, under which settings that moved between versions are silently ignored in custom CRI configs apart from a logged warning.
The 1.15 cycle extends Talos's habit of replacing kernel arguments and raw system settings with typed configuration documents. Networking dominated 1.14 and the first 1.15 alpha; alpha.2 widens that approach to hardware and resource control, and consolidates talosctl around a shared --namespace flag. The containerd change is the real operational cost of the cycle, because a customized metrics or gRPC section stops taking effect with only a logged warning.
Expect more typed documents for settings that still live in kernel arguments or SysfsConfig keys, and further alphas before a beta. Operators with CRICustomizationConfig patches should expect migration guidance to feature in the eventual 1.15 upgrade notes.
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 Gitness or Talos Linux.
Lima 2.3 nears release, with a Windows path that drops QEMU and a new TUI
Verdaccio's v9 pre-release counter reaches 41, and the notes still say nothing
Snort 3.12.4 pairs a long memory-safety pass with detection speed work
Nineteen patches into 3.2, HAProxy's ingress controller is mostly bumping dependencies
Honeycomb is working on the first ten minutes, not just the incident
Pinot 1.6 adds SQL DDL and vector backends, and now needs Java 25 to run its services.
See all Gitness alternatives → · See all Talos Linux alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — self-hosted — within Infra & APIs. Talos Linux 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. Talos Linux 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 Infra & APIs products to evaluate alongside.
Top Gitness alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Gitness alternatives" section above for the current picks, or visit /alternatives/gitness for the full list with editorial commentary on each.
Top Talos Linux alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Talos Linux alternatives" section above for the current picks, or visit /alternatives/talos-linux for the full list with editorial commentary on each.