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

github-bot pushed a change to branch 
dependabot/gradle/com.alibaba.fastjson2-fastjson2-2.0.50
in repository https://gitbox.apache.org/repos/asf/eventmesh.git


 discard ef1bd658d Bump com.alibaba.fastjson2:fastjson2 from 2.0.48 to 2.0.50
     add 6e741bf78 Bump com.alibaba.nacos:nacos-client from 2.2.3 to 2.3.2 
(#4922)
     add 29153722f Bump org.antlr:antlr4-runtime from 4.13.0 to 4.13.1 (#4923)
     add 7c70e95f9 Bump com.github.spotbugs.snom:spotbugs-gradle-plugin (#4914)
     add 1f35151ff Bump com.rabbitmq:amqp-client from 5.16.0 to 5.21.0 (#4917)
     add ed425922f Bump org.projectlombok:lombok from 1.18.22 to 1.18.32 (#4920)
     add 5ee681936 Bump com.alibaba.fastjson2:fastjson2 from 2.0.48 to 2.0.50

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   (ef1bd658d)
            \
             N -- N -- N   
refs/heads/dependabot/gradle/com.alibaba.fastjson2-fastjson2-2.0.50 (5ee681936)

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:
 build.gradle                                                     | 6 +++---
 eventmesh-connectors/eventmesh-connector-jdbc/build.gradle       | 2 +-
 eventmesh-connectors/eventmesh-connector-rabbitmq/build.gradle   | 2 +-
 eventmesh-storage-plugin/eventmesh-storage-rabbitmq/build.gradle | 4 ++--
 4 files changed, 7 insertions(+), 7 deletions(-)


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to