Update vendor of containers/(common,storage,image) #1626
Conversation
Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
There was a problem hiding this comment.
I mean, sure — but could we record why is this being done (this way), please?
What makes the three updates simultaneously so important that we want to upgrade (all of them), and so unimportant that they aren’t tagged as upstream releases? All three at the same time?!
| @@ -238,7 +238,7 @@ github.com/golang/protobuf/ptypes/timestamp | |||
| github.com/google/go-intervals/intervalset | |||
| # github.com/google/uuid v1.3.0 | |||
| github.com/google/uuid | |||
| # github.com/gorilla/mux v1.8.0 | |||
| # github.com/gorilla/mux v1.7.4 | |||
There was a problem hiding this comment.
What has happened here?
Trying to reproduce, a go get github.com/containers/common@v0.47.5-0.20220421111103-112a47964ddb adds an
+ github.com/gorilla/mux v1.8.0 // indirectentry to go.mod (and several others like that), so no downgrade happens. Was this PR done in some other way that doesn’t protect against downgrades?
Ultimately, AFAICS that doesn’t change the contents of the vendored code, so it doesn’t matter, but I’m worried that next time such a downgrade could make a difference.
There was a problem hiding this comment.
These vendors were done the same way every vendor was done.
make vendor-in-container
Nothing special.
There was a problem hiding this comment.
vendor-in-container only updates based on a go.mod; the initial operation to point at a newer versions must have been done in some other way.
(Unrelated: vendor-in-container uses quay.io/libpod/golang:1.16; should that be updated? Podman is using 1.17 at least.)
|
We are preparing for RC1 release of Podman, and are trying to avoid doing multiple vendor dances. The goal was to get these three in podman, buildah and skopeo and make sure they pass through their CI systems. We will be bumping releases of all three in the next couple of weeks and then releasing new versions of Podman, Buildah and Skopeo. |
Thanks, that’s helpful. |
Signed-off-by: Daniel J Walsh dwalsh@redhat.com