Rancher
The public feed carries tags and image manifests; the release notes live in Prime docs.
A side-by-side editorial comparison of CRI-O and GLAuth — release velocity, themes, recent moves, and the top alternatives to consider.
Patch tags land monthly with release notes that itemize nothing.
The three most recent CRI-O entries are v1.34.11, v1.34.10 and v1.33.13, cut roughly a month apart across two supported minor lines. All three carry auto-generated notes whose 'Changes by Kind' sections are empty or labelled Uncategorized, with the body given over to download bundles, checksums, SPDX manifests and signatures. Only v1.34.10 admits to a Bug or Regression category, and does not say what it was.
A small LDAP server that grew OpenTelemetry tracing, embedded plugins and RISC-V builds.
GLAuth's 2.5.0 in April was the substantial release: OpenTelemetry tracing wired through the handler and plugin packages plus otelsql, embedded plugins, RISC-V platform support, StartTLS and LDAPS brought to feature parity, and LDAP paging compatibility when proxying. The two releases since are corrective — rejecting disabled users on all backends during Bind, an arbitrary-password issue, and a release-time plugin compatibility check.
The three most recent CRI-O entries are v1.34.11, v1.34.10 and v1.33.13, cut roughly a month apart across two supported minor lines. All three carry auto-generated notes whose 'Changes by Kind' sections are empty or labelled Uncategorized, with the body given over to download bundles, checksums, SPDX manifests and signatures. Only v1.34.10 admits to a Bug or Regression category, and does not say what it was.
What the feed does show is release engineering: every tag ships static bundles per architecture with checksums, SPDX SBOMs and signing bundles, which is the supply-chain posture Kubernetes runtimes are now expected to hold. The absence of itemized changes means the actual runtime work is invisible here, so read this feed as a release calendar for the 1.33 and 1.34 branches rather than a changelog.
Expect the same monthly patch cadence on both maintained branches, with content that stays uncategorized unless the project changes how it generates notes.
GLAuth's 2.5.0 in April was the substantial release: OpenTelemetry tracing wired through the handler and plugin packages plus otelsql, embedded plugins, RISC-V platform support, StartTLS and LDAPS brought to feature parity, and LDAP paging compatibility when proxying. The two releases since are corrective — rejecting disabled users on all backends during Bind, an arbitrary-password issue, and a release-time plugin compatibility check.
The direction in 2.5.0 is toward being operable in production rather than merely functional: distributed tracing, a config watcher that notices files added to a directory, credentials no longer leaking at INFO log level, and a legacy behaviour mode so existing deployments can upgrade without changing semantics. The patches since suggest the authentication paths are getting scrutiny they had not previously had, with disabled-user handling inconsistent across backends until 2.5.1 fixed it.
Expect the 2.5 line to keep taking small authentication-correctness fixes, with the embedded plugin mechanism and the release-time compatibility check pointing toward more attention on how third-party backends are built and shipped.
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 CRI-O or GLAuth.
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.
OctoPrint 2.0 turns serial into one connector among several, and breaks plugins doing it.
A self-hosted PaaS spending its releases on secrets, injection fixes and plan limits.
One release a year, each one a filesystem or networking rewrite you must plan for.
See all CRI-O alternatives → · See all GLAuth alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. GLAuth 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. GLAuth 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 Infra & APIs products to evaluate alongside.
Top CRI-O alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "CRI-O alternatives" section above for the current picks, or visit /alternatives/cri-o for the full list with editorial commentary on each.
Top GLAuth alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "GLAuth alternatives" section above for the current picks, or visit /alternatives/glauth for the full list with editorial commentary on each.