This is an automated email from the ASF dual-hosted git repository.
dependabot[bot] pushed a change to branch
dependabot/maven/com.healthmarketscience.jackcess-jackcess-encrypt-5.0.1
in repository https://gitbox.apache.org/repos/asf/tika.git
omit 73776abff9 Bump com.healthmarketscience.jackcess:jackcess-encrypt
add cb28191626 Bump com.diffplug.spotless:spotless-maven-plugin from
3.10.2 to 3.10.3 (#3288)
add c4a6f2e86a Bump com.google.cloud:google-cloud-storage from 2.74.0 to
2.75.0 (#3295)
add 45c983f52f Bump com.h2database:h2 from 2.5.250 to 2.5.252 (#3293)
add b1321b7437 Bump com.healthmarketscience.jackcess:jackcess from 5.0.0
to 5.0.2 (#3294)
add e43950fbde Bump joda-time:joda-time from 2.14.4 to 2.15.0 (#3292)
add 3aa31a7df2 Bump com.healthmarketscience.jackcess:jackcess-encrypt
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 (73776abff9)
\
N -- N -- N
refs/heads/dependabot/maven/com.healthmarketscience.jackcess-jackcess-encrypt-5.0.1
(3aa31a7df2)
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(-)
