k8s-ci-robot
commented
1 year ago Hi @dependabot[bot]. Thanks for your PR.
I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.
Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
Bumps github.com/google/go-containerregistry from 0.15.2 to 0.16.1.
Release notes
Sourced from github.com/google/go-containerregistry's releases.
Commits
a54d642fix: pin to goreleaser v1.18 to unblock release (#1763)ea19b57Return OCI Index content-type for referrers response (#1762)b850480Drop localhost to support crane registry serve in a container (#1746)fe268b7Don't try cross-origin mounting against dockerhub (#1743)2472cbbLet the filesystem handle atomicity (#1735)db818dcUse RWLock, limit scope of locking, write digest first (#1734)44a6e2eAllow concurrent blob Sets, use RWMutex (#1733)9010ce1Correct crane registry help text (#1732)03ad2acadd --blobs-to-disk to 'crane registry serve' (#1731)4e4b03aDon't load into daemon if the image already exists (#1724)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)