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
Update containerd/containerd indirect test dep #15816
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Marking draft until shirou/gopsutil#1310 is resolved to fix the build. |
Note that CVE-2022-31030 has come out since so we should also bump |
This dependency is pulled in from our testing infra and not in our final Vault version. However, updating this dep pulls in newer versions of other deps (such as protobuf) which are used at runtime. Updated via: $ go get github.com/containerd/containerd@v1.5.13 && go mod tidy Signed-off-by: Alexander Scheel <alex.scheel@hashicorp.com>
Since docker/docker has an indirect dep on containerd, I've updated it as well: $ go get github.com/docker/docker@v20.10.16 && go mod tidy Signed-off-by: Alexander Scheel <alex.scheel@hashicorp.com>
8931bb9
to
a18bdea
Compare
Per conversation with @ncabatoff, by using |
Thanks all! Merging... |
This dependency is pulled in from our testing infra and not in our final
Vault version. However, updating this dep pulls in newer versions of
other deps (such as
protobuf
) which are used at runtime. Updated via:Since docker/docker has an indirect dep on containerd, I've updated it
as well:
Signed-off-by: Alexander Scheel <alex.scheel@hashicorp.com>
Inclined not to backport to 1.11 since this is a testing dep. Anyone know if we need to update
vault-testing-stepwise
as well?Inclined not to add a changelog as the motivation was for the containerd test dep, but if others feel the other updates warrant a changelog, happy to add one.
Resolves: #15639
/cc @mickael-hc