CRI-O v1.31.4

CRI-O v1.31.4

The release notes have been generated for the commit range v1.31.3…5f8ac6d on Sun, 02 Feb 2025 05:35:09 UTC.

Downloads

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.5f8ac6d4f618b0e60248db1b04dfc32024987554.tar.gz \
    --certificate-identity https://github.com/cri-o/cri-o/.github/workflows/test.yml@refs/tags/5f8ac6d4f618b0e60248db1b04dfc32024987554 \
    --certificate-oidc-issuer https://token.actions.githubusercontent.com \
    --certificate-github-workflow-repository cri-o/cri-o \
    --certificate-github-workflow-ref refs/tags/5f8ac6d4f618b0e60248db1b04dfc32024987554 \
    --signature cri-o.amd64.5f8ac6d4f618b0e60248db1b04dfc32024987554.tar.gz.sig \
    --certificate cri-o.amd64.5f8ac6d4f618b0e60248db1b04dfc32024987554.tar.gz.cert

To verify the bill of materials (SBOM) in SPDX format using the bom tool, run:

> tar xfz cri-o.amd64.5f8ac6d4f618b0e60248db1b04dfc32024987554.tar.gz
> bom validate -e cri-o.amd64.5f8ac6d4f618b0e60248db1b04dfc32024987554.tar.gz.spdx -d cri-o

Changelog since v1.31.3

Changes by Kind

Uncategorized

Add default_annotations to the runtime handler configuration field, allowing admins to specify default annotations to pass to pods (#8862, @openshift-cherrypick-robot)
Fix a panic when default_annotations are used (#8885, @openshift-cherrypick-robot)
Fixed issue when sandbox removal is not possible due to stale or missing network namespace path. (#8820, @openshift-cherrypick-robot)

Dependencies

Added

Nothing has changed.

Changed

github.com/containers/image/v5: v5.32.2 → 0c20855
github.com/containers/storage: 02f1845 → a030a44
github.com/cpuguy83/go-md2man/v2: v2.0.4 → v2.0.5
github.com/urfave/cli: v1.22.14 → v1.22.16
github.com/vbatts/tar-split: v0.11.5 → v0.11.7
golang.org/x/sys: v0.24.0 → v0.26.0

Removed

Nothing has changed.