Apache Druid
Druid 38 drops Java 17, recommends Java 25 and took longer to arrive than its predecessors
Comparison · Infra & APIs
Apereo CAS vs runc
A side-by-side editorial comparison of Apereo CAS and runc — release velocity, themes, recent moves, and the top alternatives to consider.
Apereo CAS vs runc: at a glance
What is Apereo CAS?
Apereo CAS opens an 8.1 line while 8.0 is still working through release candidates.
CAS is running a long release-candidate train. The 8.0.0 line reached RC6 in late June after RC4 and RC5 in spring, and 8.1.0-RC1 has now appeared in August. A 7.3.7.1 patch in June addressed a published OIDC vulnerability on the maintenance branch. The release entries themselves carry only navigation links and contributor credits, so feature detail is not visible here.
What is runc?
runc 1.6.0-rc.1 lifts the 1024-CPU limit and refuses settings it used to quietly ignore
The 1.6.0 cycle opened on October 6 with a first release candidate that is mostly cleanup: deprecated libcontainer APIs removed, Go 1.26 now required, urfave/cli moved from v1 to v3, and the binary about 15% smaller on amd64. The changes with operational weight are that cpuAffinity and NUMA memoryPolicy no longer stop at 1024 CPUs or nodes, and that a container asking for a read-only rootfs without its own mount namespace is now refused. Eleven days earlier 1.5.2 worked around a kernel bug, present since v6.17, that corrupted memory inside runc and caused random crashes on cgroup v2. It also stopped runc exec --cgroup from escaping into a sibling cgroup.
Apereo CAS vs runc: editorial side-by-side
Apereo CAS
2.5INFRA · APIS
Apereo CAS opens an 8.1 line while 8.0 is still working through release candidates.
◆ Current state
CAS is running a long release-candidate train. The 8.0.0 line reached RC6 in late June after RC4 and RC5 in spring, and 8.1.0-RC1 has now appeared in August. A 7.3.7.1 patch in June addressed a published OIDC vulnerability on the maintenance branch. The release entries themselves carry only navigation links and contributor credits, so feature detail is not visible here.
◆ Where it's heading
Two lines are moving at once, which suggests 8.0 is close enough to final that work has begun branching forward rather than that the RC train has stalled. The contributor lists stay small and consistent across releases - a handful of recurring maintainers - and security handling happens on the older supported branch, as it should.
◆ Prediction
An 8.0.0 final is the obvious next milestone given RC6 was three months ago and an 8.1 branch is already open. The release bodies do not describe features, so what it contains cannot be read from this feed.
runc
2.5INFRA · APIS
runc 1.6.0-rc.1 lifts the 1024-CPU limit and refuses settings it used to quietly ignore
◆ Current state
The 1.6.0 cycle opened on October 6 with a first release candidate that is mostly cleanup: deprecated libcontainer APIs removed, Go 1.26 now required, urfave/cli moved from v1 to v3, and the binary about 15% smaller on amd64. The changes with operational weight are that cpuAffinity and NUMA memoryPolicy no longer stop at 1024 CPUs or nodes, and that a container asking for a read-only rootfs without its own mount namespace is now refused. Eleven days earlier 1.5.2 worked around a kernel bug, present since v6.17, that corrupted memory inside runc and caused random crashes on cgroup v2. It also stopped runc exec --cgroup from escaping into a sibling cgroup.
◆ Where it's heading
The project keeps converting silent behaviour into explicit behaviour. Read-only requests that were ignored now fail, a umask that was dropped is now honoured, and poststart hooks moved to conform to the runtime spec. The same maintainers are shrinking the surface underneath, dropping the deprecated API and the high-level cilium/ebpf path, which took roughly 7.5% off the 1.5.2 binary. Stricter behaviour plus a smaller dependency set is what a component under every container host would be expected to do between majors.
◆ Prediction
1.5.0's notes pointed to a 1.6.0 in late October 2026, and the feed so far shows only rc.1, so further release candidates or the final are the next entries to expect. The refused read-only configurations are the change most likely to surface as user reports during testing.
Alternatives to Apereo CAS and runc
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 Apereo CAS or runc.
Okta
Okta adds TypeScript to its Cross App Access guides and dates the end of Classic Engine features
Gitness
Harness Open Source last shipped in August 2025, on this feed at least
Payload CMS
Payload's v4 beta ships every few days, and most of the risk sits in the breaking-change notes
Scalar
Scalar is testing demand for hosting from inside localhost
Incus
Incus 7.6 fixes 18 security issues, eight critical, and adds SR-IOV NIC live migration
See all Apereo CAS alternatives → · See all runc alternatives →
Recent activity from Apereo CAS and runc
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 26d agoruncRelease candidate lifts 1024-CPU limit, removes deprecated APIs
- 1mo agoruncWorkaround for kernel bug that crashed runc on cgroup v2
- 2mo agoApereo CASv8.1.0-RC1
- 3mo agorunctmpfs regression on Ubuntu 20.04 kernels fixed
- 4mo agoApereo CASv8.0.0-RC6
- 4mo agoApereo CASPatch release for a published OIDC vulnerability
- 4mo agoruncrunc 1.5.0 stable, with dated support windows for older branches
- 4mo agoruncCVE-2026-41579: /dev symlink host write access fixed
- 4mo agoruncRelease candidate carrying the CVE-2026-41579 fix
- 5mo agoApereo CASv8.0.0-RC5
- 6mo agoApereo CASv8.0.0-RC4
Frequently asked questions
What is the difference between Apereo CAS and runc?
They serve adjacent needs but don't currently overlap on shipped themes. Apereo CAS and runc are shipping at a similar cadence (velocity 2.5 vs 2.5, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is Apereo CAS better than runc?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Apereo CAS and runc are shipping at a similar cadence (velocity 2.5 vs 2.5, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
What are the best alternatives to Apereo CAS?
Top Apereo CAS alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Apereo CAS alternatives" section above for the current picks, or visit /alternatives/apereo-cas for the full list with editorial commentary on each.
What are the best alternatives to runc?
Top runc alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "runc alternatives" section above for the current picks, or visit /alternatives/runc for the full list with editorial commentary on each.