This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/bigquery/com.google.guava-guava-29.0-jre
in repository https://gitbox.apache.org/repos/asf/zeppelin.git
discard ce654bb375 Bump guava from 24.1.1-jre to 29.0-jre in /bigquery
add b8913a1ec3 update livy archive name (#4470)
add bf5c66672a [ZEPPELIN-5829] upgrade gson to 2.8.9 due to CVE-2022-25647
(#4476)
add 561bb35ba6 Bump guava from 24.1.1-jre to 29.0-jre in /bigquery
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 (ce654bb375)
\
N -- N -- N
refs/heads/dependabot/maven/bigquery/com.google.guava-guava-29.0-jre
(561bb35ba6)
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:
bigquery/pom.xml | 1 -
influxdb/pom.xml | 3 +-
pom.xml | 2 +-
shell/pom.xml | 1 -
testing/downloadLivy.sh | 2 +-
zeppelin-distribution/src/bin_license/LICENSE | 2 +-
.../src/bin_license/licenses/LICENSE-gson-2.2 | 203 ---------------------
...ENSE-azure-storage-4.0.0 => LICENSE-gson-2.8.9} | 0
zeppelin-integration/pom.xml | 2 +-
9 files changed, 5 insertions(+), 211 deletions(-)
delete mode 100644
zeppelin-distribution/src/bin_license/licenses/LICENSE-gson-2.2
copy
zeppelin-distribution/src/bin_license/licenses/{LICENSE-azure-storage-4.0.0 =>
LICENSE-gson-2.8.9} (100%)
