-
Notifications
You must be signed in to change notification settings - Fork 67
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
switch to github.com/containerd/log module #243
Conversation
Please rebase to pass the CI |
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
1651a36
to
7d07d28
Compare
require github.com/stretchr/testify v1.3.0 // indirect | ||
require ( | ||
github.com/sirupsen/logrus v1.9.3 // indirect | ||
gopkg.in/yaml.v3 v3.0.1 // indirect |
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.
👀
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.
containerd/log doesn't seem to depend on yaml 🤔
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.
Yeah, it's through testify;
go mod graph | grep ' gopkg.in/yaml.v3'
github.com/containerd/continuity gopkg.in/yaml.v3@v3.0.1
github.com/stretchr/testify@v1.7.0 gopkg.in/yaml.v3@v3.0.0-20200313102051-9f266ea9e77c
Which is depended on through logrus;
go mod graph | grep ' github.com/stretchr/testify@v1.7.0'
github.com/sirupsen/logrus@v1.9.3 github.com/stretchr/testify@v1.7.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.
Ah! I think I know what happened; it can be removed indeed. The v3.0.0-20200313102051-9f266ea9e77c
-> v3.0.1
may have been either a manual bump (to prevent an old version with CVEs), or possibly stuck after it was updated indirectly. Go mod doesn't remove such lines automatically, but it doesn't add them back if you remove them manually; it's worth sometimes removing all the // indirect
dependencies, and see if there's ones that are actually gone.
let me open a PR to get rid of it.
No description provided.