dependabot(deps): bump the kubernetes-version-matrix-release-pins group across 6 directories with 1 update

[dependabot]

Bumps the kubernetes-version-matrix-release-pins group with 1 update in the /images/capi/packer/config/kubernetes-version-dependencies/release-1-31 directory: github.com/containerd/containerd/v2.
Bumps the kubernetes-version-matrix-release-pins group with 1 update in the /images/capi/packer/config/kubernetes-version-dependencies/release-1-32 directory: github.com/containerd/containerd/v2.
Bumps the kubernetes-version-matrix-release-pins group with 1 update in the /images/capi/packer/config/kubernetes-version-dependencies/release-1-33 directory: github.com/containerd/containerd/v2.
Bumps the kubernetes-version-matrix-release-pins group with 1 update in the /images/capi/packer/config/kubernetes-version-dependencies/release-1-34 directory: github.com/containerd/containerd/v2.
Bumps the kubernetes-version-matrix-release-pins group with 1 update in the /images/capi/packer/config/kubernetes-version-dependencies/release-1-35 directory: github.com/containerd/containerd/v2.
Bumps the kubernetes-version-matrix-release-pins group with 1 update in the /images/capi/packer/config/kubernetes-version-dependencies/release-1-36 directory: github.com/containerd/containerd/v2.

Updates github.com/containerd/containerd/v2 from 2.3.2 to 2.3.4

Release notes

Sourced from github.com/containerd/containerd/v2's releases.

containerd 2.3.4

Welcome to the v2.3.4 release of containerd!

The fourth patch release for containerd 2.3 contains various fixes and updates.

Highlights

Container Runtime Interface (CRI)

• Disable checkpoint restore in CreateContainer by default, requiring the enable_experimental_restore_via_create configuration option to enable (#13913)
• Set default runtimeFeatures.UserNamespacesHostNetwork to true in CRI (#13914)
• Deprecate checkpoint restore in CreateContainer (#13868)
• Support non-UTF-8 binary environment variable values in CRI (#13454)
• Enable OCI runtime feature introspection for non-runc runtimes in CRI (#13778)
• Disable checkpoint restore codepaths when CRIU is not installed and add enable_criu configuration option (#13734)
• Normalize sandbox image references in CRI to resolve images without domain prefixes (#13759)

Node Resource Interface (NRI)

• Emit deprecation warnings for plugins using deprecated NRI interfaces (#13935)

Runtime

• Enable log scrubbing by default on Windows (#13904)
• Fix memory leak in OOM watcher map when stopping container monitoring (#13870)
• Avoid orphaning shims on transient errors when loading process IDs (#13857)
• Fix corruption of binary protobuf shim start responses caused by premature whitespace trimming (#13803)

Snapshotters

• Fix EROFS snapshotter dropping lower layers stacked above merged filesystem metadata (#13876)

Breaking

• Disable checkpoint restore in CreateContainer by default, requiring the enable_experimental_restore_via_create configuration option to enable (#13913)

Deprecations

• Deprecate checkpoint restore in CreateContainer (#13868)

Please try out the release binaries and report any issues at https://github.com/containerd/containerd/issues.

Contributors

• Samuel Karp
• Maksym Pavlenko
• Mike Brown
• Akihiro Suda
• Derek McGowan

... (truncated)

Changelog

Sourced from github.com/containerd/containerd/v2's changelog.

Versioning and Release

This document details the versioning and release plan for containerd. Stability is a top goal for this project, and we hope that this document and the processes it entails will help to achieve that. It covers the release process, versioning numbering, backporting, API stability and support horizons.

If you rely on containerd, it would be good to spend time understanding the areas of the API that are and are not supported and how they impact your project in the future.

This document will be considered a living document. Supported timelines, backport targets and API stability guarantees will be updated here as they change.

If there is something that you require or this document leaves out, please reach out by filing an issue.

Releases

Releases of containerd will be versioned using dotted triples, similar to Semantic Version. For the purposes of this document, we will refer to the respective components of this triple as <major>.<minor>.<patch>. The version number may have additional information, such as alpha, beta and release candidate qualifications. Such releases will be considered "pre-releases".

Major and Minor Releases

Major and minor releases of containerd will be made from main. Releases of containerd will be marked with GPG signed tags and announced at https://github.com/containerd/containerd/releases. The tag will be of the format v<major>.<minor>.<patch> and should be made with the command git tag -s v<major>.<minor>.<patch>.

After a minor release, a branch will be created, with the format release/<major>.<minor> from the minor tag. All further patch releases will be done from that branch. For example, once we release v1.0.0, a branch release/1.0 will be created from that tag. All future patch releases will be done against that branch.

Release Cadence

Since containerd v2.3 in April 2026, minor releases are provided on a time basis with a cadence of 4 months. New minor releases are scheduled for April, August, and December of each year. This cadence is synchronized with the Kubernetes release schedule to ensure that new features in containerd can be smoothly adopted by new Kubernetes releases.

The maintainers will maintain a roadmap and milestones for each release, however,

... (truncated)

Commits

• db88095 Merge pull request #13942 from samuelkarp/prepare-release-2.3.4
• 6c13edd Merge pull request #13945 from erofs/erofs-fix-backport
• 3aef405 snapshots/erofs: protect snapshot staging from cleanup
• c1f5360 Prepare release notes for v2.3.4
• a553459 Merge pull request #13913 from samuelkarp/toggle-experimental-criu-restore-2.3
• d79eeb2 Merge pull request #13935 from k8s-infra-cherrypick-robot/cherry-pick-13916-t...
• 5966e2e nri,deprecation: emit warnings for old NRI plugins.
• 14b5e7d Merge pull request #13914 from k8s-infra-cherrypick-robot/cherry-pick-13162-t...
• ab52c58 Set the default of runtimeFeatures.UserNamespacesHostNetwork to true
• 928c03c cri: disable restore in CreateContainer by default
• Additional commits viewable in compare view

Updates github.com/containerd/containerd/v2 from 2.3.2 to 2.3.4

Release notes

Sourced from github.com/containerd/containerd/v2's releases.

containerd 2.3.4

Welcome to the v2.3.4 release of containerd!

The fourth patch release for containerd 2.3 contains various fixes and updates.

Highlights

Container Runtime Interface (CRI)

• Disable checkpoint restore in CreateContainer by default, requiring the enable_experimental_restore_via_create configuration option to enable (#13913)
• Set default runtimeFeatures.UserNamespacesHostNetwork to true in CRI (#13914)
• Deprecate checkpoint restore in CreateContainer (#13868)
• Support non-UTF-8 binary environment variable values in CRI (#13454)
• Enable OCI runtime feature introspection for non-runc runtimes in CRI (#13778)
• Disable checkpoint restore codepaths when CRIU is not installed and add enable_criu configuration option (#13734)
• Normalize sandbox image references in CRI to resolve images without domain prefixes (#13759)

Node Resource Interface (NRI)

• Emit deprecation warnings for plugins using deprecated NRI interfaces (#13935)

Runtime

• Enable log scrubbing by default on Windows (#13904)
• Fix memory leak in OOM watcher map when stopping container monitoring (#13870)
• Avoid orphaning shims on transient errors when loading process IDs (#13857)
• Fix corruption of binary protobuf shim start responses caused by premature whitespace trimming (#13803)

Snapshotters

• Fix EROFS snapshotter dropping lower layers stacked above merged filesystem metadata (#13876)

Breaking

• Disable checkpoint restore in CreateContainer by default, requiring the enable_experimental_restore_via_create configuration option to enable (#13913)

Deprecations

• Deprecate checkpoint restore in CreateContainer (#13868)

Please try out the release binaries and report any issues at https://github.com/containerd/containerd/issues.

Contributors

• Samuel Karp
• Maksym Pavlenko
• Mike Brown
• Akihiro Suda
• Derek McGowan

... (truncated)

Changelog

Sourced from github.com/containerd/containerd/v2's changelog.

Versioning and Release

This document details the versioning and release plan for containerd. Stability is a top goal for this project, and we hope that this document and the processes it entails will help to achieve that. It covers the release process, versioning numbering, backporting, API stability and support horizons.

If you rely on containerd, it would be good to spend time understanding the areas of the API that are and are not supported and how they impact your project in the future.

This document will be considered a living document. Supported timelines, backport targets and API stability guarantees will be updated here as they change.

If there is something that you require or this document leaves out, please reach out by filing an issue.

Releases

Releases of containerd will be versioned using dotted triples, similar to Semantic Version. For the purposes of this document, we will refer to the respective components of this triple as <major>.<minor>.<patch>. The version number may have additional information, such as alpha, beta and release candidate qualifications. Such releases will be considered "pre-releases".

Major and Minor Releases

Major and minor releases of containerd will be made from main. Releases of containerd will be marked with GPG signed tags and announced at https://github.com/containerd/containerd/releases. The tag will be of the format v<major>.<minor>.<patch> and should be made with the command git tag -s v<major>.<minor>.<patch>.

After a minor release, a branch will be created, with the format release/<major>.<minor> from the minor tag. All further patch releases will be done from that branch. For example, once we release v1.0.0, a branch release/1.0 will be created from that tag. All future patch releases will be done against that branch.

Release Cadence

Since containerd v2.3 in April 2026, minor releases are provided on a time basis with a cadence of 4 months. New minor releases are scheduled for April, August, and December of each year. This cadence is synchronized with the Kubernetes release schedule to ensure that new features in containerd can be smoothly adopted by new Kubernetes releases.

The maintainers will maintain a roadmap and milestones for each release, however,

... (truncated)

Commits

• db88095 Merge pull request #13942 from samuelkarp/prepare-release-2.3.4
• 6c13edd Merge pull request #13945 from erofs/erofs-fix-backport
• 3aef405 snapshots/erofs: protect snapshot staging from cleanup
• c1f5360 Prepare release notes for v2.3.4
• a553459 Merge pull request #13913 from samuelkarp/toggle-experimental-criu-restore-2.3
• d79eeb2 Merge pull request #13935 from k8s-infra-cherrypick-robot/cherry-pick-13916-t...
• 5966e2e nri,deprecation: emit warnings for old NRI plugins.
• 14b5e7d Merge pull request #13914 from k8s-infra-cherrypick-robot/cherry-pick-13162-t...
• ab52c58 Set the default of runtimeFeatures.UserNamespacesHostNetwork to true
• 928c03c cri: disable restore in CreateContainer by default
• Additional commits viewable in compare view

Updates github.com/containerd/containerd/v2 from 2.3.2 to 2.3.4

Release notes

Sourced from github.com/containerd/containerd/v2's releases.

containerd 2.3.4

Welcome to the v2.3.4 release of containerd!

The fourth patch release for containerd 2.3 contains various fixes and updates.

Highlights

Container Runtime Interface (CRI)

• Disable checkpoint restore in CreateContainer by default, requiring the enable_experimental_restore_via_create configuration option to enable (#13913)
• Set default runtimeFeatures.UserNamespacesHostNetwork to true in CRI (#13914)
• Deprecate checkpoint restore in CreateContainer (#13868)
• Support non-UTF-8 binary environment variable values in CRI (#13454)
• Enable OCI runtime feature introspection for non-runc runtimes in CRI (#13778)
• Disable checkpoint restore codepaths when CRIU is not installed and add enable_criu configuration option (#13734)
• Normalize sandbox image references in CRI to resolve images without domain prefixes (#13759)

Node Resource Interface (NRI)

• Emit deprecation warnings for plugins using deprecated NRI interfaces (#13935)

Runtime

• Enable log scrubbing by default on Windows (#13904)
• Fix memory leak in OOM watcher map when stopping container monitoring (#13870)
• Avoid orphaning shims on transient errors when loading process IDs (#13857)
• Fix corruption of binary protobuf shim start responses caused by premature whitespace trimming (#13803)

Snapshotters

• Fix EROFS snapshotter dropping lower layers stacked above merged filesystem metadata (#13876)

Breaking

• Disable checkpoint restore in CreateContainer by default, requiring the enable_experimental_restore_via_create configuration option to enable (#13913)

Deprecations

• Deprecate checkpoint restore in CreateContainer (#13868)

Please try out the release binaries and report any issues at https://github.com/containerd/containerd/issues.

Contributors

• Samuel Karp
• Maksym Pavlenko
• Mike Brown
• Akihiro Suda
• Derek McGowan

... (truncated)

Changelog

Sourced from github.com/containerd/containerd/v2's changelog.

Versioning and Release

This document details the versioning and release plan for containerd. Stability is a top goal for this project, and we hope that this document and the processes it entails will help to achieve that. It covers the release process, versioning numbering, backporting, API stability and support horizons.

If you rely on containerd, it would be good to spend time understanding the areas of the API that are and are not supported and how they impact your project in the future.

This document will be considered a living document. Supported timelines, backport targets and API stability guarantees will be updated here as they change.

If there is something that you require or this document leaves out, please reach out by filing an issue.

Releases

Releases of containerd will be versioned using dotted triples, similar to Semantic Version. For the purposes of this document, we will refer to the respective components of this triple as <major>.<minor>.<patch>. The version number may have additional information, such as alpha, beta and release candidate qualifications. Such releases will be considered "pre-releases".

Major and Minor Releases

Major and minor releases of containerd will be made from main. Releases of containerd will be marked with GPG signed tags and announced at https://github.com/containerd/containerd/releases. The tag will be of the format v<major>.<minor>.<patch> and should be made with the command git tag -s v<major>.<minor>.<patch>.

After a minor release, a branch will be created, with the format release/<major>.<minor> from the minor tag. All further patch releases will be done from that branch. For example, once we release v1.0.0, a branch release/1.0 will be created from that tag. All future patch releases will be done against that branch.

Release Cadence

Since containerd v2.3 in April 2026, minor releases are provided on a time basis with a cadence of 4 months. New minor releases are scheduled for April, August, and December of each year. This cadence is synchronized with the Kubernetes release schedule to ensure that new features in containerd can be smoothly adopted by new Kubernetes releases.

The maintainers will maintain a roadmap and milestones for each release, however,

... (truncated)

Commits

• db88095 Merge pull request #13942 from samuelkarp/prepare-release-2.3.4
• 6c13edd Merge pull request #13945 from erofs/erofs-fix-backport
• 3aef405 snapshots/erofs: protect snapshot staging from cleanup
• c1f5360 Prepare release notes for v2.3.4
• a553459 Merge pull request #13913 from samuelkarp/toggle-experimental-criu-restore-2.3
• d79eeb2 Merge pull request #13935 from k8s-infra-cherrypick-robot/cherry-pick-13916-t...
• 5966e2e nri,deprecation: emit warnings for old NRI plugins.
• 14b5e7d Merge pull request #13914 from k8s-infra-cherrypick-robot/cherry-pick-13162-t...
• ab52c58 Set the default of runtimeFeatures.UserNamespacesHostNetwork to true
• 928c03c cri: disable restore in CreateContainer by default
• Additional commits viewable in compare view

Updates github.com/containerd/containerd/v2 from 2.3.2 to 2.3.4

Release notes

Sourced from github.com/containerd/containerd/v2's releases.

containerd 2.3.4

Welcome to the v2.3.4 release of containerd!

The fourth patch release for containerd 2.3 contains various fixes and updates.

Highlights

Container Runtime Interface (CRI)

• Disable checkpoint restore in CreateContainer by default, requiring the enable_experimental_restore_via_create configuration option to enable (#13913)
• Set default runtimeFeatures.UserNamespacesHostNetwork to true in CRI (#13914)
• Deprecate checkpoint restore in CreateContainer (#13868)
• Support non-UTF-8 binary environment variable values in CRI (#13454)
• Enable OCI runtime feature introspection for non-runc runtimes in CRI (#13778)
• Disable checkpoint restore codepaths when CRIU is not installed and add enable_criu configuration option (#13734)
• Normalize sandbox image references in CRI to resolve images without domain prefixes (#13759)

Node Resource Interface (NRI)

• Emit deprecation warnings for plugins using deprecated NRI interfaces (#13935)

Runtime

• Enable log scrubbing by default on Windows (#13904)
• Fix memory leak in OOM watcher map when stopping container monitoring (#13870)
• Avoid orphaning shims on transient errors when loading process IDs (#13857)
• Fix corruption of binary protobuf shim start responses caused by premature whitespace trimming (#13803)

Snapshotters

• Fix EROFS snapshotter dropping lower layers stacked above merged filesystem metadata (#13876)

Breaking

• Disable checkpoint restore in CreateContainer by default, requiring the enable_experimental_restore_via_create configuration option to enable (#13913)

Deprecations

• Deprecate checkpoint restore in CreateContainer (#13868)

Please try out the release binaries and report any issues at https://github.com/containerd/containerd/issues.

Contributors

• Samuel Karp
• Maksym Pavlenko
• Mike Brown
• Akihiro Suda
• Derek McGowan

... (truncated)

Changelog

Sourced from github.com/containerd/containerd/v2's changelog.

Versioning and Release

This document details the versioning and release plan for containerd. Stability is a top goal for this project, and we hope that this document and the processes it entails will help to achieve that. It covers the release process, versioning numbering, backporting, API stability and support horizons.

If you rely on containerd, it would be good to spend time understanding the areas of the API that are and are not supported and how they impact your project in the future.

This document will be considered a living document. Supported timelines, backport targets and API stability guarantees will be updated here as they change.

If there is something that you require or this document leaves out, please reach out by filing an issue.

Releases

Releases of containerd will be versioned using dotted triples, similar to Semantic Version. For the purposes of this document, we will refer to the respective components of this triple as <major>.<minor>.<patch>. The version number may have additional information, such as alpha, beta and release candidate qualifications. Such releases will be considered "pre-releases".

Major and Minor Releases

Major and minor releases of containerd will be made from main. Releases of containerd will be marked with GPG signed tags and announced at https://github.com/containerd/containerd/releases. The tag will be of the format v<major>.<minor>.<patch> and should be made with the command git tag -s v<major>.<minor>.<patch>.

After a minor release, a branch will be created, with the format release/<major>.<minor> from the minor tag. All further patch releases will be done from that branch. For example, once we release v1.0.0, a branch release/1.0 will be created from that tag. All future patch releases will be done against that branch.

Release Cadence

Since containerd v2.3 in April 2026, minor releases are provided on a time basis with a cadence of 4 months. New minor releases are scheduled for April, August, and December of each year. This cadence is synchronized with the Kubernetes release schedule to ensure that new features in containerd can be smoothly adopted by new Kubernetes releases.

The maintainers will maintain a roadmap and milestones for each release, however,

... (truncated)

Commits

• db88095 Merge pull request #13942 from samuelkarp/prepare-release-2.3.4
• 6c13edd Merge pull request #13945 from erofs/erofs-fix-backport
• 3aef405 snapshots/erofs: protect snapshot staging from cleanup
• c1f5360 Prepare release notes for v2.3.4
• a553459 Merge pull request #13913 from samuelkarp/toggle-experimental-criu-restore-2.3
• d79eeb2 Merge pull request #13935 from k8s-infra-cherrypick-robot/cherry-pick-13916-t...
• 5966e2e nri,deprecation: emit warnings for old NRI plugins.
• 14b5e7d Merge pull request #13914 from k8s-infra-cherrypick-robot/cherry-pick-13162-t...
• ab52c58 Set the default of runtimeFeatures.UserNamespacesHostNetwork to true
• 928c03c cri: disable restore in CreateContainer by default
• Additional commits viewable in compare view

Updates github.com/containerd/containerd/v2 from 2.3.2 to 2.3.4

Release notes

Sourced from github.com/containerd/containerd/v2's releases.

containerd 2.3.4

Welcome to the v2.3.4 release of containerd!

The fourth patch release for containerd 2.3 contains various fixes and updates.

Highlights

Container Runtime Interface (CRI)

• Disable checkpoint restore in CreateContainer by default, requiring the enable_experimental_restore_via_create configuration option to enable (#13913)
• Set default runtimeFeatures.UserNamespacesHostNetwork to true in CRI (#13914)
• Deprecate checkpoint restore in CreateContainer (#13868)
• Support non-UTF-8 binary environment variable values in CRI (#13454)
• Enable OCI runtime feature introspection for non-runc runtimes in CRI (#13778)
• Disable checkpoint restore codepaths when CRIU is not installed and add enable_criu configuration option (#13734)
• Normalize sandbox image references in CRI to resolve images without domain prefixes (#13759)

Node Resource Interface (NRI)

• Emit deprecation warnings for plugins using deprecated NRI interfaces (#13935)

Runtime

• Enable log scrubbing by default on Windows (#13904)
• Fix memory leak in OOM watcher map when stopping container monitoring (#13870)
• Avoid orphaning shims on transient errors when loading process IDs (#13857)
• Fix corruption of binary protobuf shim start responses caused by premature whitespace trimming (#13803)

Snapshotters

• Fix EROFS snapshotter dropping lower layers stacked above merged filesystem metadata (#13876)

Breaking

• Disable checkpoint restore in CreateContainer by default, requiring the enable_experimental_restore_via_create configuration option to enable (#13913)

Deprecations

• Deprecate checkpoint restore in CreateContainer (#13868)

Please try out the release binaries and report any issues at https://github.com/containerd/containerd/issues.

Contributors

• Samuel Karp
• Maksym Pavlenko
• Mike Brown
• Akihiro Suda
• Derek McGowan

... (truncated)

Changelog

Sourced from github.com/containerd/containerd/v2's changelog.

Versioning and Release

This document details the versioning and release plan for containerd. Stability is a top goal for this project, and we hope that this document and the processes it entails will help to achieve that. It covers the release process, versioning numbering, backporting, API stability and support horizons.

If you rely on containerd, it would be good to spend time understanding the areas of the API that are and are not supported and how they impact your project in the future.

This document will be considered a living document. Supported timelines, backport targets and API stability guarantees will be updated here as they change.

If there is something that you require or this document leaves out, please reach out by filing an issue.

Releases

Releases of containerd will be versioned using dotted triples, similar to Semantic Version. For the purposes of this document, we will refer to the respective components of this triple as <major>.<minor>.<patch>. The version number may have additional information, such as alpha, beta and release candidate qualifications. Such releases will be considered "pre-releases".

Major and Minor Releases

Major and minor releases of containerd will be made from main. Releases of containerd will be marked with GPG signed tags and announced at https://github.com/containerd/containerd/releases. The tag will be of the format v<major>.<minor>.<patch> and should be made with the command git tag -s v<major>.<minor>.<patch>.

After a minor release, a branch will be created, with the format release/<major>.<minor> from the minor tag. All further patch releases will be done from that branch. For example, once we release v1.0.0, a branch release/1.0 will be created from that tag. All future patch releases will be done against that branch.

Release Cadence

Since containerd v2.3 in April 2026, minor releases are provided on a time basis with a cadence of 4 months. New minor releases are scheduled for April, August, and December of each year. This cadence is synchronized with the Kubernetes release schedule to ensure that new features in containerd can be smoothly adopted by new Kubernetes releases.

The maintainers will maintain a roadmap and milestones for each release, however,

... (truncated)

Commits

• db88095 Merge pull request #13942 from samuelkarp/prepare-release-2.3.4
• 6c13edd Merge pull request #13945 from erofs/erofs-fix-backport
• 3aef405 snapshots/erofs: protect snapshot staging from cleanup
• c1f5360 Prepare release notes for v2.3.4
• a553459 Merge pull request #13913 from samuelkarp/toggle-experimental-criu-restore-2.3
• d79eeb2 Merge pull request #13935 from k8s-infra-cherrypick-robot/cherry-pick-13916-t...
• 5966e2e nri,deprecation: emit warnings for old NRI plugins.
• 14b5e7d Merge pull request #13914 from k8s-infra-cherrypick-robot/cherry-pick-13162-t...
• ab52c58 Set the default of runtimeFeatures.UserNamespacesHostNetwork to true
• 928c03c cri: disable restore in CreateContainer by default
• Additional commits viewable in compare view

Updates github.com/containerd/containerd/v2 from 2.3.2 to 2.3.4

Release notes

Sourced from github.com/containerd/containerd/v2's releases.

containerd 2.3.4

Welcome to the v2.3.4 release of containerd!

The fourth patch release for containerd 2.3 contains various fixes and updates.

Highlights

Container Runtime Interface (CRI)

• Disable checkpoint restore in CreateContainer by default, requiring the enable_experimental_restore_via_create configuration option to enable (#13913)
• Set default runtimeFeatures.UserNamespacesHostNetwork to true in CRI (#13914)
• Deprecate checkpoint restore in CreateContainer (#13868)
• Support non-UTF-8 binary environment variable values in CRI (#13454)
• Enable OCI runtime feature introspection for non-runc runtimes in CRI (#13778)
• Disable checkpoint restore codepaths when CRIU is not installed and add enable_criu configuration option (#13734)
• Normalize sandbox image references in CRI to resolve images without domain prefixes (#13759)

Node Resource Interface (NRI)

• Emit deprecation warnings for plugins using deprecated NRI interfaces (#13935)

Runtime

• Enable log scrubbing by default on Windows (#13904)
• Fix memory leak in OOM watcher map when stopping container monitoring (#13870)
• Avoid orphaning shims on transient errors when loading process IDs (#13857)
• Fix corruption of binary protobuf shim start responses caused by premature whitespace trimming (#13803)

Snapshotters

• Fix EROFS snapshotter dropping lower layers stacked above merged filesystem metadata (#13876)

Breaking

• Disable checkpoint restore in CreateContainer by default, requiring the enable_experimental_restore_via_create configuration option to enable (#13913)

Deprecations

• Deprecate checkpoint restore in CreateContainer (#13868)

Please try out the release binaries and report any issues at https://github.com/containerd/containerd/issues.

Contributors

• Samuel Karp
• Maksym Pavlenko
• Mike Brown
• Akihiro Suda
• Derek McGowan

... (truncated)

Changelog

Sourced from github.com/containerd/containerd/v2's changelog.

Versioning and Release

This document details the versioning and release plan for containerd. Stability is a top goal for this project, and we hope that this document and the processes it entails will help to achieve that. It covers the release process, versioning numbering, backporting, API stability and support horizons.

If you rely on containerd, it would be good to spend time understanding the areas of the API that are and are not supported and how they impact your project in the future.

This document will be considered a living document. Supported timelines, backport targets and API stability guarantees will be updated here as they change.

If there is something that you require or this document leaves out, please reach out by filing an issue.

Releases

Releases of containerd will be versioned using dotted triples, similar to Semantic Version. For the purposes of this document, we will refer to the respective components of this triple as <major>.<minor>.<patch>. The version number may have additional information, such as alpha, beta and release candidate qualifications. Such releases will be considered "pre-releases".

Major and Minor Releases

Major and minor releases of containerd will be made from main. Releases of containerd will be marked with GPG signed tags and announced at https://github.com/containerd/containerd/releases. The tag will be of the format v<major>.<minor>.<patch> and should be made with the command git tag -s v<major>.<minor>.<patch>.

After a minor release, a branch will be created, with the format release/<major>.<minor> from the minor tag. All further patch releases will be done from that branch. For example, once we release v1.0.0, a branch release/1.0 will be created from that tag. All future patch releases will be done against that branch.

Release Cadence

Since containerd v2.3 in April 2026, minor releases are provided on a time basis with a cadence of 4 months. New minor releases are scheduled for April, August, and December of each year. This cadence is synchronized with the Kubernetes release schedule to ensure that new features in containerd can be smoothly adopted by new Kubernetes releases.

The maintainers will maintain a roadmap and milestones for each release, however,

... (truncated)

Commits

• db88095 Merge pull request #13942 from samuelkarp/prepare-release-2.3.4
• 6c13edd Merge pull request #13945 from erofs/erofs-fix-backport
• 3aef405 snapshots/erofs: protect snapshot staging from cleanup
• c1f5360 Prepare release notes for v2.3.4
• a553459 Merge pull request #13913 from samuelkarp/toggle-experimental-criu-restore-2.3
• d79eeb2 Merge pull request #13935 from k8s-infra-cherrypick-robot/cherry-pick-13916-t...
• 5966e2e nri,deprecation: emit warnings for old NRI plugins.
• 14b5e7d Merge pull request #13914 from k8s-infra-cherrypick-robot/cherry-pick-13162-t...
• ab52c58 Set the default of runtimeFeatures.UserNamespacesHostNetwork to true
• 928c03c cri: disable restore in CreateContainer by default
• Additional commits viewable in compare view

[kubernetes-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign averagemarcus for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[kubernetes-prow]

Hi @dependabot[bot]. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.