The release notes have been generated for the commit range v1.28.11…48c134e on Wed, 30 Apr 2025 18:53:14 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.48c134e17c04f9201c8100f9155513a4d864b7f8.tar.gz \
--certificate-identity https://github.com/cri-o/cri-o/.github/workflows/test.yml@refs/tags/48c134e17c04f9201c8100f9155513a4d864b7f8 \
--certificate-oidc-issuer https://token.actions.githubusercontent.com \
--certificate-github-workflow-repository cri-o/cri-o \
--certificate-github-workflow-ref refs/tags/48c134e17c04f9201c8100f9155513a4d864b7f8 \
--signature cri-o.amd64.48c134e17c04f9201c8100f9155513a4d864b7f8.tar.gz.sig \
--certificate cri-o.amd64.48c134e17c04f9201c8100f9155513a4d864b7f8.tar.gz.cert
To verify the bill of materials (SBOM) in SPDX format using the bom tool, run:
> tar xfz cri-o.amd64.48c134e17c04f9201c8100f9155513a4d864b7f8.tar.gz
> bom validate -e cri-o.amd64.48c134e17c04f9201c8100f9155513a4d864b7f8.tar.gz.spdx -d cri-o
Fixed the issue that /etc/crypto-policies/config in a container isn't updated.
to respect the current behavior (#9166, @bitoku)Nothing has changed.