This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch dependabot/maven/org.apache.ivy-ivy-2.5.3
in repository https://gitbox.apache.org/repos/asf/tika.git
discard f3a734f3f Bump org.apache.ivy:ivy from 2.5.2 to 2.5.3
add 0e3a240d7 TIKA-4327: exclude ffmpeg (again!) until update
add 9b326de50 Bump com.github.luben:zstd-jni from 1.5.6-8 to 1.5.6-9
(#2091)
add d2d233eec Bump org.xerial:sqlite-jdbc from 3.47.1.0 to 3.47.2.0 (#2087)
add d84ae6ab9 Bump com.healthmarketscience.jackcess:jackcess from 4.0.7 to
4.0.8 (#2092)
add c7ca05e7e Bump com.nimbusds:nimbus-jose-jwt from 9.48 to 10.0.1 (#2090)
add 53b48af01 Bump org.apache.ivy:ivy from 2.5.2 to 2.5.3
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 (f3a734f3f)
\
N -- N -- N refs/heads/dependabot/maven/org.apache.ivy-ivy-2.5.3
(53b48af01)
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 | 8 ++++----
tika-parsers/tika-parsers-ml/tika-dl/pom.xml | 3 +++
2 files changed, 7 insertions(+), 4 deletions(-)
