search

openshift / check-payload

Apache License 2.0
10 stars 28 forks source link

chore(deps): bump github.com/containerd/containerd from 1.5.7 to 1.5.18 #127

Closed dependabot[bot] closed 8 months ago

dependabot[bot] commented 8 months ago

Bumps github.com/containerd/containerd from 1.5.7 to 1.5.18.

Release notes

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

containerd 1.5.18

Welcome to the v1.5.18 release of containerd!

The eighteenth patch release for containerd 1.5 includes fixes for CVE-2023-25153 and CVE-2023-25173 along with a security update for Go.

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

  • Akihiro Suda
  • Derek McGowan
  • Ye Sijun
  • Samuel Karp
  • Phil Estes
  • Swagat Bora
  • Wei Fu

Changes

  • [release/1.5] Prepare release notes for v1.5.18 (#8117)
    • ddf9de6cb Prepare release notes for v1.5.18
  • Github Security Advisory GHSA-hmfx-3pcx-653p
    • a62c38bf2 oci: fix additional GIDs
    • 3b89da580 oci: fix loop iterator aliasing
    • b07ec6b25 oci: skip checking gid for WithAppendAdditionalGroups
    • 356672cb5 refactor: reduce duplicate code
    • 6a7b7617c add WithAdditionalGIDs test
    • 832bcf300 add WithAppendAdditionalGroups helper
  • Github Security Advisory GHSA-259w-8hf6-59c2
    • 19a347e45 importer: stream oci-layout and manifest.json
  • [release/1.5] Go 1.19.6 (#8112)
  • [release/1.5] Fix retry logic within devmapper device deactivation (#8089)
    • 0d16d045d Fix retry logic within devmapper device deactivation
  • [release/1.5] CI: skip some jobs when repo != containerd/containerd (#8084)
    • 34451bc66 CI: skip some jobs when repo != containerd/containerd

... (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
  • 39bb06f Merge pull request #8117 from dmcgowan/prepare-v1.5.18
  • ddf9de6 Prepare release notes for v1.5.18
  • 28e4618 Merge pull request from GHSA-hmfx-3pcx-653p
  • 959e1cf Merge pull request from GHSA-259w-8hf6-59c2
  • b4538c2 Merge pull request #8112 from AkihiroSuda/cherrypick-8109-1.5
  • 4209dc2 Go 1.19.6
  • 7c3b243 Merge pull request #8089 from swagatbora90/backport-1.5
  • 0d16d04 Fix retry logic within devmapper device deactivation
  • 9e9f4c8 Merge pull request #8084 from AkihiroSuda/ci-skip-on-fork-1.5
  • a62c38b oci: fix additional GIDs
  • 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 show 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) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/openshift/check-payload/network/alerts).
openshift-ci[bot] commented 8 months ago

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

I'm waiting for a openshift 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.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
rphillips commented 8 months ago

/lgtm /approve

openshift-ci[bot] commented 8 months ago

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dependabot[bot], rphillips

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

The pull request process is described here

Needs approval from an approver in each of these files: - ~~[OWNERS](https://github.com/openshift/check-payload/blob/main/OWNERS)~~ [rphillips] Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment
openshift-ci[bot] commented 8 months ago

@dependabot[bot]: all tests passed!

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).