Merge tag 'v5.33.0' into main #2634
Open
+0
−0
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Bumping c/storage to v1.56.0 as part of the SIC vendor dance for Podman v5.3.0 Signed-off-by: tomsweeneyredhat <[email protected]>
Bump to c/image v5.33.0 in preparation for Podman v5.3 Signed-off-by: tomsweeneyredhat <[email protected]>
mtrmac
changed the title
... 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. Signed-off-by: Miloslav Trmač <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
... so that Go tooling sees the main branch as later than
v5.33.0.Tag
v5.33.0is equivalent to commit 8b9301c on themainbranch, but the tag is actually not directly on themainbranch, so Go sees currentmainasv5.32.3-0.202411…, a downgrade fromv5.33.0.This merge should fix that.