-
Notifications
You must be signed in to change notification settings - Fork 528
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 go mod
deps, regenerate /vendor
#1139
Conversation
Codecov Report
@@ Coverage Diff @@
## main #1139 +/- ##
============================
============================
Continue to review full report at Codecov.
|
Can you cite an unhappy consumer today? What's being fixed? |
Dependabot, at least for |
Your PR description could use some work.
In any case, thanks for doing this. I'd just like to understand more the thought process behind it. |
…vendor` Signed-off-by: Jake Sanders <jsand@google.com>
Updated the commit and PR comment. I agree that go-containerregistry isn't affected, but it costs ~nothing to get rid of the warning and avoid any potential future fire drill(s) as scanners pick it up |
Make dependabot & consumers happy. This silences a dependabot vuln alert for
containerd
which does not affectgo-containerregistry
but does show up on a scan of our dependency graph.Generated by: