This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/npm_and_yarn/docs/docusaurus/preset-classic-3.9.2
in repository https://gitbox.apache.org/repos/asf/superset.git
discard f6be1d406b chore(deps): bump @docusaurus/preset-classic in /docs
add fa90ba976c fix: Extension events not fired in SQL Lab tabs (#35753)
add 4974c08f7d chore(deps): bump @docusaurus/theme-mermaid from 3.9.1 to
3.9.2 in /docs (#35741)
add 6af09c45a2 chore(deps): bump @docusaurus/preset-classic in /docs
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 (f6be1d406b)
\
N -- N -- N
refs/heads/dependabot/npm_and_yarn/docs/docusaurus/preset-classic-3.9.2
(6af09c45a2)
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 | 2 +-
docs/yarn.lock | 263 ++---------------------------
superset-frontend/src/core/sqlLab/index.ts | 6 +-
3 files changed, 12 insertions(+), 259 deletions(-)
