Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump github.com/containerd/containerd from 1.7.0 to 1.7.2 #6275

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jun 5, 2023

Bumps github.com/containerd/containerd from 1.7.0 to 1.7.2.

Release notes

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

containerd 1.7.2

Welcome to the v1.7.2 release of containerd!

The second patch release for containerd 1.7 includes enhancements to CRI sandbox mode, Windows snapshot mounting support, and CRI and container IO bug fixes.

CRI/Sandbox Updates

  • Publish sandbox events (#8613)
  • Make stats respect sandbox's platform (#8604)

Other Notable Updates

  • Mount snapshots on Windows (#8616)
  • Notify readiness when registered plugins are ready (#8584)
  • Fix cio.Cancel() should close pipes (#8624)
  • CDI: Use CRI Config.CDIDevices field for CDI injection (#8519)

See the changelog for complete list of changes

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

Contributors

  • Gabriel Adrian Samfira
  • Derek McGowan
  • Paul "TBBle" Hampson
  • Maksym Pavlenko
  • Phil Estes
  • Austin Vazquez
  • Akihiro Suda
  • Kazuyoshi Kato
  • Danny Canter
  • Samuel Karp
  • Sebastiaan van Stijn
  • Ed Bartosh
  • Henry Wang
  • Hsing-Yu (David) Chen
  • Jan Dubois
  • Mike Brown
  • Wei Fu
  • helen

Changes

  • [release/1.7] Prepare release notes for v1.7.2 (#8629)
    • 0e41daaea [release/1.7] Prepare release notes for v1.7.2
  • [1.7 backport] Fix panic when remote differ returns empty result (#8631)
    • e134b6393 Fix panic when remote differ returns empty result

... (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
  • 0cae528 Merge pull request #8629 from dcantah/1.7.2-release-notes
  • 0aa82d1 Merge pull request #8631 from thaJeztah/1.7_backport_fix_diff_proxy
  • e134b63 Fix panic when remote differ returns empty result
  • 0e41daa [release/1.7] Prepare release notes for v1.7.2
  • 02a00c3 Merge pull request #8616 from gabriel-samfira/backport-8043
  • a04e94b Merge pull request #8624 from davidhsingyuchen/backport-8334
  • 99582fb fix: cio.Cancel() should close the pipes
  • deec965 Merge pull request #8621 from thaJeztah/1.7_backport_fix_deprecation_comments
  • eeda70f remotes/docker: ResolverOptions: fix deprecation comments
  • 313c226 Update continuity to a tagged version
  • Additional commits viewable in compare view

Dependabot compatibility score

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 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)

Bumps [github.com/containerd/containerd](https://github.com/containerd/containerd) from 1.7.0 to 1.7.2.
- [Release notes](https://github.com/containerd/containerd/releases)
- [Changelog](https://github.com/containerd/containerd/blob/main/RELEASES.md)
- [Commits](containerd/containerd@v1.7.0...v1.7.2)

---
updated-dependencies:
- dependency-name: github.com/containerd/containerd
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file go Pull requests that update Go code labels Jun 5, 2023
@netlify
Copy link

netlify bot commented Jun 5, 2023

Deploy Preview for kubeapps-dev canceled.

Name Link
🔨 Latest commit b087eb3
🔍 Latest deploy log https://app.netlify.com/sites/kubeapps-dev/deploys/647d45386805d3000892a3f8

@absoludity absoludity merged commit 214c96b into main Jun 5, 2023
@absoludity absoludity deleted the dependabot/go_modules/github.com/containerd/containerd-1.7.2 branch June 5, 2023 06:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cla-not-required dependencies Pull requests that update a dependency file go Pull requests that update Go code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants