This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/com.google.cloud-google-cloud-storage-2.62.1
in repository https://gitbox.apache.org/repos/asf/tika.git
discard afca0dbeb8 Bump com.google.cloud:google-cloud-storage from 2.62.0 to
2.62.1
add a399aa03af Bump com.azure:azure-sdk-bom from 1.3.3 to 1.3.4 (#2576)
add 26fc000596 Bump commons-codec:commons-codec from 1.20.0 to 1.21.0
(#2574)
add b8f4b1a336 Bump software.amazon.awssdk:bom from 2.41.14 to 2.41.19
(#2571)
add 9edac076c8 Bump com.diffplug.spotless:spotless-maven-plugin from 3.2.0
to 3.2.1 (#2570)
add 16d2c76818 Bump org.apache.maven.plugins:maven-compiler-plugin (#2572)
add bcf1495adf Bump com.google.cloud:google-cloud-storage from 2.62.0 to
2.62.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 (afca0dbeb8)
\
N -- N -- N
refs/heads/dependabot/maven/com.google.cloud-google-cloud-storage-2.62.1
(bcf1495adf)
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(-)
