Skip to content

Update runc binary to v1.3.0#11785

Merged
AkihiroSuda merged 1 commit intocontainerd:mainfrom
austinvazquez:update-runc-1.3.0
May 2, 2025
Merged

Update runc binary to v1.3.0#11785
AkihiroSuda merged 1 commit intocontainerd:mainfrom
austinvazquez:update-runc-1.3.0

Conversation

@austinvazquez
Copy link
Member

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

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-ci-robot
Copy link

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@github-project-automation github-project-automation bot moved this from Needs Triage to Review In Progress in Pull Request Review May 2, 2025
@AkihiroSuda AkihiroSuda added this pull request to the merge queue May 2, 2025
Merged via the queue into containerd:main with commit ca28217 May 2, 2025
99 of 102 checks passed
@github-project-automation github-project-automation bot moved this from Review In Progress to Done in Pull Request Review May 2, 2025
@akhilerm
Copy link
Member

akhilerm commented May 6, 2025

/cherry-pick release/2.0
/cherry-pick release/1.7
/cherry-pick release/1.6

@k8s-infra-cherrypick-robot

@akhilerm: new pull request created: #11799

Details

In response to this:

/cherry-pick release/2.0
/cherry-pick release/1.7
/cherry-pick release/1.6

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.

@k8s-infra-cherrypick-robot

@akhilerm: new pull request created: #11800

Details

In response to this:

/cherry-pick release/2.0
/cherry-pick release/1.7
/cherry-pick release/1.6

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.

@k8s-infra-cherrypick-robot

@akhilerm: new pull request created: #11801

Details

In response to this:

/cherry-pick release/2.0
/cherry-pick release/1.7
/cherry-pick release/1.6

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.

@akhilerm
Copy link
Member

/cherry-pick release/1.6

@k8s-infra-cherrypick-robot

@akhilerm: new pull request could not be created: failed to create pull request against containerd/containerd#release/1.6 from head k8s-infra-cherrypick-robot:cherry-pick-11785-to-release/1.6: status code 422 not one of [201], body: {"message":"Validation Failed","errors":[{"resource":"PullRequest","code":"custom","message":"A pull request already exists for k8s-infra-cherrypick-robot:cherry-pick-11785-to-release/1.6."}],"documentation_url":"https://docs.github.com/rest/pulls/pulls#create-a-pull-request","status":"422"}

Details

In response to this:

/cherry-pick release/1.6

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

5 participants