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

dependabot[bot] pushed a change to branch 
dependabot/maven/org.springframework-spring-context-7.0.9
in repository https://gitbox.apache.org/repos/asf/tika.git


    omit dfc59d59a6 Bump org.springframework:spring-context from 7.0.8 to 7.0.9
     add e81276a242 Bump com.diffplug.spotless:spotless-maven-plugin from 3.9.0 
to 3.10.0 (#3057)
     add caedaa3c46 Bump io.projectreactor:reactor-core from 3.8.6 to 3.8.7 
(#3052)
     add f4dc4a8d41 Bump io.swagger.core.v3:swagger-annotations from 2.2.53 to 
2.2.54 (#3056)
     add 59091c2a7b Bump software.amazon.awssdk:bom from 2.53.1 to 2.54.1 
(#3061)
     add 0e8ca052e4 Bump jackson.version from 2.22.1 to 2.22.2 (#3049)
     add 45b64e42ce Bump eu.maveniverse.maven.nisse:extension from 0.9.5 to 
0.9.7 (#3059)
     add bb391ca9ff Bump com.github.luben:zstd-jni from 1.5.7-13 to 1.5.7-15 
(#3058)
     add b484cbbe10 Bump org.codehaus.plexus:plexus-utils from 4.0.3 to 4.1.0 
(#3055)
     add 6b620caf75 Bump org.springframework:spring-context from 7.0.8 to 7.0.9

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   (dfc59d59a6)
            \
             N -- N -- N   
refs/heads/dependabot/maven/org.springframework-spring-context-7.0.9 
(6b620caf75)

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:
 .mvn/extensions.xml |  2 +-
 tika-parent/pom.xml | 14 +++++++-------
 2 files changed, 8 insertions(+), 8 deletions(-)

Reply via email to