-
Notifications
You must be signed in to change notification settings - Fork 0
Update module github.com/docker/docker to v28 #69
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
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -7,7 +7,7 @@ require ( | |
| github.com/containerd/containerd/v2 v2.2.5 | ||
| github.com/containerd/platforms v1.0.0-rc.2 | ||
| github.com/distribution/reference v0.6.0 | ||
| github.com/docker/docker v27.5.1+incompatible | ||
| github.com/docker/docker v28.5.2+incompatible | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Because 💡 Suggestion: Ensure CI runs |
||
| github.com/docker/go-connections v0.5.0 | ||
| github.com/google/go-containerregistry v0.20.3 | ||
| github.com/opencontainers/go-digest v1.0.0 | ||
|
|
||
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.
This PR performs a major version upgrade of the direct dependency
github.com/docker/dockerfromv27.5.1+incompatibletov28.5.2+incompatiblewithout any accompanying source code or test changes. Docker v28 can introduce breaking API changes compared to v27, and without verifying usage sites, the project may fail to compile or behave incorrectly at runtime.💡 Suggestion: Confirm that all usages of
github.com/docker/dockerclient types and methods in the codebase are compatible with v28. Rungo build ./...and the full test suite. If the upgrade passes, add or update an integration/unit test that exercises Docker client code paths to catch future regressions.