tektoncd
Bump github.com/containerd/containerd from 1.5.13 to 1.6.8
Bumps github.com/containerd/containerd from 1.5.13 to 1.6.8.
Release notes
Sourced from github.com/containerd/containerd's releases.
containerd 1.6.8
Welcome to the v1.6.8 release of containerd!
The eighth patch release for containerd 1.6 fixes a regression in the release build binaries which limited the environments they could be run in.
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
- Samuel Karp
- Phil Estes
Changes
- [release/1.6] Prepare release notes for v1.6.8 (#7263)
3364f411ePrepare release notes for v1.6.8- [release/1.6] release workflow: increase timeout to 30 minutes & remove Go setup action (#7261)
- [release/1.6] release: rollback Ubuntu to 18.04 (except for riscv64) (#7260)
57873e652release: rollback Ubuntu to 18.04 (except for riscv64)Dependency Changes
This release has no dependency changes
Previous release can be found at v1.6.7
containerd 1.6.7
Welcome to the v1.6.7 release of containerd!
The seventh patch release for containerd 1.6 contains various fixes, includes a new version of runc and adds support for ppc64le and riscv64 (requires unreleased runc 1.2) builds.
Notable Updates
... (truncated)
Commits
9cd3357Merge pull request #7263 from dmcgowan/prepare-1.6.83364f41Prepare release notes for v1.6.8a76f3c8Merge pull request #7261 from samuelkarp/release-workflow/1.63909204release workflow: remove Go setup actioncf48ba6release workflow: increase timeout to 30 minutes76f5db4Merge pull request #7260 from samuelkarp/fix-7255/1.657873e6release: rollback Ubuntu to 18.04 (except for riscv64)0197261Merge pull request #7250 from dmcgowan/release-1.6-update-build-timeouteccb82fUpdate release build timeout to 20 minutes5f242b5Merge pull request #7225 from dcantah/v1.6.7-rnotes- 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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "Published by a pub.dev verified publisher"){kind=small}
Hi @dependabot[bot]. Thanks for your PR.
I'm waiting for a tektoncd 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. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.
If you change your mind, just re-open this PR and I'll resolve any conflicts on it.
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: vdemeester
The full list of commands accepted by this bot can be found here.
The pull request process is described here
- ~~OWNERS~~ [vdemeester]
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
@abayer: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:
/test pull-tekton-pipeline-alpha-integration-tests/test pull-tekton-pipeline-build-tests/test pull-tekton-pipeline-integration-tests/test tekton-pipeline-unit-tests
The following commands are available to trigger optional jobs:
/test pull-tekton-pipeline-go-coverage
Use /test all to run all jobs.
In response to this:
/test check-pr-has-kind-label
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/test-infra repository.