This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/com.azure-azure-storage-common-12.28.1
in repository https://gitbox.apache.org/repos/asf/tika.git
discard 74cf16af1 Bump com.azure:azure-storage-common from 12.28.0 to 12.28.1
add 8ab05f715 Bump org.testcontainers:testcontainers-bom from 1.20.5 to
1.20.6 (#2153)
add bf7f9df2b Bump org.mockito:mockito-junit-jupiter from 5.15.2 to 5.16.0
(#2162)
add eb41d8692 Bump net.bytebuddy:byte-buddy from 1.17.1 to 1.17.2 (#2155)
add e39d6a945 Bump com.azure:azure-storage-blob from 12.29.0 to 12.29.1
(#2160)
add 8f25a8fc6 Bump com.azure:azure-json from 1.4.0 to 1.5.0 (#2159)
add 538e37d53 Bump curator.version from 5.7.1 to 5.8.0 (#2161)
add 9fb0ddf14 Bump com.thoughtworks.paranamer:paranamer from 2.8.1 to
2.8.2 (#2158)
add 244c65641 Bump com.azure:azure-storage-common from 12.28.0 to 12.28.1
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 (74cf16af1)
\
N -- N -- N
refs/heads/dependabot/maven/com.azure-azure-storage-common-12.28.1 (244c65641)
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-age-recogniser/pom.xml | 6 +++---
2 files changed, 7 insertions(+), 7 deletions(-)
