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/multi-b069860f50
in repository https://gitbox.apache.org/repos/asf/zeppelin.git
discard 0c3d332cd5 Bump @tootallnate/once, @angular-eslint/schematics and
@angular/cli
add aaa52286a3 [ZEPPELIN-6402] Update copyright year to 2026 in NOTICE file
add 08fa86aeab [ZEPPELIN-6401] Resolve all npm audit vulnerabilities in
zeppelin-react
add 1be5c3e704 [ZEPPELIN-6397] Bump Testcontainers version to 1.21.4
add 85a45dcd64 Bump @tootallnate/once, @angular-eslint/schematics and
@angular/cli
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 (0c3d332cd5)
\
N -- N -- N
refs/heads/dependabot/npm_and_yarn/zeppelin-web-angular/multi-b069860f50
(85a45dcd64)
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:
.github/workflows/frontend.yml | 14 +
NOTICE | 2 +-
pom.xml | 2 +-
zeppelin-web-angular/package-lock.json | 48 +-
.../projects/zeppelin-react/package-lock.json | 2595 +++++++++++---------
.../projects/zeppelin-react/package.json | 9 +-
.../zeppelin-react/src/utils/exportFile.ts | 2 +-
7 files changed, 1448 insertions(+), 1224 deletions(-)
