This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/com.azure-azure-core-1.52.0
in repository https://gitbox.apache.org/repos/asf/tika.git
discard c9d4e0243 Bump com.azure:azure-core from 1.51.0 to 1.52.0
add b83d66a52 Bump aws.version from 1.12.771 to 1.12.772 (#1953)
add d5818ce1f Bump io.projectreactor:reactor-core from 3.6.9 to 3.6.10
(#1955)
add 128bd9bca Bump net.java.dev.jna:jna from 5.14.0 to 5.15.0 (#1951)
add ecfaac09c Bump com.azure:azure-core-http-netty from 1.15.3 to 1.15.4
(#1949)
add 35ee74342 Bump org.xerial.snappy:snappy-java from 1.1.10.6 to 1.1.10.7
(#1950)
add 754c9005b Bump joda-time:joda-time from 2.12.7 to 2.13.0 (#1952)
add 8db0fc7c7 Bump com.azure:azure-core from 1.51.0 to 1.52.0
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 (c9d4e0243)
\
N -- N -- N
refs/heads/dependabot/maven/com.azure-azure-core-1.52.0 (8db0fc7c7)
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 | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
