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-blob-12.29.0
in repository https://gitbox.apache.org/repos/asf/tika.git
discard 6008236aa Bump com.azure:azure-storage-blob from 12.28.1 to 12.29.0
add 0a398bdf7 Bump com.azure:azure-storage-common from 12.27.1 to 12.28.0
(#2055)
add 635a9a809 Bump com.azure:azure-core from 1.54.0 to 1.54.1 (#2052)
add a6e488d25 Bump com.nimbusds:nimbus-jose-jwt from 9.46 to 9.47 (#2050)
add d691366da Bump com.azure:azure-storage-blob from 12.28.1 to 12.29.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 (6008236aa)
\
N -- N -- N
refs/heads/dependabot/maven/com.azure-azure-storage-blob-12.29.0 (d691366da)
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 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
