This is an automated email from the ASF dual-hosted git repository.
alexstocks pushed a change to branch develop
in repository https://gitbox.apache.org/repos/asf/dubbo-go.git.
omit 4a721a2 Merge pull request #999 from
apache/dependabot/go_modules/develop/github.com/alibaba/sentinel-golang-1.0.2
omit 982e74c Merge pull request #1001 from
apache/dependabot/go_modules/develop/github.com/stretchr/testify-1.7.0
omit aaacf31 Bump github.com/stretchr/testify from 1.6.1 to 1.7.0
omit 7dd17b3 Bump github.com/alibaba/sentinel-golang from 1.0.1 to 1.0.2
omit 5cb723a update hessian2 version to v1.8.2
new 016bcce update hessian2 version to v1.8.2
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 (4a721a2)
\
N -- N -- N refs/heads/develop (016bcce)
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.
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
go.mod | 6 ++++--
go.sum | 6 ++----
2 files changed, 6 insertions(+), 6 deletions(-)
