Skip to content

Merge tag 'v5.33.0' into main #2634

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 3 commits into from
Nov 18, 2024
Merged

Conversation

mtrmac
Copy link
Collaborator

@mtrmac mtrmac commented Nov 15, 2024

... so that Go tooling sees the main branch as later than v5.33.0.

Tag v5.33.0 is equivalent to commit 8b9301c on the main branch, but the tag is actually not directly on the main branch, so Go sees current main as v5.32.3-0.202411… , a downgrade from v5.33.0.

This merge should fix that.

Bumping c/storage to v1.56.0 as part of the SIC vendor dance
for Podman v5.3.0

Signed-off-by: tomsweeneyredhat <tsweeney@redhat.com>
Bump to c/image v5.33.0 in preparation for Podman v5.3

Signed-off-by: tomsweeneyredhat <tsweeney@redhat.com>
@mtrmac
Copy link
Collaborator Author

mtrmac commented Nov 15, 2024

Cc: @TomSweeneyRedHat

@mtrmac mtrmac changed the title Merge tag 'v5.33.0' into into-main Merge tag 'v5.33.0' into main Nov 15, 2024
v5.33.0

Signed-off-by: Miloslav Trmač <mitr@redhat.com>
@TomSweeneyRedHat TomSweeneyRedHat merged commit b706d93 into containers:main Nov 18, 2024
10 checks passed
@TomSweeneyRedHat
Copy link
Member

Ooops, forgot the LGTM loop, so officially
LGTM

@mtrmac mtrmac deleted the into-main branch November 19, 2024 16:06
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