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

Bump to v5.26.0 #2013

Merged
merged 2 commits into from
Jun 27, 2023
Merged

Bump to v5.26.0 #2013

merged 2 commits into from
Jun 27, 2023

Conversation

TomSweeneyRedHat
Copy link
Member

Bump to v5.26.0

I bumped to 5.27.0-dev, too, as I'm planning to create a release branch for v5.26.0, and that's where 5.26.1 will get generated. We'll use v5.26.* for RHEL 8.8/9.3 either in Podman v4.6 or v4.7, the version number is to be decided.
[NO NEW TESTS NEEDED]

Bump to v5.26.0 in preparation of Podman v4.6

[NO NEW TESTS NEEDED]

Signed-off-by: Tom Sweeney <tsweeney@redhat.com>
Bump to v5.27.0-dev.  I intend to make a release branch for v5.26,
thus bumping to 27 dev here.

[NO NEW TESTS NEEDED]

Signed-off-by: Tom Sweeney <tsweeney@redhat.com>
Copy link
Collaborator

@mtrmac mtrmac left a comment

Choose a reason for hiding this comment

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

LGTM.

Actually there is no new APIs since 5.25.0, only bug fixes, behavior changes and internal work to allow future features — so this could plausibly be a 5.25.1.

OTOH e.g. now requiring TLS 1.2 might be a big enough deal to not do that in a patch release, at least per the VersionPatch documentation.

“Skipping” 5.26.1 is fair enough.

@mtrmac mtrmac merged commit c7f692d into containers:main Jun 27, 2023
9 checks passed
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.

2 participants