[dubbo-go-samples] branch dependabot/maven/rpc/triple/pb/dubbogo-java/java-client/junit-junit-4.13.1 updated (89dd02d0 -> b3bbc0a5)

[gi...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

github-bot pushed a change to branch dependabot/maven/rpc/triple/pb/dubbogo-java/java-client/junit-junit-4.13.1
in repository https://gitbox.apache.org/repos/asf/dubbo-go-samples.git


    omit 89dd02d0 Build(deps-dev): bump junit in /rpc/triple/pb/dubbogo-java/java-client
     add 6a5cb679 Build(deps): bump zookeeper in /rpc/triple/pb/dubbogo-java/java-server (#328)
     add da67db2d Build(deps): bump zookeeper in /rpc/triple/pb/dubbogo-java/java-client (#329)
     add 4da65e7b Build(deps-dev): bump junit in /rpc/triple/pb/dubbogo-java/java-server (#330)
     add 5fee84c3 Build(deps): bump dubbo in /rpc/triple/pb/dubbogo-java/java-client (#331)
     add b3bbc0a5 Build(deps-dev): bump junit in /rpc/triple/pb/dubbogo-java/java-client

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   (89dd02d0)
            \
             N -- N -- N   refs/heads/dependabot/maven/rpc/triple/pb/dubbogo-java/java-client/junit-junit-4.13.1 (b3bbc0a5)

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:
 rpc/triple/pb/dubbogo-java/java-client/pom.xml | 4 ++--
 rpc/triple/pb/dubbogo-java/java-server/pom.xml | 4 ++--
 2 files changed, 4 insertions(+), 4 deletions(-)