The release notes have been generated for the commit range v1.31.1…2a28261 on Wed, 20 Nov 2024 14:16:24 UTC.
Download one of our static release bundles via our Google Cloud Bucket:
To verify the artifact signatures via cosign, run:
> export COSIGN_EXPERIMENTAL=1
> cosign verify-blob cri-o.amd64.2a28261689b174d95c55f5be3f737dc82fb85a02.tar.gz \
--certificate-identity https://github.com/cri-o/cri-o/.github/workflows/test.yml@refs/tags/2a28261689b174d95c55f5be3f737dc82fb85a02 \
--certificate-oidc-issuer https://token.actions.githubusercontent.com \
--certificate-github-workflow-repository cri-o/cri-o \
--certificate-github-workflow-ref refs/tags/2a28261689b174d95c55f5be3f737dc82fb85a02 \
--signature cri-o.amd64.2a28261689b174d95c55f5be3f737dc82fb85a02.tar.gz.sig \
--certificate cri-o.amd64.2a28261689b174d95c55f5be3f737dc82fb85a02.tar.gz.cert
To verify the bill of materials (SBOM) in SPDX format using the bom tool, run:
> tar xfz cri-o.amd64.2a28261689b174d95c55f5be3f737dc82fb85a02.tar.gz
> bom validate -e cri-o.amd64.2a28261689b174d95c55f5be3f737dc82fb85a02.tar.gz.spdx -d cri-o
use_default_runtime
. Setting it to true causes the values for runtime path, runtime type and runtime root to be inherited from the currently configured default runtime. (#8762, @openshift-cherrypick-robot)allowed_annotation
specified twice (in either a workload or runtime) couldn’t be used (#8710, @openshift-cherrypick-robot)Nothing has changed.
Nothing has changed.