This is an automated email from the ASF dual-hosted git repository.
dependabot[bot] pushed a change to branch
dependabot/npm_and_yarn/ui/multi-74278cf740
in repository https://gitbox.apache.org/repos/asf/skywalking-banyandb.git
omit 386034685 chore(deps): bump esbuild, @vitejs/plugin-vue and vite in /ui
add 9630914ae chore(mcp,ui): bump npm dependencies and update CI actions
(#1175)
add cec0f9bdb chore(deps): bump esbuild, @vitejs/plugin-vue and vite in /ui
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 (386034685)
\
N -- N -- N
refs/heads/dependabot/npm_and_yarn/ui/multi-74278cf740 (cec0f9bdb)
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/actions/setup-build-env/action.yml | 18 +-
.github/workflows/e2e.yml | 2 +-
.github/workflows/prepare.yml | 4 +-
.github/workflows/publish-docker.yml | 2 +-
dist/LICENSE | 81 ++--
... license-type-is-node-modules-content-type.txt} | 0
go.mod | 2 +-
mcp/.gitignore | 2 +-
mcp/.licenserc.yaml | 1 +
mcp/LICENSE | 17 +-
mcp/package-lock.json | 513 +++++++++++----------
ui/LICENSE | 64 +--
ui/package-lock.json | 350 +++++++-------
13 files changed, 543 insertions(+), 513 deletions(-)
copy dist/licenses/mcp-licenses/{license-content-type.txt =>
license-type-is-node-modules-content-type.txt} (100%)
