This is an automated email from the ASF dual-hosted git repository.
dependabot[bot] pushed a change to branch
dependabot/maven/com.google.cloud-google-cloud-storage-2.77.0
in repository https://gitbox.apache.org/repos/asf/tika.git
discard 7765271f44 Bump com.google.cloud:google-cloud-storage from 2.76.0 to
2.77.0
add 919768aeab Bump com.google.api.grpc:proto-google-common-protos (#3587)
add 54ba4ac904 Bump com.google.guava:guava from 33.7.2-jre to 33.8.0-jre
(#3584)
add 5f0853c827 Bump org.pf4j:pf4j from 3.16.0 to 3.16.1 (#3579)
add 888ae699b9 Bump software.amazon.awssdk:bom from 2.57.7 to 2.57.10
(#3588)
add aee6708f8f Bump org.jsoup:jsoup from 1.23.2 to 1.24.1 (#3578)
add 2eb9cb9e7b Bump eu.maveniverse.maven.nisse:extension from 0.9.11 to
0.9.12 (#3577)
add 8f872e98b5 Bump com.google.errorprone:error_prone_annotations from
2.51.0 to 2.52.0 (#3582)
add 94ce8f955f Bump google-auth-library-oauth2-http.version from 1.55.0 to
1.56.0 (#3576)
add 56201a7c46 Bump com.google.cloud:google-cloud-storage from 2.76.0 to
2.77.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 (7765271f44)
\
N -- N -- N
refs/heads/dependabot/maven/com.google.cloud-google-cloud-storage-2.77.0
(56201a7c46)
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:
.mvn/extensions.xml | 2 +-
tika-grpc/pom.xml | 2 +-
tika-parent/pom.xml | 10 +++++-----
tika-pipes/tika-pipes-plugins/tika-pipes-google-drive/pom.xml | 2 +-
4 files changed, 8 insertions(+), 8 deletions(-)
