The release notes have been generated for the commit range v1.37.0…cc36e00 on Fri, 30 Oct 2026 00:12:00 UTC.
Download one of our static release bundles via our Google Cloud Bucket.
Each bundle includes a SHA-256 checksum, a cosign signature (.bundle), and a SPDX 3 bill of materials (.spdx.json) with its own signature:
The OpenVEX vulnerability report:
The SLSA provenance attestation:
All release artifacts are also available as signed OCI artifacts at ghcr.io/cri-o/bundle:cc36e008e7320722e3cd90a64e7515f41339b51a.
To verify the artifact signatures via cosign, run:
> export COSIGN_EXPERIMENTAL=1
> cosign verify-blob cri-o.amd64.cc36e008e7320722e3cd90a64e7515f41339b51a.tar.gz \
--certificate-identity https://github.com/cri-o/packaging/.github/workflows/obs.yml@refs/heads/main \
--certificate-oidc-issuer https://token.actions.githubusercontent.com \
--certificate-github-workflow-repository cri-o/packaging \
--certificate-github-workflow-ref refs/heads/main \
--bundle cri-o.amd64.cc36e008e7320722e3cd90a64e7515f41339b51a.tar.gz.bundle
To verify the bill of materials (SBOM) in SPDX format using the bom tool (v0.8.0 or later), run:
> tar xfz cri-o.amd64.cc36e008e7320722e3cd90a64e7515f41339b51a.tar.gz
> bom validate -e cri-o.amd64.cc36e008e7320722e3cd90a64e7515f41339b51a.tar.gz.spdx.json -d cri-o
To verify the OpenVEX vulnerability report, run:
> cosign verify-blob cri-o.cc36e008e7320722e3cd90a64e7515f41339b51a.openvex.json \
--certificate-identity https://github.com/cri-o/packaging/.github/workflows/obs.yml@refs/heads/main \
--certificate-oidc-issuer https://token.actions.githubusercontent.com \
--certificate-github-workflow-repository cri-o/packaging \
--certificate-github-workflow-ref refs/heads/main \
--bundle cri-o.cc36e008e7320722e3cd90a64e7515f41339b51a.openvex.json.bundle
To verify the SLSA provenance attestation, run:
> cosign verify-blob cri-o.cc36e008e7320722e3cd90a64e7515f41339b51a.provenance.json \
--certificate-identity https://github.com/cri-o/packaging/.github/workflows/obs.yml@refs/heads/main \
--certificate-oidc-issuer https://token.actions.githubusercontent.com \
--certificate-github-workflow-repository cri-o/packaging \
--certificate-github-workflow-ref refs/heads/main \
--bundle cri-o.cc36e008e7320722e3cd90a64e7515f41339b51a.provenance.json.bundle
stream_websockets and conmon-rs v1.2.0 or later, conmon-rs also serves port forwarding and its streaming sessions end after stream_idle_timeout of inactivity. Older conmon-rs versions disable stream_websockets, and pods started by them keep using the CRI-O streaming server. A conmon-rs server which does not exit on pod removal gets killed. A negative stream_idle_timeout fails the config validation. With conmon-rs, log_to_journald also logs containers to the journal, and exec syncs which conmon-rs could not start fail instead of returning exit code -2 or -3. (#10458, @saschagrunert)monitor_path pointing to conmonrs on a runtime handler with runtime_type = "oci" is now rejected with a hint to use runtime_type = "pod". (#10438, @saschagrunert)monitor_env) instead of the whole CRI-O environment, so variables set only on the CRI-O service (for example OTEL_* or proxy settings) no longer reach conmon-rs and the OCI runtime unless they are added to monitor_env. Attaching to a stdin once container through the conmon-rs streaming server now closes the container stdin when the client closes its stdin. (#10443, @saschagrunert)systemctl --failed indefinitely. (#10343, @amritansh1502).spdx.json instead of SPDX 2.3 tag-value .spdx files. Validating them with bom requires v0.8.0 or later. (#10383, @saschagrunert)Nothing has changed.