rancher / rio

Application Deployment Engine for Kubernetes
https://rio.io
Apache License 2.0
2.27k stars 228 forks source link

Bump github.com/containerd/containerd from 1.3.3 to 1.4.13 #1073

Open dependabot[bot] opened 2 years ago

dependabot[bot] commented 2 years ago

Bumps github.com/containerd/containerd from 1.3.3 to 1.4.13.

Release notes

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

containerd 1.4.13

Welcome to the v1.4.13 release of containerd!

The thirteenth patch release for containerd 1.4 is a security release to address CVE-2022-23648.

Notable Updates

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

  • Derek McGowan
  • Sebastiaan van Stijn
  • Phil Estes
  • Akihiro Suda
  • David Porter
  • Kazuyoshi Kato
  • Michael Crosby

Changes

  • Github Security Advisory GHSA-crp2-qrr5-8pq7
    • Prepare release notes for v1.4.13
    • Use fs.RootPath when mounting volumes
  • [release/1.4] backport: Wait for containerd installation in GCE scripts (#6553)
    • Wait for containerd installation in GCE scripts
  • [release/1.4] Update Go to 1.16.14 (#6527)
    • Do not use go get to install executables
    • [release/1.4] update Go to 1.16.14
    • [release/1.4] Update Go to 1.16.13
  • [release/1.4] vendor: github.com/opencontainers/image-spec v1.0.2 (#6265)
    • [release/1.4] vendor: github.com/opencontainers/image-spec v1.0.2
  • [release/1.4] Update Go to 1.16.12 (#6368)
    • [release/1.4] Update Go to 1.16.12
  • [release/1.4] update runc binary to v1.0.3 (#6344)
    • update runc binary to v1.0.3
  • [release/1.4] Update Go to 1.16.11 (#6335)
    • [release/1.4] Update Go to 1.16.11

Changes from containerd/cri

... (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
  • 9cc6152 Merge pull request from GHSA-crp2-qrr5-8pq7
  • 3e5a4a9 Prepare release notes for v1.4.13
  • 3406af8 Use fs.RootPath when mounting volumes
  • 7aa560b Merge pull request #6553 from bobbypage/backport-6544-1-4
  • 6d93874 Wait for containerd installation in GCE scripts
  • b5811c7 Merge pull request #6527 from thaJeztah/1.4_update_go
  • d6d073b Do not use go get to install executables
  • b907c24 [release/1.4] update Go to 1.16.14
  • f524d6d [release/1.4] Update Go to 1.16.13
  • 0475ec3 Merge pull request #6265 from thaJeztah/1.4_bump_oci_spec
  • 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) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/rancher/rio/network/alerts).