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

github-bot pushed a change to branch 
dependabot/go_modules/3.0/github.com/dubbogo/triple-1.1.5
in repository https://gitbox.apache.org/repos/asf/dubbo-go.git.


 discard bc06d77  build(deps): bump github.com/dubbogo/triple from 1.1.3 to 
1.1.5
     add 19c0bb9  refactor listenDirEvent 1. remove CLEAR label; 2. remove 
register/unregister logic for watch children; 3. reorder the zk dynamic 
configuration code 4. adapt the gost
     add 4d780a9  upgrade gost dependency version
     add a812919  Merge pull request #1589 from Mulavar/3.0
     add dd251e8  build(deps): bump github.com/dubbogo/triple from 1.1.3 to 
1.1.5

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   (bc06d77)
            \
             N -- N -- N   
refs/heads/dependabot/go_modules/3.0/github.com/dubbogo/triple-1.1.5 (dd251e8)

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:
 config_center/zookeeper/impl.go | 12 ++++++++---
 go.mod                          |  2 +-
 go.sum                          |  4 ++--
 registry/zookeeper/registry.go  | 11 +++++++---
 remoting/zookeeper/listener.go  | 48 ++++++++++++-----------------------------
 5 files changed, 34 insertions(+), 43 deletions(-)

Reply via email to