This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/go_modules/github.com/containers/image/v5-5.30.1
in repository https://gitbox.apache.org/repos/asf/dubbo-kubernetes.git
omit b0470a67 --- updated-dependencies: - dependency-name:
github.com/containers/image/v5 dependency-type: direct:production ...
add f551ce8a fix(core/registry): Fix the bug where obtaining instance
metadata information failed in universal mode
add 8c164776 go mod tidy
add f493d76f Merge pull request #289 from Allen442/master
add 6fe85e6d --- updated-dependencies: - dependency-name:
github.com/containers/image/v5 dependency-type: direct:production ...
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (b0470a67)
\
N -- N -- N
refs/heads/dependabot/go_modules/github.com/containers/image/v5-5.30.1
(6fe85e6d)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
No new revisions were added by this update.
Summary of changes:
go.mod | 7 +----
go.sum | 14 +---------
.../global.go => registry/metadata_instance.go} | 30 ++++++++++++----------
.../service_instances_changed_listener_impl.go | 15 ++++++-----
4 files changed, 26 insertions(+), 40 deletions(-)
copy pkg/core/{resources/registry/global.go => registry/metadata_instance.go}
(56%)
