This is an automated email from the ASF dual-hosted git repository.
dependabot[bot] pushed a change to branch
dependabot/npm_and_yarn/superset-frontend/baseline-browser-mapping-2.11.29
in repository https://gitbox.apache.org/repos/asf/superset.git
omit f0801277e2e chore(deps-dev): bump baseline-browser-mapping in
/superset-frontend
add 6d986408f61 chore(deps-dev): bump lerna from 10.0.1 to 10.1.1 in
/superset-frontend (#45715)
add ae9fc20c659 chore(deps): bump sqlalchemy from 2.0.52 to 2.0.55 (#45703)
add a028e65ba3a chore(deps-dev): bump clickhouse-connect from 1.10.1 to
1.11.0 (#45708)
add 3f85ceb15b4 chore(deps-dev): bump duckdb from 1.5.5 to 1.5.6 (#45705)
add 1c288801558 chore(deps-dev): bump baseline-browser-mapping in
/superset-frontend
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 (f0801277e2e)
\
N -- N -- N
refs/heads/dependabot/npm_and_yarn/superset-frontend/baseline-browser-mapping-2.11.29
(1c288801558)
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:
pyproject.toml | 6 +-
requirements/base.txt | 2 +-
requirements/development.txt | 6 +-
superset-frontend/package-lock.json | 3349 +++++++++++++++++------------------
superset-frontend/package.json | 2 +-
5 files changed, 1595 insertions(+), 1770 deletions(-)
