This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/npm_and_yarn/zeppelin-web-angular/async-2.6.4
in repository https://gitbox.apache.org/repos/asf/zeppelin.git
omit 5a61b6b703 Bump async from 2.6.3 to 2.6.4 in /zeppelin-web-angular
add e137fc074d Bump moment from 2.22.2 to 2.29.2 in /zeppelin-web (#4346)
add 5bbefdba4e MINOR Fix typo and change some fields of PR template (#4359)
add 96148c16b1 MINOR Cache .spark-dist for Github actions (#4358)
add 58a0e34c4f MINOR Update asf.yaml to link with JIRA (#4357)
add 891cdea00a Bump hadoop-common from 2.3.0 to 3.2.3 in /beam (#4350)
add a4f299d67f Bump async from 2.6.3 to 2.6.4 in /zeppelin-web-angular
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 (5a61b6b703)
\
N -- N -- N
refs/heads/dependabot/npm_and_yarn/zeppelin-web-angular/async-2.6.4 (a4f299d67f)
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:
.asf.yaml | 8 +-
.github/PULL_REQUEST_TEMPLATE | 10 ++-
.github/workflows/core.yml | 16 ++++
.github/workflows/frontend.yml | 6 ++
beam/pom.xml | 2 +-
zeppelin-web/package-lock.json | 185 +++++++++--------------------------------
zeppelin-web/package.json | 2 +-
7 files changed, 80 insertions(+), 149 deletions(-)
