This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/org.springframework-spring-context-7.0.4
in repository https://gitbox.apache.org/repos/asf/tika.git
omit 9391257391 Bump org.springframework:spring-context from 7.0.3 to 7.0.4
add 9b775e6568 Bump org.xerial:sqlite-jdbc from 3.51.1.0 to 3.51.2.0
(#2607)
add 0dee7db5de Bump software.amazon.awssdk:bom from 2.41.28 to 2.41.29
(#2609)
add eb065261a4 Bump org.springframework:spring-context from 7.0.3 to 7.0.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 (9391257391)
\
N -- N -- N
refs/heads/dependabot/maven/org.springframework-spring-context-7.0.4
(eb065261a4)
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:
tika-parent/pom.xml | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
