The release notes have been generated for the commit range v1.31.2…b031f89 on Wed, 18 Dec 2024 19:47:19 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.b031f890da99234425d52c3f1c5b171356cba404.tar.gz \
--certificate-identity https://github.com/cri-o/cri-o/.github/workflows/test.yml@refs/tags/b031f890da99234425d52c3f1c5b171356cba404 \
--certificate-oidc-issuer https://token.actions.githubusercontent.com \
--certificate-github-workflow-repository cri-o/cri-o \
--certificate-github-workflow-ref refs/tags/b031f890da99234425d52c3f1c5b171356cba404 \
--signature cri-o.amd64.b031f890da99234425d52c3f1c5b171356cba404.tar.gz.sig \
--certificate cri-o.amd64.b031f890da99234425d52c3f1c5b171356cba404.tar.gz.cert
To verify the bill of materials (SBOM) in SPDX format using the bom tool, run:
> tar xfz cri-o.amd64.b031f890da99234425d52c3f1c5b171356cba404.tar.gz
> bom validate -e cri-o.amd64.b031f890da99234425d52c3f1c5b171356cba404.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)default_annotations to the runtime handler configuration field, allowing admins to specify default annotations to pass to pods (#8862, @openshift-cherrypick-robot)--pull-progress-timeout / pull_progress_timeout option to fine-tune the timeout for making progress on image pull. (#8776, @openshift-cherrypick-robot)Nothing has changed.
Nothing has changed.
Nothing has changed.