Oh Dear
Oh Dear's weekly changelogs have carried a security section five weeks running.
A side-by-side editorial comparison of Robusta and runc — release velocity, themes, recent moves, and the top alternatives to consider.
Robusta's recent releases patch its runner image rather than add features.
Robusta ships from an alpha channel, so alpha tags are its release line. The October tags are almost entirely image and CI work: 0.52.0-alpha patched high and critical CVEs in the runner image and removed orphaned Perl packages after a Debian upgrade, 0.52.0-alpha.1 backported OpenSSH, curl, expat and systemd fixes from Debian forky, and 0.54.0-alpha's notes cover only the removal of helm golden-file tests from CI. The last feature work in the feed was August's workflow trigger action and the signing-key leak fix.
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.
Robusta ships from an alpha channel, so alpha tags are its release line. The October tags are almost entirely image and CI work: 0.52.0-alpha patched high and critical CVEs in the runner image and removed orphaned Perl packages after a Debian upgrade, 0.52.0-alpha.1 backported OpenSSH, curl, expat and systemd fixes from Debian forky, and 0.54.0-alpha's notes cover only the removal of helm golden-file tests from CI. The last feature work in the feed was August's workflow trigger action and the signing-key leak fix.
Since late August the project has been treating its container image as the product surface that needs attention, with CVE patching handled by backporting packages from the next Debian release. The feature line that added workflow chaining, JSON logs and new alert sources has gone quiet in these entries. The 0.53 tag does not appear in the feed, so part of the picture may be missing.
Expect more runner-image CVE releases on the alpha line. Whether feature work on Holmes integration or alert sources resumes is not visible in these entries.
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.
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.
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.
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 Robusta or runc.
Oh Dear's weekly changelogs have carried a security section five weeks running.
ShenYu's AI gateway plugins are back in motion, with 2.7.2 candidate tags in October.
TestingBot's autumn work is plumbing: a rebuilt tunnel and another bug-tracker link.
KubeArmor ships fixes as release-candidate tags, and its feed misses the finals.
All Quiet moves from enterprise integrations to the on-call engineer's own day.
Uptrends spent October on account plumbing: vault credentials, bulk edits and a free trial path.
See all Robusta alternatives → · See all runc alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Robusta 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. Robusta 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 Robusta alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Robusta alternatives" section above for the current picks, or visit /alternatives/robusta for the full list with editorial commentary on each.
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.