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

[Backport release-1.30] Bump containerd to v1.7.24 #5349

Merged

Conversation

twz123
Copy link
Member

@twz123 twz123 commented Dec 11, 2024

https://github.com/containerd/containerd/releases/tag/v1.7.24

Signed-off-by: Tom Wieczorek <[email protected]>
(cherry picked from commit 8d59bdb)
(cherry picked from commit 6bb5702)
@twz123 twz123 added area/containers chore component/containerd backport/release-1.29 PR that needs to be backported/cherrypicked to the release-1.29 branch labels Dec 11, 2024
@twz123 twz123 marked this pull request as ready for review December 11, 2024 18:58
@twz123 twz123 requested a review from a team as a code owner December 11, 2024 18:58
@twz123 twz123 requested review from kke and jnummelin December 11, 2024 18:58
@twz123 twz123 merged commit 9e5d360 into k0sproject:release-1.30 Dec 12, 2024
86 checks passed
@twz123 twz123 deleted the backport-5339-to-release-1.30 branch December 12, 2024 19:40
@k0s-bot
Copy link

k0s-bot commented Dec 12, 2024

Backport failed for release-1.29, because it was unable to cherry-pick the commit(s).

Please cherry-pick the changes locally and resolve any conflicts.

git fetch origin release-1.29
git worktree add -d .worktree/backport-5349-to-release-1.29 origin/release-1.29
cd .worktree/backport-5349-to-release-1.29
git switch --create backport-5349-to-release-1.29
git cherry-pick -x 00a8ca571067043c687798d1129d9af706bf0187

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/containers backport/release-1.29 PR that needs to be backported/cherrypicked to the release-1.29 branch chore component/containerd
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants