Skip to content

[release/1.6] Update runc binary to v1.3.0#11799

Merged
mikebrow merged 1 commit intocontainerd:release/1.6from
k8s-infra-cherrypick-robot:cherry-pick-11785-to-release/1.6
Jun 9, 2025
Merged

[release/1.6] Update runc binary to v1.3.0#11799
mikebrow merged 1 commit intocontainerd:release/1.6from
k8s-infra-cherrypick-robot:cherry-pick-11785-to-release/1.6

Conversation

@k8s-infra-cherrypick-robot

This is an automated cherry-pick of #11785

/assign akhilerm

@k8s-ci-robot
Copy link

Hi @k8s-infra-cherrypick-robot. Thanks for your PR.

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

Details

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-sigs/prow repository.

@dosubot dosubot bot added the area/runtime Runtime label May 6, 2025
@akhilerm
Copy link
Member

akhilerm commented May 6, 2025

/ok-to-test

@austinvazquez
Copy link
Member

1.6 CI is a mess with Ubuntu 20 GHA retirement. Still 2 months of support left though so I guess we need to sort it out.

This is the first release of the 1.3.z release branch of runc. It
contains a few minor fixes for issues found in 1.3.0-rc.2.

This is the first release of runc that will follow our new release and
support policy (see RELEASES.md for more details). This means that, as
of this release:

    As of this release, the runc 1.2.z release branch will now only
    receive security and "significant" bugfixes.
    Users are encouraged to plan migrating to runc 1.3.0 as soon as
    possible.
    Due to its particular situation, runc 1.1.z is officially no longer
    supported and will no longer receive any updates (not even for
    critical security issues). Users are urged (in the strongest possible
    terms) to upgrade to a supported version of runc.
    Barring any future changes to our release policy, users should expect
    a runc 1.4.0 release in late October 2025.

full diff: opencontainers/runc@v1.2.6...v1.3.0

Signed-off-by: Austin Vazquez <austin.vazquez.dev@gmail.com>
@k8s-infra-cherrypick-robot k8s-infra-cherrypick-robot force-pushed the cherry-pick-11785-to-release/1.6 branch from a28ea71 to d00ccf5 Compare May 27, 2025 10:54
@github-project-automation github-project-automation bot moved this from Needs Triage to Review In Progress in Pull Request Review May 27, 2025
@djdongjin djdongjin moved this from Review In Progress to Merge on Green in Pull Request Review Jun 7, 2025
Copy link
Member

@mikebrow mikebrow left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@github-project-automation github-project-automation bot moved this from Merge on Green to Review In Progress in Pull Request Review Jun 9, 2025
@mikebrow mikebrow merged commit c77f56c into containerd:release/1.6 Jun 9, 2025
82 of 83 checks passed
@github-project-automation github-project-automation bot moved this from Review In Progress to Done in Pull Request Review Jun 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

6 participants