This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/io.projectreactor-reactor-core-3.8.0-M3
in repository https://gitbox.apache.org/repos/asf/tika.git
discard 215efd00d Bump io.projectreactor:reactor-core from 3.8.0-M2 to 3.8.0-M3
add 2870f80a4 Bump org.jetbrains.kotlin:kotlin-stdlib from 2.1.20 to
2.1.21 (#2213)
add ca83e8068 Bump com.azure:azure-identity from 1.16.0 to 1.16.1 (#2212)
add d7565c5c1 Bump com.microsoft.graph:microsoft-graph from 6.37.0 to
6.38.0 (#2211)
add 280a78f72 Bump org.jline:jline from 3.30.0 to 3.30.1 (#2210)
add 5fe082501 Bump reactor.netty.version from 1.3.0-M2 to 1.3.0-M3 (#2209)
add 90bb24f0c Bump junit5.version from 5.13.0-M3 to 5.13.0-RC1 (#2207)
add 3d82a85d7 Bump io.projectreactor:reactor-core from 3.8.0-M2 to 3.8.0-M3
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 (215efd00d)
\
N -- N -- N
refs/heads/dependabot/maven/io.projectreactor-reactor-core-3.8.0-M3 (3d82a85d7)
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 | 6 +++---
tika-parsers/tika-parsers-ml/tika-age-recogniser/pom.xml | 2 +-
tika-pipes/tika-fetchers/tika-fetcher-microsoft-graph/pom.xml | 4 ++--
3 files changed, 6 insertions(+), 6 deletions(-)
