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.0
in repository https://gitbox.apache.org/repos/asf/tika.git
discard 9d11b2383 Bump com.azure:azure-storage-common from 12.27.1 to 12.28.0
add 522d70ff2 Bump aws.version from 1.12.777 to 1.12.778 (#2049)
add 63d6263a5 Bump org.netpreserve:jwarc from 0.30.0 to 0.31.0 (#2058)
add cc328edd3 Bump com.azure:azure-identity from 1.14.1 to 1.14.2 (#2057)
add f49a70fdb Bump com.azure:azure-core-http-netty from 1.15.6 to 1.15.7
(#2056)
add 14343fa26 Bump javacpp.version from 1.5.10 to 1.5.11 (#2047)
add 57b74d257 Bump com.azure:azure-storage-common from 12.27.1 to 12.28.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 (9d11b2383)
\
N -- N -- N
refs/heads/dependabot/maven/com.azure-azure-storage-common-12.28.0 (57b74d257)
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 | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
