This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/registry/servicediscovery/zookeeper/java-server/junit-junit-4.13.1
in repository https://gitbox.apache.org/repos/asf/dubbo-go-samples.git
discard d520a051 Build(deps-dev): bump junit
add 0c2d2666 Build(deps): bump dubbo in
/rpc/triple/pb/dubbogo-java/java-server (#332)
add 54fe7161 Build(deps): bump protobuf-java in
/rpc/triple/hessian2/java-server (#338)
add 98ee7379 Build(deps-dev): bump junit in
/rpc/triple/hessian2/java-server (#339)
add 568c126f Build(deps): bump dubbo in /rpc/triple/hessian2/java-client
(#340)
add 40825b7e Build(deps): bump protobuf-java in
/rpc/triple/hessian2/java-client (#341)
add 430206b6 Build(deps-dev): bump junit in
/rpc/triple/hessian2/java-client (#342)
add 255fe34a Build(deps): bump dubbo (#343)
add c0920adf Build(deps): bump protobuf-java (#344)
add e66c395f Build(deps-dev): bump junit
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 (d520a051)
\
N -- N -- N
refs/heads/dependabot/maven/registry/servicediscovery/zookeeper/java-server/junit-junit-4.13.1
(e66c395f)
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:
registry/servicediscovery/zookeeper/java-server/pom.xml | 4 ++--
rpc/triple/hessian2/java-client/pom.xml | 6 +++---
rpc/triple/hessian2/java-server/pom.xml | 4 ++--
rpc/triple/pb/dubbogo-java/java-server/pom.xml | 2 +-
4 files changed, 8 insertions(+), 8 deletions(-)
