CRI-O v1.30.4

CRI-O v1.30.4

The release notes have been generated for the commit range v1.30.3…95e494c on Mon, 19 Aug 2024 08:03:23 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.95e494c283ab3860511deb23b51429eaf091b7cd.tar.gz \
    --certificate-identity https://github.com/cri-o/cri-o/.github/workflows/test.yml@refs/tags/95e494c283ab3860511deb23b51429eaf091b7cd \
    --certificate-oidc-issuer https://token.actions.githubusercontent.com \
    --certificate-github-workflow-repository cri-o/cri-o \
    --certificate-github-workflow-ref refs/tags/95e494c283ab3860511deb23b51429eaf091b7cd \
    --signature cri-o.amd64.95e494c283ab3860511deb23b51429eaf091b7cd.tar.gz.sig \
    --certificate cri-o.amd64.95e494c283ab3860511deb23b51429eaf091b7cd.tar.gz.cert

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

> tar xfz cri-o.amd64.95e494c283ab3860511deb23b51429eaf091b7cd.tar.gz
> bom validate -e cri-o.amd64.95e494c283ab3860511deb23b51429eaf091b7cd.tar.gz.spdx -d cri-o

Changelog since v1.30.3

Changes by Kind

Feature

Update the type of checks the internal repair feature performs on CRI-O’s start-up following an unclean shutdown, and add a new crio check sub-command. (#8468, @kwilczynski)

Uncategorized

Fixed a bug where stopping a container would block all further stop attempts for the same container. (#8392, @sohankunkerkar)
Reduced “Failed to get pid for pod infra container” NRI message for spoofed containers and lowering the verbosity to DEBUG. (#8435, @openshift-cherrypick-robot)

Dependencies

Added

Nothing has changed.

Changed

Nothing has changed.

Removed

Nothing has changed.