Bump github.com/containerd/containerd from 1.7.11 to 1.7.20

[dependabot]

Bumps github.com/containerd/containerd from 1.7.11 to 1.7.20.

Release notes

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

containerd 1.7.20

Welcome to the v1.7.20 release of containerd!

The twentieth patch release for containerd 1.7 contains various fixes and updates.

Highlights

• Support for dropping inheritable capabilities (#10469)

Container Runtime Interface (CRI)

• Make PodSandboxStatus friendlier to shim crashes (#10461)
• Handle empty DNSConfig differently than unspecified (#10462)
• Fix for [cri] ttrpc: closed during ListPodSandboxStats (#10423)

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

Contributors

• Derek McGowan
• Akihiro Suda
• Phil Estes
• Akhil Mohan
• Bryant Biggs
• Danny Canter
• Davanum Srinivas
• Mike Brown
• Samuel Karp
• Tim Hockin

Changes

• Prepare release notes for v1.7.20 (#10481)
  • 7f2d4cd97 Prepare release notes for v1.7.20
• deps: Update otelgrpc (#10413)
  • 3a02c523d deps: Update otelgrpc
• Make PodSandboxStatus friendlier to shim crashes (#10461)
  • df86bdd5d CRI Sbserver: Make PodSandboxStatus friendlier to shim crashes
• Handle empty DNSConfig differently than unspecified (#10462)
  • 209ee4f10 CRI: An empty DNSConfig != unspecified
• Support for dropping inheritable capabilities (#10469)
  • ce65228af Support for dropping inheritable capabilities
• Fix for [cri] ttrpc: closed during ListPodSandboxStats (#10423)
  • 610498df7 Fix for [cri] ttrpc: closed during ListPodSandboxStats
• update to go1.21.12 / go1.22.5 (#10426)
  • e61c7932e update to go1.21.12 / go1.22.5

... (truncated)

Changelog

Sourced from github.com/containerd/containerd'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.

Pre-releases

Pre-releases, such as alphas, betas and release candidates will be conducted from their source branch. For major and minor releases, these releases will be done from main. For patch releases, these pre-releases should be done within the corresponding release branch.

While pre-releases are done to assist in the stabilization process, no guarantees are provided.

... (truncated)

Commits

• 8fc6bcf Merge pull request #10481 from dmcgowan/prepare-v1.7.20
• 7f2d4cd Prepare release notes for v1.7.20
• 7eb0501 Merge pull request #10413 from austinvazquez/cherry-pick-78421616e0a6ba76ac25...
• 34ea461 Merge pull request #10461dims/automated-cherry-pick-of-#8367
• 87c908e Merge pull request #10462dims/automated-cherry-pick-of-#9730
• b06e353 Merge pull request #10469dims/automated-cherry-pick-of-#8356
• 209ee4f CRI: An empty DNSConfig != unspecified
• ce65228 Support for dropping inheritable capabilities
• df86bdd CRI Sbserver: Make PodSandboxStatus friendlier to shim crashes
• 923bb1f Merge pull request #10423 from dims/cri-ttrpc-closed-during-ListPodSandboxStats
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)