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.18.0
in repository https://gitbox.apache.org/repos/asf/tika.git
omit 4db068d96 Bump google-cloud-storage from 2.17.2 to 2.18.0
add 2b5ea26f6 Bump maven-model from 3.8.7 to 3.9.0
add c93f65c91 Merge pull request #947 from
apache/dependabot/maven/org.apache.maven-maven-model-3.9.0
add 553e3a694 Bump aws.version from 1.12.400 to 1.12.401
add 72c457b52 Merge pull request #946 from
apache/dependabot/maven/aws.version-1.12.401
add e3037eb72 Bump google-cloud-storage from 2.17.2 to 2.18.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 (4db068d96)
\
N -- N -- N
refs/heads/dependabot/maven/com.google.cloud-google-cloud-storage-2.18.0
(e3037eb72)
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 | 2 +-
tika-parsers/tika-parsers-ml/tika-parser-nlp-module/pom.xml | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
