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

github-bot pushed a change to branch dependabot/maven/spring.version-6.2.4
in repository https://gitbox.apache.org/repos/asf/storm.git


 discard a1ba2c053 Update DEPENDENCY-LICENSES
 discard 84466d00b Update DEPENDENCY-LICENSES
 discard bcf3ee224 Bump spring.version from 5.3.27 to 6.2.4
     add 4af86b1e1 Bump curator.version from 5.7.1 to 5.8.0 (#7985)
     add 7635633d1 Bump io.netty:netty-bom from 4.1.118.Final to 4.1.119.Final 
(#7982)
     add dcfab1890 Bump spring.version from 5.3.27 to 6.2.4

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   (a1ba2c053)
            \
             N -- N -- N   refs/heads/dependabot/maven/spring.version-6.2.4 
(dcfab1890)

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:
 DEPENDENCY-LICENSES | 86 ++++++++++++++++++++++++++---------------------------
 LICENSE-binary      | 84 +++++++++++++++++++++++++--------------------------
 pom.xml             |  4 +--
 3 files changed, 87 insertions(+), 87 deletions(-)

Reply via email to