The release notes have been generated for the commit range v1.31.0…6adc9a4 on Fri, 22 Nov 2024 00:10:20 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.6adc9a4f25b3d03295894a00e9ad9c0d01431621.tar.gz \
--certificate-identity https://github.com/cri-o/cri-o/.github/workflows/test.yml@refs/tags/6adc9a4f25b3d03295894a00e9ad9c0d01431621 \
--certificate-oidc-issuer https://token.actions.githubusercontent.com \
--certificate-github-workflow-repository cri-o/cri-o \
--certificate-github-workflow-ref refs/tags/6adc9a4f25b3d03295894a00e9ad9c0d01431621 \
--signature cri-o.amd64.6adc9a4f25b3d03295894a00e9ad9c0d01431621.tar.gz.sig \
--certificate cri-o.amd64.6adc9a4f25b3d03295894a00e9ad9c0d01431621.tar.gz.cert
To verify the bill of materials (SBOM) in SPDX format using the bom tool, run:
> tar xfz cri-o.amd64.6adc9a4f25b3d03295894a00e9ad9c0d01431621.tar.gz
> bom validate -e cri-o.amd64.6adc9a4f25b3d03295894a00e9ad9c0d01431621.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. (#8754, @MarSik)goroutines subcommand and /debug/goroutines HTTP endpoint for printing the go routine stack. (#8697, @saschagrunert)heap subcommand and /debug/heap HTTP endpoint for creating memory heap dumps. (#8702, @saschagrunert)SignatureValidationFailed CRI error for invalid signatures. (#8656, @saschagrunert)allowed_annotation specified twice (in either a workload or runtime) couldn’t be used (#8628, @haircommander)RFC3339Nano timestamp log format (2006-01-02T15:04:05.999999999Z07:00) (#8592, @saschagrunert)