Update to container-libs main#6904
Merged
giuseppe merged 2 commits intoJun 11, 2026
Merged
Conversation
Move our main branch onto container-libs main: * go get go.podman.io/storage@main go.podman.io/image/v5@main go.podman.io/common@main * make vendor-in-container Signed-off-by: Nalin Dahyabhai <nalin@redhat.com>
Signed-off-by: Nalin Dahyabhai <nalin@redhat.com>
|
Ephemeral COPR build failed. @containers/packit-build please check. |
Contributor
|
Hmm, thought I LGTM'd this earlier today. Anywho, |
Contributor
Author
|
@podman-container-tools/buildah-maintainers PTAL |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
What type of PR is this?
/kind other
What this PR does / why we need it:
Moves our main branch onto container-libs main:
How to verify it
No new tests.
Which issue(s) this PR fixes:
Should unblock #6899.
Special notes for your reviewer:
Does this PR introduce a user-facing change?