This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/io.micronaut-micronaut-http-server-4.10.16
in repository https://gitbox.apache.org/repos/asf/tika.git
discard 51d5104cf1 Bump io.micronaut:micronaut-http-server from 3.10.4 to
4.10.16
add 2a9957a12b Bump org.tukaani:xz from 1.11 to 1.12 (#2670)
add 0385b58466 Bump io.swagger.core.v3:swagger-annotations from 2.2.38 to
2.2.43 (#2669)
add 1d46c8b97f Bump org.jetbrains.kotlin:kotlin-stdlib from 2.2.0 to
2.3.10 (#2663)
add aaef3ca7a3 Bump info.picocli:picocli from 4.7.5 to 4.7.7 (#2661)
add b9903d0840 Bump org.jetbrains:annotations from 26.0.2-1 to 26.1.0
(#2659)
add 4ba11a4e19 Bump org.yaml:snakeyaml from 2.4 to 2.6 (#2671)
add 4c9017fca3 Bump jakarta.inject:jakarta.inject-api from 2.0.1 to
2.0.1.MR (#2667)
add 93b5cfa96f TIKA-4488: update micronaut
add 3e88d4e259 Bump io.micronaut:micronaut-http-server from 3.10.4 to
4.10.16
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 (51d5104cf1)
\
N -- N -- N
refs/heads/dependabot/maven/io.micronaut-micronaut-http-server-4.10.16
(3e88d4e259)
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 | 31 +++++++++++++----------
tika-pipes/tika-pipes-config-store-ignite/pom.xml | 26 +++++++++----------
2 files changed, 31 insertions(+), 26 deletions(-)
