Rancher
The public feed carries tags and image manifests; the release notes live in Prime docs.
A side-by-side editorial comparison of Argo Rollouts and Dashy — release velocity, themes, recent moves, and the top alternatives to consider.
An RC-only feed where 1.9's headline change was reverted before it shipped.
Every entry in this window is a release candidate; no GA tag appears at all. The 1.9 line spent three RCs largely on pipeline problems — rc3 explicitly ships no changes from rc2 — and its one architectural change was withdrawn. That change would have narrowed .status.selector to report only the stable ReplicaSet for traffic-routed canaries so HPA stopped counting canary pods in its desired-replica math. The 1.10.0-rc1 notes are dominated by build and dependency work.
Dashy ships a release per merged PR — the real 4.5 features are already scrolling off the feed.
The self-hosted dashboard cuts a version for essentially every merged pull request, so the recent window is a mix of dependabot bumps, German translations, an out-of-memory fix from unclosed secureConnect listeners, OIDC post-logout redirect support, and new sorting by provider and item ID. The 4.5.0 release that carries the substance — drag-and-drop editing of sections, items and widgets, a rebuilt GitHub stats widget on the official API, and number formatting in the custom-api widget — sits just outside this window.
Every entry in this window is a release candidate; no GA tag appears at all. The 1.9 line spent three RCs largely on pipeline problems — rc3 explicitly ships no changes from rc2 — and its one architectural change was withdrawn. That change would have narrowed .status.selector to report only the stable ReplicaSet for traffic-routed canaries so HPA stopped counting canary pods in its desired-replica math. The 1.10.0-rc1 notes are dominated by build and dependency work.
The visible direction is operational rather than behavioural: notifications broadened to Teams workflows and NATS.io, a build system parameterized for company forks, CI skipped for docs-only changes, a move to pnpm. The selector revert says the project would rather live with awkward HPA math than break autoscaling for existing users, so progressive-delivery mechanics stay where they are.
1.10.0 looks likely to land close to rc1 — dependency, CVE and notification work with no controller-semantics change — and the HPA selector question stays open unless it returns behind an opt-in flag.
The self-hosted dashboard cuts a version for essentially every merged pull request, so the recent window is a mix of dependabot bumps, German translations, an out-of-memory fix from unclosed secureConnect listeners, OIDC post-logout redirect support, and new sorting by provider and item ID. The 4.5.0 release that carries the substance — drag-and-drop editing of sections, items and widgets, a rebuilt GitHub stats widget on the official API, and number formatting in the custom-api widget — sits just outside this window.
Development is steady and community-driven, with a maintainer handling auth and stability while contributors add widgets, sorting and translations. The direction after 4.5.0 is refinement rather than expansion: fix what the new editing surface exposed, round out OIDC, keep dependencies current. The per-PR release cadence makes the feed noisy relative to how much actually changes.
Expect the 4.5.x patch stream to continue at roughly a release every few days, dominated by dependency bumps and follow-up fixes to the drag-and-drop editor. Larger features will land in a 4.6 cut rather than trickling through patches.
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 Argo Rollouts or Dashy.
The public feed carries tags and image manifests; the release notes live in Prime docs.
Three release channels at once as werf 3 takes shape beside a still-shipping 2.75.
Volatility 3 caught up with Volatility 2, then started reorganising itself.
A small LDAP server that grew OpenTelemetry tracing, embedded plugins and RISC-V builds.
OctoPrint 2.0 turns serial into one connector among several, and breaks plugins doing it.
Patch tags land monthly with release notes that itemize nothing.
See all Argo Rollouts alternatives → · See all Dashy alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Dashy is currently shipping more aggressively (velocity 6.3 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. Dashy is currently shipping more aggressively (velocity 6.3 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 Argo Rollouts alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Argo Rollouts alternatives" section above for the current picks, or visit /alternatives/argo-rollouts for the full list with editorial commentary on each.
Top Dashy alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Dashy alternatives" section above for the current picks, or visit /alternatives/dashy for the full list with editorial commentary on each.