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 Tekton Pipelines — 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.
Tekton names a new LTS while patching five older lines in the same fortnight
Tekton Pipeline maintains an unusually wide set of branches — v1.3, v1.6, v1.9, v1.12, v1.14 and now v1.15 all received releases recently, several cut within minutes of each other. v1.15.0 arrives as an LTS with configurable backoffs, following v1.14.0 which added pipelines-in-pipelines by reference along with leaner controllers and sturdier reconcilers. Every release carries a Rekor attestation UUID.
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.
Tekton Pipeline maintains an unusually wide set of branches — v1.3, v1.6, v1.9, v1.12, v1.14 and now v1.15 all received releases recently, several cut within minutes of each other. v1.15.0 arrives as an LTS with configurable backoffs, following v1.14.0 which added pipelines-in-pipelines by reference along with leaner controllers and sturdier reconcilers. Every release carries a Rekor attestation UUID.
Two things are consistent here: composability is the feature direction, and supply-chain provenance is non-negotiable — attestation is part of every release entry, including patches on years-old branches. The LTS designation matters more than the version number for platform teams, since it determines what they can standardise on without re-qualifying every quarter.
Expect patch releases to concentrate on v1.15 and the previous LTS lines, with older branches like v1.3 and v1.6 receiving fixes only until their support windows close.
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 Tekton Pipelines.
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 Tekton Pipelines alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — kubernetes — within Infra & APIs. Tekton Pipelines is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 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. Tekton Pipelines is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 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 Tekton Pipelines alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Tekton Pipelines alternatives" section above for the current picks, or visit /alternatives/tekton for the full list with editorial commentary on each.