[zeppelin] branch dependabot/npm_and_yarn/zeppelin-web/grunt-1.5.3 updated (2989dfac56 -> 9076c62fb8)

[gi...@apache.org]

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/grunt-1.5.3
in repository https://gitbox.apache.org/repos/asf/zeppelin.git


    omit 2989dfac56 Bump grunt from 0.4.5 to 1.5.3 in /zeppelin-web
     add 0761df530d [ZEPPELIN-3945] Create .gitattributes (#4409)
     add 65dcdb8148 [ZEPPELIN-5761] Support flink 1.15.1 (#4404)
     add 25c9a36b16 Bump aws-java-sdk-s3 in /zeppelin-plugins/notebookrepo/s3 (#4413)
     add 6941a5f342 Bump kubernetes-client in /zeppelin-plugins/launcher/k8s-standard (#4411)
     add 9076c62fb8 Bump grunt from 0.4.5 to 1.5.3 in /zeppelin-web

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   (2989dfac56)
            \
             N -- N -- N   refs/heads/dependabot/npm_and_yarn/zeppelin-web/grunt-1.5.3 (9076c62fb8)

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:
 .gitattributes                                 | 1 +
 flink/pom.xml                                  | 2 +-
 testing/env_python_3_with_flink_115.yml        | 2 +-
 zeppelin-plugins/launcher/k8s-standard/pom.xml | 2 +-
 zeppelin-plugins/notebookrepo/s3/pom.xml       | 2 +-
 5 files changed, 5 insertions(+), 4 deletions(-)
 create mode 100644 .gitattributes