This is an automated email from the ASF dual-hosted git repository.

github-bot pushed a change to branch 
dependabot/npm_and_yarn/superset-frontend/packages/superset-ui-demo/react-19.2.4
in repository https://gitbox.apache.org/repos/asf/superset.git


 discard 99a72ec98e0 chore(deps): bump react in 
/superset-frontend/packages/superset-ui-demo
     add fea135b46ca chore(deps-dev): bump @playwright/test from 1.58.0 to 
1.58.1 in /superset-frontend (#37633)
     add 568486a3048 chore(deps): bump @babel/core from 7.28.6 to 7.29.0 in 
/docs (#37598)
     add 7112bce961b chore(deps-dev): bump @types/node from 25.1.0 to 25.2.0 in 
/superset-websocket (#37597)
     add a44980da65a chore(deps-dev): bump globals from 17.2.0 to 17.3.0 in 
/superset-websocket (#37595)
     add 3eb860a6635 chore(deps): bump hot-shots from 13.1.0 to 13.2.0 in 
/superset-websocket (#37596)
     add 66264856a7f chore(deps): bump googleapis from 171.0.0 to 171.1.0 in 
/superset-frontend (#37630)
     add 569606635b0 docs(databases): add Supabase, AlloyDB, and Neon as 
PostgreSQL-compatible databases (#37589)
     add 76889c1a696 feat(db_engine_specs): add Apache Phoenix and Apache IoTDB 
engine specs (#37590)
     add 5ac5480f359 chore(deps): bump caniuse-lite from 1.0.30001766 to 
1.0.30001767 in /docs (#37601)
     add 3728bcbbbd7 chore(deps): bump react in 
/superset-frontend/packages/superset-ui-demo

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   (99a72ec98e0)
            \
             N -- N -- N   
refs/heads/dependabot/npm_and_yarn/superset-frontend/packages/superset-ui-demo/react-19.2.4
 (3728bcbbbd7)

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:
 docs/package.json                            |   4 +-
 docs/static/img/databases/alloydb.png        | Bin 0 -> 88097 bytes
 docs/static/img/databases/apache-iotdb.svg   | Bin 0 -> 4646 bytes
 docs/static/img/databases/apache-phoenix.png | Bin 0 -> 29188 bytes
 docs/static/img/databases/neon.png           | Bin 0 -> 20140 bytes
 docs/static/img/databases/supabase.svg       | Bin 0 -> 5817 bytes
 docs/yarn.lock                               |  80 ++++++++++-----------
 superset-frontend/package-lock.json          |  32 ++++-----
 superset-frontend/package.json               |   4 +-
 superset-websocket/package-lock.json         |  42 +++++------
 superset-websocket/package.json              |   6 +-
 superset/db_engine_specs/iotdb.py            |  59 ++++++++++++++++
 superset/db_engine_specs/phoenix.py          |  86 +++++++++++++++++++++++
 superset/db_engine_specs/postgres.py         | 101 +++++++++++++++++++++++++++
 14 files changed, 330 insertions(+), 84 deletions(-)
 create mode 100644 docs/static/img/databases/alloydb.png
 create mode 100644 docs/static/img/databases/apache-iotdb.svg
 create mode 100644 docs/static/img/databases/apache-phoenix.png
 create mode 100644 docs/static/img/databases/neon.png
 create mode 100644 docs/static/img/databases/supabase.svg
 create mode 100644 superset/db_engine_specs/iotdb.py
 create mode 100644 superset/db_engine_specs/phoenix.py

Reply via email to