Bump c/storage to v1.56.0, c/image to v5.33.0 #2625
Merged
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]>
Bump c/image back to a dev version, v5.34.0-dev Signed-off-by: tomsweeneyredhat <[email protected]>
|
I had all kinds of trouble getting this piece of the dance to work. I had to upgrade my build machine in order to get a high enough version of go, and then after vendoring only the go.* files changed. I'm assuming due to others having pulled from the top of tree recently? |
|
There is no vendor dir here so it is expected that only go.{mod,sum} change. |
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.
Bumping c/image to v5.33.0 after vendoring c/storage v1.56.0
This is in preparation for Podman v5.3