LoginSign Up
← Back to all sparks
C

CRI-O

INFRA · APIS
Velocity2.5

Lightweight container runtime for Kubernetes

cri-o.io ↗

Patch tags land monthly with release notes that itemize nothing.

container-runtimekubernetespatch-cadencesupply-chainsbom
◆Current state
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.
◆Where it's heading
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.
◆Prediction
Expect the same monthly patch cadence on both maintained branches, with content that stays uncategorized unless the project changes how it generates notes.

◆Recent moves

  1. 2d ago

    v1.34.11: patch tag with no itemized changes

    A monthly patch on the 1.34 branch whose generated notes list no categorized changes at all. The only concrete content is the signed, checksummed release bundles.

    View source ↗
  2. 1mo ago

    v1.34.10: patch tag citing an uncategorized regression fix

    The one entry in this window with a Bug or Regression heading, though the section names nothing. Notable only as evidence that the 1.34 branch is taking corrective work.

    View source ↗
  3. 2mo ago

    v1.33.13: patch tag on the older maintained branch

    A parallel patch on 1.33, confirming both minor lines are still being cut on the same monthly rhythm. Contents are again uncategorized.

    View source ↗