Skip to content

[1.3] VERSION: release v1.3.0 #4753

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

Merged
merged 2 commits into from
Apr 29, 2025
Merged

Conversation

cyphar
Copy link
Member

@cyphar cyphar commented Apr 29, 2025

Intended release notes:

runc v1.3.0 -- "Mr. President, we must not allow a mine shaft gap!"

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
   recieve 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 receieve 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.

Fixed:

 * Removed pre-emptive "full access to cgroups" warning when calling
   runc pause or runc unpause as an unprivileged user without
   --systemd-cgroups. Now the warning is only emitted if an actual
   permission error was encountered. (#4709)
 * Several fixes to our CI, mainly related to AlmaLinux and CRIU.
   (#4670, #4728, #4736)

Changed:

 * In runc 1.2, we changed our mount behaviour to correctly handle
   clearing flags. However, the error messages we returned did not
   provide as much information to users about what clearing flags were
   conflicting with locked mount flags. We now provide more diagnostic
   information if there is an error when in the fallback path to handle
   locked mount flags. (#4734)
 * Upgrade our CI to use golangci-lint v2.0. (#4692)
 * runc version information is now filled in using //go:embed rather
   than being set through Makefile. This allows go install or other
   non-make builds to contain the correct version information. Note that
   "make EXTRA_VERSION=..." still works. (#418)
 * Remove exclude directives from our go.mod for broken cilium/ebpf
   versions. v0.17.3 resolved the issue we had, and exclude directives
   are incompatible with go install. (#4748)

Thanks to the following contributors for making this release possible:

 * Akihiro Suda <[email protected]>
 * Aleksa Sarai <[email protected]>
 * Kir Kolyshkin <[email protected]>
 * Rodrigo Campos <[email protected]>
 * lifubang <[email protected]>

Signed-off-by: Aleksa Sarai <[email protected]>

cyphar added 2 commits April 29, 2025 14:33
Signed-off-by: Aleksa Sarai <[email protected]>
Signed-off-by: Aleksa Sarai <[email protected]>
@cyphar cyphar added this to the 1.3.0 milestone Apr 29, 2025
@cyphar cyphar requested a review from a team April 29, 2025 04:44
Copy link
Member

@rata rata left a comment

Choose a reason for hiding this comment

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

LGTM, thanks!

@cyphar cyphar merged commit b2397e6 into opencontainers:release-1.3 Apr 29, 2025
34 checks passed
@cyphar cyphar deleted the release-1.3.0 branch April 29, 2025 15:21
@h-vetinari
Copy link

Congratulations on the release (and the new release schedule)! 🥳

One thing that would be nice to have in the 1.{N+1}.0 release notes is all the relevant changes since 1.N.0. Currently the release notes only contain the changes since 1.{N+1}.0.rcX, which is either confusing (for those who mistake the release notes to be complete) or extra work (i.e. manually collating the changes across all release candidates + GA).

PS. Typo: receieve

@kolyshkin
Copy link
Contributor

PS. Typo: receieve

Thanks, fixed in release notes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants