This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/hugegraph-hubble/hubble-be/commons-fileupload-commons-fileupload-1.5
in repository
https://gitbox.apache.org/repos/asf/incubator-hugegraph-toolchain.git
omit e6fca5bc chore(deps): bump commons-fileupload in
/hugegraph-hubble/hubble-be
add 11ee775b chore(hubble): use latest code in Dockerfile (#440)
add 4c524014 Update pom.xml (#443)
add 3945e10e chore(deps): bump commons-fileupload in
/hugegraph-hubble/hubble-be
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 (e6fca5bc)
\
N -- N -- N
refs/heads/dependabot/maven/hugegraph-hubble/hubble-be/commons-fileupload-commons-fileupload-1.5
(3945e10e)
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:
README.md | 4 +-
hugegraph-hubble/Dockerfile | 32 ++++++----
hugegraph-hubble/README.md | 10 ++-
.../assembly/static/bin/start-hubble.sh | 71 +++++++++++-----------
hugegraph-hubble/hubble-dist/pom.xml | 58 ------------------
5 files changed, 62 insertions(+), 113 deletions(-)
