fix(pre-commit): exclude lockfiles from oxfmt-frontend to avoid hard-erroring on lockfile-only diffs

The oxfmt-frontend hook's `files:` regex matches `.json`, which includes
package-lock.json. oxfmt itself internally treats lockfiles as generated
files and filters them out of its target list, so when a diff touches
only a lockfile, pre-commit hands oxfmt a target list that resolves to
zero real files. Unlike prettier (which no-ops cleanly on an empty
target set), oxfmt hard-errors with "Expected at least one target
file. All matched files may have been excluded by ignore rules." and
exits 2.

This masqueraded as a red CI check on any lockfile-only PR, most
immediately dependabot bump #42718, and will recur on every future
lockfile-only dependency bump until fixed on master.

Add an `exclude:` pattern for package-lock.json, yarn.lock, and
pnpm-lock.yaml so pre-commit never hands oxfmt a target set doomed to
be empty. Real frontend source files are unaffected - verified with
`pre-commit run oxfmt-frontend --files <path>` against a lockfile-only
target (now skips cleanly), a real .ts file (still formats), and a
mixed lockfile + real file target (still formats the real file).

Co-Authored-By: Claude <noreply@anthropic.com>

.cursor/rules/dev-standard.mdc

@@ -105,9 +105,9 @@ Charts built from enriched datasets containing:
 pre-commit install
 
 # Quick validation (faster than --all-files)
-pre-commit run                    # Staged files only
+pre-commit run                   # Staged files only
 pre-commit run mypy              # Python type checking
-pre-commit run prettier          # Code formatting
+pre-commit run format            # Code formatting
 pre-commit run eslint            # Frontend linting
 ```
 

.devcontainer/devcontainer-base.json

@@ -32,7 +32,6 @@
         "ms-python.vscode-pylance",
         "charliermarsh.ruff",
         "dbaeumer.vscode-eslint",
-        "esbenp.prettier-vscode"
       ]
     }
   }

.devcontainer/devcontainer.json

@@ -59,7 +59,6 @@
         "ms-python.vscode-pylance",
         "charliermarsh.ruff",
         "dbaeumer.vscode-eslint",
-        "esbenp.prettier-vscode"
       ]
     }
   }

.github/workflows/bashlib.sh

@@ -256,7 +256,7 @@ cypress-run-all() {
   # UNCOMMENT the next few commands to monitor memory usage
   # monitor_memory &  # Start memory monitoring in the background
   # memoryMonitorPid=$!
-  python ../../scripts/cypress_run.py --parallelism $PARALLELISM --parallelism-id $PARALLEL_ID --group $PARALLEL_ID --retries 5 $USE_DASHBOARD_FLAG
+  python ../../scripts/cypress_run.py --retries 5 $USE_DASHBOARD_FLAG
   # kill $memoryMonitorPid
 }
 

.github/workflows/bump-python-package.yml

@@ -23,7 +23,7 @@ on:
 
 jobs:
   bump-python-package:
-    runs-on: ubuntu-26.04
+    runs-on: ubuntu-slim
     permissions:
       actions: write
       contents: write

.github/workflows/check-db-migration-confict.yml

@@ -19,7 +19,7 @@ concurrency:
 jobs:
   check_db_migration_conflict:
     name: Check DB migration conflict
-    runs-on: ubuntu-26.04
+    runs-on: ubuntu-slim
     permissions:
       contents: read
       pull-requests: write

.github/workflows/check-python-deps.yml

@@ -11,6 +11,7 @@ on:
 permissions:
   contents: read
   pull-requests: read
+  actions: read
 
 # cancel previous workflow jobs for PRs
 concurrency:
@@ -21,6 +22,10 @@ jobs:
   check-python-deps:
     runs-on: ubuntu-26.04
     steps:
+      - uses: Kesin11/actions-timeline@7bf79990b7c09f5dfb570ac30b814ca597bd538e # v3.1.1
+        with:
+          expand-composite-actions: true
+
       - name: "Checkout ${{ github.ref }} ( ${{ github.sha }} )"
         uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
         with:
@@ -46,7 +51,7 @@ jobs:
       - name: Login to Docker Hub
         if: steps.check.outputs.python
         continue-on-error: true
-        uses: docker/login-action@abd2ef45e78c5afb21d64d4ca52ee8550d9572c7 # v4.5.1
+        uses: docker/login-action@371161bbe7024a29a25c5e19bfcbc0804fe9ad2c # v4.5.2
         with:
           username: ${{ secrets.DOCKERHUB_USER }}
           password: ${{ secrets.DOCKERHUB_TOKEN }}

.github/workflows/dependency-review.yml

@@ -20,11 +20,12 @@ concurrency:
 
 permissions:
   contents: read
+  actions: read
 
 jobs:
   dependency-review:
     if: github.event_name == 'pull_request'
-    runs-on: ubuntu-26.04
+    runs-on: ubuntu-slim
     steps:
       - name: "Checkout Repository"
         uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
@@ -47,8 +48,12 @@ jobs:
   python-dependency-liccheck:
     # NOTE: Configuration for liccheck lives in our pyproject.yml.
     # You cannot use a liccheck.ini file in this workflow.
-    runs-on: ubuntu-26.04
+    runs-on: ubuntu-slim
     steps:
+      - uses: Kesin11/actions-timeline@7bf79990b7c09f5dfb570ac30b814ca597bd538e # v3.1.1
+        with:
+          expand-composite-actions: true
+
       - name: "Checkout Repository"
         uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
         with:

.github/workflows/docker.yml

@@ -40,7 +40,7 @@ jobs:
           token: ${{ secrets.GITHUB_TOKEN }}
 
   setup_matrix:
-    runs-on: ubuntu-26.04
+    runs-on: ubuntu-slim
     timeout-minutes: 5
     outputs:
       matrix_config: ${{ steps.set_matrix.outputs.matrix_config }}
@@ -213,3 +213,14 @@ jobs:
         shell: bash
         run: |
           docker compose -f docker-compose-image-tag.yml up superset-init --exit-code-from superset-init
+
+  actions-timeline:
+    needs: [docker-build, docker-compose-image-tag]
+    if: always()
+    runs-on: ubuntu-26.04
+    permissions:
+      actions: read
+    steps:
+      - uses: Kesin11/actions-timeline@7bf79990b7c09f5dfb570ac30b814ca597bd538e # v3.1.1
+        with:
+          expand-composite-actions: true

.github/workflows/embedded-sdk-release.yml

@@ -15,7 +15,7 @@ jobs:
     # gate on. Restrict to the canonical repo: forks cannot mint a valid OIDC
     # token for this package and must not publish.
     if: github.repository == 'apache/superset'
-    runs-on: ubuntu-26.04
+    runs-on: ubuntu-slim
     permissions:
       contents: read
       id-token: write # required for npm trusted publishing (OIDC)

.github/workflows/embedded-sdk-test.yml

@@ -16,7 +16,7 @@ concurrency:
 
 jobs:
   embedded-sdk-test:
-    runs-on: ubuntu-26.04
+    runs-on: ubuntu-slim
     defaults:
       run:
         working-directory: superset-embedded-sdk

.github/workflows/generate-FOSSA-report.yml

@@ -11,7 +11,7 @@ permissions:
 
 jobs:
   config:
-    runs-on: ubuntu-26.04
+    runs-on: ubuntu-slim
     outputs:
       has-secrets: ${{ steps.check.outputs.has-secrets }}
     steps:
@@ -29,7 +29,7 @@ jobs:
     needs: config
     if: needs.config.outputs.has-secrets
     name: Generate Report
-    runs-on: ubuntu-26.04
+    runs-on: ubuntu-slim
     steps:
       - name: "Checkout ${{ github.ref }} ( ${{ github.sha }} )"
         uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1

.github/workflows/issue-creation.yml

@@ -9,7 +9,7 @@ on:
 
 jobs:
   superbot-orglabel:
-    runs-on: ubuntu-26.04
+    runs-on: ubuntu-slim
     permissions:
       contents: read
       pull-requests: write

.github/workflows/label-merge-conflicts.yml

@@ -0,0 +1,54 @@
+name: Label Merge Conflicts
+
+# Sweeps every open PR and labels the ones GitHub reports as CONFLICTING with
+# `requires:rebase` (removing it once a rebase makes the PR mergeable again),
+# so the label can be used to filter the PR backlog for the ones that need a
+# rebase before they can be reviewed/merged.
+#
+# The action itself always re-checks *every* open PR via GraphQL on each run
+# regardless of what triggered it (see eps1lon/actions-label-merge-conflict's
+# sources/main.ts) - there's no way to scope it to "just this PR". The
+# project's own README suggests triggering on `push` (to the default branch)
+# plus `pull_request_target: [synchronize]`, but on a repo with Superset's PR
+# volume that combination would re-sweep the entire open-PR list on every
+# merge to master *and* every push to *any* open PR - many times an hour.
+# A schedule bounds that to a fixed, predictable cadence instead; adjust it
+# if 2 hours turns out to be too slow or too chatty in practice.
+on:
+  schedule:
+    - cron: "0 */2 * * *"
+  workflow_dispatch:
+
+# Avoid two full backlog sweeps racing (a manual workflow_dispatch landing
+# mid-schedule-tick, say); queue rather than cancel so an in-progress
+# paginated sweep always runs to completion.
+concurrency:
+  group: ${{ github.workflow }}
+  cancel-in-progress: false
+
+permissions: {}
+
+jobs:
+  label-merge-conflicts:
+    # Scheduled/dispatch workflows still run on forks that carry this file;
+    # skip anywhere but the canonical repo.
+    if: github.repository == 'apache/superset'
+    name: Label Merge Conflicts
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read
+      pull-requests: write # to add/remove requires:rebase and need:merge
+    steps:
+      # ASF Infra allowlists this whole action via a wildcard
+      # (eps1lon/actions-label-merge-conflict@*), so any pinned SHA/version
+      # is already fine here - no Infra ticket needed for future bumps.
+      - uses: eps1lon/actions-label-merge-conflict@0273be72a0bbd58fcd71d0d6c02c209b50d1e5e1 # v3.1.0
+        with:
+          dirtyLabel: "requires:rebase"
+          # A conflicting PR isn't actually ready to merge; strip that signal
+          # if it was previously set so reviewers don't act on a stale one.
+          removeOnDirtyLabel: "need:merge"
+          repoToken: ${{ secrets.GITHUB_TOKEN }}
+          # Intentionally no commentOnDirty/commentOnClean: the label alone is
+          # the signal (matches the label's existing description, and avoids
+          # a one-time comment storm across the whole backlog on first run).

.github/workflows/labeler.yml

@@ -12,7 +12,7 @@ jobs:
     permissions:
       contents: read
       pull-requests: write
-    runs-on: ubuntu-26.04
+    runs-on: ubuntu-slim
     steps:
     - uses: actions/labeler@bf12e9b00b37c5c0ca2b87b79b2daf7891dbda13 # v7.0.0
       with:

.github/workflows/latest-release-tag.yml

@@ -6,7 +6,7 @@ on:
 jobs:
   latest-release:
     name: Add/update tag to new release
-    runs-on: ubuntu-26.04
+    runs-on: ubuntu-slim
     permissions:
       contents: write
 

.github/workflows/license-check.yml

@@ -15,7 +15,7 @@ concurrency:
 jobs:
   license_check:
     name: License Check
-    runs-on: ubuntu-26.04
+    runs-on: ubuntu-slim
     steps:
       - name: "Checkout ${{ github.ref }} ( ${{ github.sha }} )"
         uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1

.github/workflows/mirror-service-images.yml

@@ -80,13 +80,13 @@ jobs:
           - starburstdata/presto:350-e.6
     steps:
       - name: Log in to Docker Hub (authenticated source pulls)
-        uses: docker/login-action@abd2ef45e78c5afb21d64d4ca52ee8550d9572c7 # v4.5.1
+        uses: docker/login-action@371161bbe7024a29a25c5e19bfcbc0804fe9ad2c # v4.5.2
         with:
           username: ${{ secrets.DOCKERHUB_USER }}
           password: ${{ secrets.DOCKERHUB_TOKEN }}
 
       - name: Log in to GHCR (push target)
-        uses: docker/login-action@abd2ef45e78c5afb21d64d4ca52ee8550d9572c7 # v4.5.1
+        uses: docker/login-action@371161bbe7024a29a25c5e19bfcbc0804fe9ad2c # v4.5.2
         with:
           registry: ghcr.io
           username: ${{ github.actor }}

.github/workflows/no-hold-label.yml

@@ -17,7 +17,7 @@ concurrency:
 
 jobs:
   check-hold-label:
-    runs-on: ubuntu-26.04
+    runs-on: ubuntu-slim
     steps:
     - name: Check for 'hold' label
       uses: actions/github-script@3a2844b7e9c422d3c10d287c895573f7108da1b3 # v9.0.0

.github/workflows/pr-lint.yml

@@ -21,7 +21,7 @@ concurrency:
 
 jobs:
   lint-check:
-    runs-on: ubuntu-26.04
+    runs-on: ubuntu-slim
     permissions:
       contents: read
       pull-requests: write

.github/workflows/pre-commit.yml

@@ -15,6 +15,7 @@ on:
 
 permissions:
   contents: read
+  actions: read
 
 # cancel previous workflow jobs for PRs
 concurrency:
@@ -188,3 +189,12 @@ jobs:
             echo "📖 More details here: https://superset.apache.org/docs/contributing/development#git-hooks"
             exit 1
           fi
+
+  actions-timeline:
+    needs: pre-commit
+    if: always()
+    runs-on: ubuntu-26.04
+    steps:
+      - uses: Kesin11/actions-timeline@7bf79990b7c09f5dfb570ac30b814ca597bd538e # v3.1.1
+        with:
+          expand-composite-actions: true

.github/workflows/release.yml

@@ -11,7 +11,7 @@ permissions:
 
 jobs:
   config:
-    runs-on: ubuntu-26.04
+    runs-on: ubuntu-slim
     outputs:
       has-secrets: ${{ steps.check.outputs.has-secrets }}
     steps:

.github/workflows/superset-app-cli.yml

@@ -11,6 +11,7 @@ on:
 permissions:
   contents: read
   pull-requests: read
+  actions: read
 
 # cancel previous workflow jobs for PRs
 concurrency:
@@ -40,6 +41,10 @@ jobs:
         ports:
           - 16379:6379
     steps:
+      - uses: Kesin11/actions-timeline@7bf79990b7c09f5dfb570ac30b814ca597bd538e # v3.1.1
+        with:
+          expand-composite-actions: true
+
       - name: "Checkout ${{ github.ref }} ( ${{ github.sha }} )"
         uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
         with:

.github/workflows/superset-docs-deploy.yml

@@ -30,6 +30,7 @@ concurrency:
 
 permissions:
   contents: read
+  actions: read
 
 jobs:
   config:
@@ -59,6 +60,10 @@ jobs:
     name: Build & Deploy
     runs-on: ubuntu-26.04
     steps:
+      - uses: Kesin11/actions-timeline@7bf79990b7c09f5dfb570ac30b814ca597bd538e # v3.1.1
+        with:
+          expand-composite-actions: true
+
       - name: "Checkout ${{ github.event.workflow_run.head_sha || github.sha }}"
         uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
         with:

.github/workflows/superset-e2e.yml

@@ -57,19 +57,13 @@ jobs:
       pull-requests: read
     strategy:
       # when one test fails, DO NOT cancel the other
-      # parallel_id, because this will kill Cypress processes
+      # app_root variant, because this will kill Cypress processes
       # leaving the Dashboard hanging ...
       # https://github.com/cypress-io/github-action/issues/48
       fail-fast: false
       matrix:
-        parallel_id: [0, 1]
         browser: ["chrome"]
         app_root: ${{ github.event_name == 'push' && fromJSON('["", "/app/prefix"]') || fromJSON('[""]') }}
-        # The /app/prefix variant (push events only) is smoke-tested on a single
-        # shard rather than the full matrix, so exclude it from the other shards.
-        exclude:
-          - parallel_id: 1
-            app_root: "/app/prefix"
     env:
       SUPERSET_ENV: development
       SUPERSET_CONFIG: tests.integration_tests.superset_test_config
@@ -148,8 +142,6 @@ jobs:
         uses: ./.github/actions/cached-dependencies
         env:
           CYPRESS_BROWSER: ${{ matrix.browser }}
-          PARALLEL_ID: ${{ matrix.parallel_id }}
-          PARALLELISM: 2
           CYPRESS_RECORD_KEY: ${{ secrets.CYPRESS_RECORD_KEY }}
           NODE_OPTIONS: "--max-old-space-size=4096"
         with:
@@ -167,7 +159,7 @@ jobs:
         if: failure()
         with:
           path: ${{ github.workspace }}/superset-frontend/cypress-base/cypress/screenshots
-          name: cypress-artifact-${{ github.run_id }}-${{ github.job }}-${{ matrix.browser }}-${{ matrix.parallel_id }}--${{ steps.set-safe-app-root.outputs.safe_app_root }}
+          name: cypress-artifact-${{ github.run_id }}-${{ github.job }}-${{ matrix.browser }}--${{ steps.set-safe-app-root.outputs.safe_app_root }}
 
   playwright-tests:
     needs: changes
@@ -264,6 +256,21 @@ jobs:
           NODE_OPTIONS: "--max-old-space-size=4096"
         with:
           run: playwright-run "${{ matrix.app_root }}"
+      - name: Run Playwright (Soft-delete Tests)
+        uses: ./.github/actions/cached-dependencies
+        env:
+          NODE_OPTIONS: "--max-old-space-size=4096"
+          # Scoped to this step: each playwright-run boots its own gunicorn
+          # with the step's env, so the Required Tests server above keeps
+          # master's Flask configuration while this one runs with SOFT_DELETE
+          # on — the same isolation pattern as the Embedded step in
+          # superset-playwright.yml. Without a flag-on server the
+          # recently-archived specs skip themselves everywhere and ship zero
+          # executed E2E coverage; in the Required run above they are
+          # collected and skipped, which is expected.
+          SUPERSET_FEATURE_SOFT_DELETE: "true"
+        with:
+          run: playwright-run "${{ matrix.app_root }}" recently-archived/
       - name: Set safe app root
         if: failure()
         id: set-safe-app-root
@@ -340,3 +347,14 @@ jobs:
             exit 1
           fi
           echo "playwright-tests result: $RESULT (changes: $CHANGES)"
+
+  actions-timeline:
+    needs: [cypress-matrix, playwright-tests, cypress-matrix-required, playwright-tests-required]
+    if: always()
+    runs-on: ubuntu-26.04
+    permissions:
+      actions: read
+    steps:
+      - uses: Kesin11/actions-timeline@7bf79990b7c09f5dfb570ac30b814ca597bd538e # v3.1.1
+        with:
+          expand-composite-actions: true

.github/workflows/superset-extensions-cli.yml

@@ -11,6 +11,7 @@ on:
 permissions:
   contents: read
   pull-requests: read
+  actions: read
 
 # cancel previous workflow jobs for PRs
 concurrency:
@@ -69,3 +70,12 @@ jobs:
         with:
           name: superset-extensions-cli-coverage-html
           path: htmlcov/
+
+  actions-timeline:
+    needs: test-superset-extensions-cli-package
+    if: always()
+    runs-on: ubuntu-26.04
+    steps:
+      - uses: Kesin11/actions-timeline@7bf79990b7c09f5dfb570ac30b814ca597bd538e # v3.1.1
+        with:
+          expand-composite-actions: true

.github/workflows/superset-frontend.yml

@@ -201,3 +201,14 @@ jobs:
         run: |
           docker run --rm $TAG bash -c \
           "npm run build-storybook && npx playwright install-deps && npx playwright install chromium && npm run test-storybook:ci"
+
+  actions-timeline:
+    needs: [report-coverage, lint-frontend, validate-frontend, test-storybook]
+    if: always()
+    runs-on: ubuntu-26.04
+    permissions:
+      actions: read
+    steps:
+      - uses: Kesin11/actions-timeline@7bf79990b7c09f5dfb570ac30b814ca597bd538e # v3.1.1
+        with:
+          expand-composite-actions: true

.github/workflows/superset-helm-lint-test.yml

@@ -8,6 +8,7 @@ on:
 
 permissions:
   contents: read
+  actions: read
 
 # Serialize runs per PR without cancelling: when a first-time contributor's
 # queued runs are approved together, cancel-in-progress lets an older run
@@ -19,8 +20,12 @@ concurrency:
 
 jobs:
   lint-test:
-    runs-on: ubuntu-26.04
+    runs-on: ubuntu-slim
     steps:
+      - uses: Kesin11/actions-timeline@7bf79990b7c09f5dfb570ac30b814ca597bd538e # v3.1.1
+        with:
+          expand-composite-actions: true
+
       - name: "Checkout ${{ github.ref }} ( ${{ github.sha }} )"
         uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
         with:

.github/workflows/superset-playwright.yml

@@ -170,3 +170,14 @@ jobs:
             ${{ github.workspace }}/superset-frontend/playwright-results/
             ${{ github.workspace }}/superset-frontend/test-results/
           name: playwright-experimental-artifact-${{ github.run_id }}-${{ github.job }}-${{ matrix.browser }}--${{ steps.set-safe-app-root.outputs.safe_app_root }}
+
+  actions-timeline:
+    needs: playwright-tests-experimental
+    if: always()
+    runs-on: ubuntu-26.04
+    permissions:
+      actions: read
+    steps:
+      - uses: Kesin11/actions-timeline@7bf79990b7c09f5dfb570ac30b814ca597bd538e # v3.1.1
+        with:
+          expand-composite-actions: true

.github/workflows/superset-python-integrationtest.yml

@@ -255,3 +255,14 @@ jobs:
             exit 1
           fi
           echo "test-postgres result: $RESULT"
+
+  actions-timeline:
+    needs: [test-mysql, test-postgres, test-sqlite, test-postgres-required]
+    if: always()
+    runs-on: ubuntu-26.04
+    permissions:
+      actions: read
+    steps:
+      - uses: Kesin11/actions-timeline@7bf79990b7c09f5dfb570ac30b814ca597bd538e # v3.1.1
+        with:
+          expand-composite-actions: true

.github/workflows/superset-python-presto-hive.yml

@@ -158,3 +158,14 @@ jobs:
           verbose: true
           use_oidc: true
           slug: apache/superset
+
+  actions-timeline:
+    needs: [test-postgres-presto, test-postgres-hive]
+    if: always()
+    runs-on: ubuntu-26.04
+    permissions:
+      actions: read
+    steps:
+      - uses: Kesin11/actions-timeline@7bf79990b7c09f5dfb570ac30b814ca597bd538e # v3.1.1
+        with:
+          expand-composite-actions: true

.github/workflows/superset-python-unittest.yml

@@ -101,7 +101,14 @@ jobs:
     if: always()
     runs-on: ubuntu-26.04
     timeout-minutes: 5
+    permissions:
+      contents: read
+      actions: read
     steps:
+      - uses: Kesin11/actions-timeline@7bf79990b7c09f5dfb570ac30b814ca597bd538e # v3.1.1
+        with:
+          expand-composite-actions: true
+
       - name: Check unit-tests result
         env:
           RESULT: ${{ needs.unit-tests.result }}

.github/workflows/superset-translations.yml

@@ -153,3 +153,14 @@ jobs:
       - name: Fail if regression detected
         if: steps.regression.outcome == 'failure'
         run: exit 1
+
+  actions-timeline:
+    needs: [frontend-check-translations, babel-extract]
+    if: always()
+    runs-on: ubuntu-26.04
+    permissions:
+      actions: read
+    steps:
+      - uses: Kesin11/actions-timeline@7bf79990b7c09f5dfb570ac30b814ca597bd538e # v3.1.1
+        with:
+          expand-composite-actions: true

.github/workflows/superset-websocket.yml

@@ -21,7 +21,7 @@ concurrency:
 
 jobs:
   app-checks:
-    runs-on: ubuntu-26.04
+    runs-on: ubuntu-slim
     timeout-minutes: 20
     steps:
       - name: "Checkout ${{ github.ref }} ( ${{ github.sha }} )"
@@ -41,9 +41,9 @@ jobs:
       - name: typescript checks
         working-directory: ./superset-websocket
         run: npm run type
-      - name: prettier
+      - name: code format check
         working-directory: ./superset-websocket
-        run: npm run prettier-check
+        run: npm run format-check
       - name: unit tests
         working-directory: ./superset-websocket
         run: npm run test

.github/workflows/sync-requirements-for-python-dep-upgrade-pr.yml

@@ -38,7 +38,7 @@ jobs:
       - name: Login to Docker Hub
         if: ${{ steps.dependabot-metadata.outputs.package-ecosystem == 'pip' }}
         continue-on-error: true
-        uses: docker/login-action@abd2ef45e78c5afb21d64d4ca52ee8550d9572c7 # v4.5.1
+        uses: docker/login-action@371161bbe7024a29a25c5e19bfcbc0804fe9ad2c # v4.5.2
         with:
           username: ${{ secrets.DOCKERHUB_USER }}
           password: ${{ secrets.DOCKERHUB_TOKEN }}

.github/workflows/tag-release.yml

@@ -32,7 +32,7 @@ concurrency:
 
 jobs:
   config:
-    runs-on: ubuntu-26.04
+    runs-on: ubuntu-slim
     outputs:
       has-secrets: ${{ steps.check.outputs.has-secrets }}
     steps:

.github/workflows/tech-debt.yml

@@ -11,7 +11,7 @@ permissions:
 
 jobs:
   config:
-    runs-on: ubuntu-26.04
+    runs-on: ubuntu-slim
     outputs:
       has-secrets: ${{ steps.check.outputs.has-secrets }}
     steps:
@@ -28,7 +28,7 @@ jobs:
   process-and-upload:
     needs: config
     if: needs.config.outputs.has-secrets
-    runs-on: ubuntu-26.04
+    runs-on: ubuntu-slim
     name: Generate Reports
     steps:
       - name: Checkout Repository

.github/workflows/welcome-new-users.yml

@@ -7,7 +7,7 @@ on:
 
 jobs:
   welcome:
-    runs-on: ubuntu-26.04
+    runs-on: ubuntu-slim
     if: github.event.pull_request.author_association == 'FIRST_TIME_CONTRIBUTOR'
     permissions:
       pull-requests: write

.pre-commit-config.yaml

@@ -62,12 +62,19 @@ repos:
         args: ["--markdown-linebreak-ext=md"]
   - repo: local
     hooks:
-      - id: prettier-frontend
-        name: prettier (frontend)
-        entry: bash -c 'cd superset-frontend && files=(); for f in "$@"; do files+=("${f#superset-frontend/}"); done; npx prettier --write -- "${files[@]}"' --
+      - id: oxfmt-frontend
+        name: oxfmt (frontend)
+        entry: bash -c 'cd superset-frontend && files=(); for f in "$@"; do files+=("${f#superset-frontend/}"); done; npx oxfmt --write -- "${files[@]}"' --
         language: system
         pass_filenames: true
         files: ^superset-frontend/.*\.(js|jsx|ts|tsx|css|scss|sass|json)$
+        # oxfmt treats lockfiles as generated files and internally filters them
+        # out of its target list. If a diff only touches a lockfile, pre-commit
+        # still hands it to oxfmt as the sole target, and oxfmt hard-errors with
+        # "Expected at least one target file" once its internal filtering leaves
+        # zero files to format. Excluding lockfiles here keeps pre-commit from
+        # ever invoking oxfmt on a target set that's guaranteed to end up empty.
+        exclude: ^superset-frontend/(package-lock\.json|yarn\.lock|pnpm-lock\.yaml)$
   - repo: local
     hooks:
       - id: oxlint-frontend

.rat-excludes

@@ -10,7 +10,6 @@
 .stylelintignore
 .flake8
 .nvmrc
-.prettierrc
 .rat-excludes
 .swcrc
 .*log
@@ -64,7 +63,6 @@ tsconfig.tsbuildinfo
 .*yml
 .*iml
 .esprintrc
-.prettierignore
 generator-superset/*
 temporary_superset_ui/*
 

AGENTS.md

@@ -19,7 +19,7 @@ git commit --amend  # or new commit
 ```
 
 Common pre-commit failures:
-- **Formatting** - black, prettier, eslint will auto-fix
+- **Formatting** - black, oxfmt, eslint will auto-fix
 - **Type errors** - mypy failures need manual fixes
 - **Linting** - ruff, pylint issues need manual fixes
 
@@ -263,7 +263,7 @@ git add .                        # Pre-commit only checks staged files
 # Quick validation (faster than --all-files)
 pre-commit run                   # Staged files only
 pre-commit run mypy              # Python type checking
-pre-commit run prettier          # Code formatting
+pre-commit run format            # Code formatting
 pre-commit run eslint            # Frontend linting
 ```
 

Makefile

@@ -95,7 +95,7 @@ py-format: pre-commit
 	pre-commit run black --all-files
 
 js-format:
-	cd superset-frontend; npm run prettier
+	cd superset-frontend; npm run format
 
 flask-app:
 	flask run -p 8088 --reload --debugger

RELEASING/validate_this_release.sh

@@ -1,3 +1,5 @@
+#!/usr/bin/env bash
+
 # Licensed to the Apache Software Foundation (ASF) under one
 # or more contributor license agreements.  See the NOTICE file
 # distributed with this work for additional information
@@ -15,8 +17,6 @@
 # specific language governing permissions and limitations
 # under the License.
 
-#!/bin/bash
-
 # Function to determine Python command
 get_python_command() {
     if command -v python3 &>/dev/null; then

UPDATING.md

@@ -418,6 +418,19 @@ Deployments that replace the default `CELERY_CONFIG` must add `superset.tasks.de
 
 Operators can immediately erase a specific entity for compliance (GDPR) via `superset deletion-retention force-purge --uuid <uuid>`; this applies legacy hard-delete semantics — a live chart referencing a force-purged dataset is left without a datasource until re-pointed (the chart is not modified), and it purges the named entity even when it was never soft-deleted. Every purge writes an immutable, content-free audit record to the new `purge_audit_log` table that survives the entity it names: the **scheduled** purge fails closed (an entity whose audit row cannot be written is skipped and retried next run), while **force-purge** proceeds even if the audit write fails — the operator is present and deletion outranks audit for a compliance erasure.
 
+### Recently Archived view and permanent delete (purge) endpoints
+
+Behind the same `SOFT_DELETE` flag, a **Recently Archived** page (Settings menu, `/archived/`) lists soft-deleted charts, dashboards, and datasets with their archive time and archiving user, and offers **Recover** and **Delete permanently** row actions. The page admits any viewer holding `can_read` on **any** of the three types and offers each viewer only the types they can read; a viewer with none of the three sees an explanatory empty state, and unauthenticated requests are redirected to login.
+
+**New endpoints** — `POST /api/v1/{chart,dashboard,dataset}/<uuid>/purge` permanently delete a single **soft-deleted** row, running the same cascade as the retention task. Irreversible. Requires `can_write` on the entity plus editorship of the row (or admin), mirroring `/restore`. The endpoints answer 404 while `SOFT_DELETE` is off (restore deliberately stays live so rows archived before a flag-off remain recoverable), 404 for rows that are not soft-deleted, and 422 with a reason when the purge is blocked (an alert/report references the entity, a user has the dashboard as their welcome page, or a restrictive foreign key intervenes). A purge that cannot write its audit record is refused with 422 rather than executed unrecorded — unlike the operator CLI, an end user's purge never outranks the audit.
+
+With the flag on, delete confirmations across the chart/dashboard/dataset list pages change shape: a recoverable archive is confirmed with a primary **Archive** button and no type-DELETE friction, and the copy states the retention window when one is configured. A bulk dataset selection that includes semantic views keeps the full danger treatment, because semantic views have no soft-delete — they are deleted permanently and the confirmation says so.
+
+This also resolves the limitation noted under *Soft delete and restore for datasets*: a database blocked by soft-deleted datasets can now be freed by purging those datasets (per-entity endpoint, retention task, or `force-purge` CLI) instead of hard-deleting `tables` rows out-of-band.
+
+The `purge_audit_log` table is **never pruned by design** — the audit must survive the entities it names; operators who need to age it out should prune manually.
+
+
 ### Webhook alerts/reports block private/internal hosts by default
 
 Webhook alert/report dispatch (`WebhookNotification.send`) now validates the target URL's host against the same private/internal-IP block applied to dataset import URLs. If the resolved host is in a loopback, link-local, private (RFC-1918), shared-CGNAT, or multicast range, the webhook is rejected with `NotificationParamException`.

docker/apt-install.sh

@@ -38,7 +38,7 @@ RESET='\033[0m'
 echo -e "${GREEN}Updating package lists...${RESET}"
 apt-get update -qq
 
-echo -e "${GREEN}Installing packages: $@${RESET}"
+echo -e "${GREEN}Installing packages: $*${RESET}"
 apt-get install -yqq --no-install-recommends "$@"
 
 echo -e "${GREEN}Autoremoving unnecessary packages...${RESET}"

docker/tag_latest_release.sh

@@ -163,10 +163,10 @@ do
     # Iterate through the components of the version strings
     for (( j=0; j<${#THIS_TAG_NAME_ARRAY[@]}; j++ )); do
         echo "Comparing ${THIS_TAG_NAME_ARRAY[$j]} to ${LATEST_RELEASE_TAG_ARRAY[$j]}"
-        if [[ $((THIS_TAG_NAME_ARRAY[$j])) > $((LATEST_RELEASE_TAG_ARRAY[$j])) ]]; then
+        if [[ $((THIS_TAG_NAME_ARRAY[$j])) -gt $((LATEST_RELEASE_TAG_ARRAY[$j])) ]]; then
             compare_result="greater"
             break
-        elif [[ $((THIS_TAG_NAME_ARRAY[$j])) < $((LATEST_RELEASE_TAG_ARRAY[$j])) ]]; then
+        elif [[ $((THIS_TAG_NAME_ARRAY[$j])) -lt $((LATEST_RELEASE_TAG_ARRAY[$j])) ]]; then
             compare_result="lesser"
             break
         fi

docs/.claude/instructions.md

@@ -9,11 +9,13 @@ When working on the Storybook-to-MDX documentation system:
 ## Why This Matters
 
 The generator (`scripts/generate-superset-components.mjs`) should be lightweight - it extracts data from stories and passes it through. When you add special cases to the generator:
+
 - It becomes harder to maintain
 - Stories diverge from their docs representation
 - Future stories need to know about generator quirks
 
 When you fix stories to match the expected patterns:
+
 - Stories work identically in Storybook and Docs
 - The generator stays simple and predictable
 - Patterns are consistent and learnable
@@ -21,6 +23,7 @@ When you fix stories to match the expected patterns:
 ## Story Patterns for Docs Generation
 
 ### Required Structure
+
 ```tsx
 // Use inline export default (NOT const meta = ...; export default meta)
 export default {
@@ -45,6 +48,7 @@ export const InteractiveMyComponent: Story = {
 ```
 
 ### For Components with Variants (size × style grids)
+
 ```tsx
 const sizes = ['small', 'medium', 'large'];
 const variants = ['primary', 'secondary', 'danger'];
@@ -63,16 +67,20 @@ InteractiveButton.parameters = {
 ```
 
 ### For Components Requiring Children
+
 ```tsx
 InteractiveIconTooltip.parameters = {
   docs: {
     // Component descriptors with dot notation for nested components
-    sampleChildren: [{ component: 'Icons.InfoCircleOutlined', props: { iconSize: 'l' } }],
+    sampleChildren: [
+      { component: 'Icons.InfoCircleOutlined', props: { iconSize: 'l' } },
+    ],
   },
 };
 ```
 
 ### For Custom Live Code Examples
+
 ```tsx
 InteractiveMyComponent.parameters = {
   docs: {
@@ -84,6 +92,7 @@ InteractiveMyComponent.parameters = {
 ```
 
 ### For Complex Props (objects, arrays)
+
 ```tsx
 InteractiveMenu.parameters = {
   docs: {
@@ -99,13 +108,13 @@ InteractiveMenu.parameters = {
 
 ## Common Issues and How to Fix Them (in the Story)
 
-| Issue | Wrong Approach | Right Approach |
-|-------|---------------|----------------|
-| Component not generated | Add pattern to generator | Change story to use inline `export default` |
+| Issue                                   | Wrong Approach                | Right Approach                                    |
+| --------------------------------------- | ----------------------------- | ------------------------------------------------- |
+| Component not generated                 | Add pattern to generator      | Change story to use inline `export default`       |
 | Control shows as text instead of select | Add special case in generator | Add `argTypes` with `control: { type: 'select' }` |
-| Missing children/content | Modify StorybookWrapper | Add `parameters.docs.sampleChildren` |
-| Gallery not showing | Add to generator output | Add `parameters.docs.gallery` config |
-| Wrong live example | Hardcode in generator | Add `parameters.docs.liveExample` |
+| Missing children/content                | Modify StorybookWrapper       | Add `parameters.docs.sampleChildren`              |
+| Gallery not showing                     | Add to generator output       | Add `parameters.docs.gallery` config              |
+| Wrong live example                      | Hardcode in generator         | Add `parameters.docs.liveExample`                 |
 
 ## Files
 

docs/.oxfmtrc.json

@@ -0,0 +1,9 @@
+{
+  "$schema": "./node_modules/oxfmt/configuration_schema.json",
+  "singleQuote": true,
+  "trailingComma": "all",
+  "arrowParens": "avoid",
+  "printWidth": 80,
+  "sortPackageJson": false,
+  "ignorePatterns": ["**/*.mdx"]
+}

docs/.prettierrc

@@ -1,5 +0,0 @@
-{
-  "singleQuote": true,
-  "trailingComma": "all",
-  "arrowParens": "avoid"
-}

docs/DOCS_CLAUDE.md

@@ -69,6 +69,7 @@ yarn eslint              # Lint TypeScript/JavaScript files
 ## 📁 Documentation Structure
 
 ### Main Documentation (`/docs`)
+
 The primary documentation lives in `/docs` with this structure:
 
 ```
@@ -104,54 +105,57 @@ docs/
 ```
 
 ### Admin Docs (`/admin_docs`)
+
 Admin-focused content: installation, configuration, security.
 
 ### Developer Docs (`/developer_docs`)
+
 Developer-focused content: API documentation, architecture guides, CLI tools, code examples.
 
 ### Component Playground (`/components`)
+
 Interactive component examples for UI development.
 
 ## 📝 Documentation Standards
 
 ### File Types
+
 - **`.md` files**: Basic Markdown documents
 - **`.mdx` files**: Markdown with JSX - can include React components
 - **`.tsx` files in `/src`**: Custom React components and pages
 
 ### Frontmatter Structure
+
 Every documentation page should have frontmatter:
 
 ```yaml
 ---
 title: Page Title
 description: Brief description for SEO
-sidebar_position: 1  # Optional: controls order in sidebar
+sidebar_position: 1 # Optional: controls order in sidebar
 ---
 ```
 
 ### MDX Component Usage
+
 MDX files can import and use React components:
 
-```mdx
+````mdx
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 
 <Tabs>
   <TabItem value="npm" label="npm" default>
-    ```bash
-    npm install superset
-    ```
+    ```bash npm install superset ```
   </TabItem>
   <TabItem value="yarn" label="yarn">
-    ```bash
-    yarn add superset
-    ```
+    ```bash yarn add superset ```
   </TabItem>
 </Tabs>
-```
+````
 
 ### Code Blocks
+
 Use triple backticks with language identifiers:
 
 ````markdown
@@ -171,6 +175,7 @@ pip install apache-superset
 ````
 
 ### Admonitions
+
 Docusaurus supports various admonition types:
 
 ```markdown
@@ -198,20 +203,21 @@ This is an info box
 ## 🔄 Version Management
 
 ### Version Configuration
+
 Versions are managed through `versions-config.json`:
 
 ```json
 {
   "docs": {
     "disabled": false,
-    "lastVersion": "6.0.0",        // Default version shown
-    "includeCurrentVersion": true,  // Show "Next" version
+    "lastVersion": "6.0.0", // Default version shown
+    "includeCurrentVersion": true, // Show "Next" version
     "onlyIncludeVersions": ["current", "6.0.0"],
     "versions": {
       "current": {
         "label": "Next",
         "path": "",
-        "banner": "unreleased"     // Shows warning banner
+        "banner": "unreleased" // Shows warning banner
       },
       "6.0.0": {
         "label": "6.0.0",
@@ -224,6 +230,7 @@ Versions are managed through `versions-config.json`:
 ```
 
 ### Creating New Versions
+
 **IMPORTANT**: Always use the custom scripts, NOT native Docusaurus commands:
 
 ```bash
@@ -235,8 +242,10 @@ yarn docusaurus docs:version 6.1.0
 ```
 
 ### Version Files Created
+
 When versioning, these files are created (per section, with the
 section's plugin id as prefix):
+
 - `<section>_versioned_docs/version-X.X.X/` - Snapshot of current docs
 - `<section>_versioned_sidebars/version-X.X.X-sidebars.json` - Sidebar config
 - `<section>_versions.json` - List of all versions
@@ -246,6 +255,7 @@ Section plugin ids: `user_docs`, `admin_docs`, `developer_docs`, `components`.
 ## 🎨 Styling and Theming
 
 ### Custom CSS
+
 Add custom styles in `/src/css/custom.css`:
 
 ```css
@@ -256,13 +266,14 @@ Add custom styles in `/src/css/custom.css`:
 ```
 
 ### Custom Components
+
 Create React components in `/src/components/`:
 
 ```tsx
 // src/components/FeatureCard.tsx
 import React from 'react';
 
-export default function FeatureCard({title, description}) {
+export default function FeatureCard({ title, description }) {
   return (
     <div className="card">
       <h3>{title}</h3>
@@ -277,10 +288,7 @@ Use in MDX:
 ```mdx
 import FeatureCard from '@site/src/components/FeatureCard';
 
-<FeatureCard
-  title="Fast"
-  description="Lightning fast queries"
-/>
+<FeatureCard title="Fast" description="Lightning fast queries" />
 ```
 
 ## 📦 Key Dependencies
@@ -295,6 +303,7 @@ import FeatureCard from '@site/src/components/FeatureCard';
 ## 🔗 Linking Strategies
 
 ### Internal Links
+
 Use relative paths for internal documentation:
 
 ```markdown
@@ -303,6 +312,7 @@ Use relative paths for internal documentation:
 ```
 
 ### External Links
+
 Always use full URLs:
 
 ```markdown
@@ -310,6 +320,7 @@ Always use full URLs:
 ```
 
 ### Linking to Code
+
 Reference code in the main repository:
 
 ```markdown
@@ -319,21 +330,24 @@ See the [main configuration file](https://github.com/apache/superset/blob/master
 ## 🛠️ Common Documentation Tasks
 
 ### Adding a New Guide
+
 1. Create the `.mdx` file in the appropriate directory
 2. Add frontmatter with title and description
 3. Update sidebar if needed (for manual sidebar configs)
 
 ### Adding API Documentation
+
 The API docs use Swagger UI embedded in `/docs/api.mdx`:
 
 ```mdx
-import SwaggerUI from "swagger-ui-react";
-import "swagger-ui-react/swagger-ui.css";
+import SwaggerUI from 'swagger-ui-react';
+import 'swagger-ui-react/swagger-ui.css';
 
 <SwaggerUI url="/api/v1/openapi.json" />
 ```
 
 ### Adding Interactive Examples
+
 Use MDX to create interactive documentation:
 
 ```mdx
@@ -360,6 +374,7 @@ When creating or updating documentation:
 ## 🔍 Searching and Navigation
 
 ### Sidebar Configuration
+
 Sidebars are configured in `/sidebars.js`:
 
 ```javascript
@@ -385,6 +400,7 @@ module.exports = {
 ```
 
 ### Search
+
 Docusaurus includes Algolia DocSearch integration configured in `docusaurus.config.ts`.
 
 ## 🚫 Common Pitfalls to Avoid
@@ -398,6 +414,7 @@ Docusaurus includes Algolia DocSearch integration configured in `docusaurus.conf
 ## 🔧 Troubleshooting
 
 ### Dev Server Issues
+
 ```bash
 yarn stop     # Kill any running servers
 yarn clear    # Clear cache
@@ -405,6 +422,7 @@ yarn start    # Restart
 ```
 
 ### Build Failures
+
 ```bash
 # Check for broken links
 yarn build
@@ -417,7 +435,9 @@ yarn eslint
 ```
 
 ### Version Issues
+
 If versions don't appear in dropdown:
+
 1. Check `versions-config.json` includes the version
 2. Verify version files exist in `<section>_versioned_docs/`
 3. Restart dev server
@@ -432,9 +452,10 @@ If versions don't appear in dropdown:
 ## 📖 Real Examples and Patterns
 
 ### Example: Configuration Documentation Pattern
+
 From `docs/configuration/configuring-superset.mdx`:
 
-```mdx
+````mdx
 ---
 title: Configuring Superset
 hide_title: true
@@ -452,7 +473,9 @@ Superset exposes hundreds of configurable parameters through its
 ```bash
 export SUPERSET_CONFIG_PATH=/app/superset_config.py
 ```
-```
+````
+
+````
 
 **Key patterns:**
 - Links to source code for reference
@@ -476,9 +499,10 @@ documentation at [docs.preset.io](https://docs.preset.io/).
 ### Connecting to a new database
 
 <img src={useBaseUrl("/img/tutorial/tutorial_01_add_database_connection.png")} width="600" />
-```
+````
 
 **Key patterns:**
+
 - Import Docusaurus hooks for dynamic URLs
 - Use of admonitions (:::tip) for helpful information
 - Screenshots with useBaseUrl for proper path resolution
@@ -486,11 +510,12 @@ documentation at [docs.preset.io](https://docs.preset.io/).
 - Step-by-step visual guides
 
 ### Example: API Documentation Pattern
+
 From `docs/api.mdx`:
 
 ```mdx
-import SwaggerUI from "swagger-ui-react";
-import "swagger-ui-react/swagger-ui.css";
+import SwaggerUI from 'swagger-ui-react';
+import 'swagger-ui-react/swagger-ui.css';
 
 ## API Documentation
 
@@ -498,6 +523,7 @@ import "swagger-ui-react/swagger-ui.css";
 ```
 
 **Key patterns:**
+
 - Embedding interactive Swagger UI
 - Importing necessary CSS
 - Direct API spec integration
@@ -508,49 +534,39 @@ import "swagger-ui-react/swagger-ui.css";
 // For images in static folder
 import useBaseUrl from "@docusaurus/useBaseUrl";
 
-<img src={useBaseUrl("/img/feature-screenshot.png")} width="600" />
+<img src={useBaseUrl('/img/feature-screenshot.png')} width="600" />
 
 // With caption
+
 <figure>
-  <img src={useBaseUrl("/img/dashboard.png")} alt="Dashboard view" />
+  <img src={useBaseUrl('/img/dashboard.png')} alt="Dashboard view" />
   <figcaption>Superset Dashboard Interface</figcaption>
 </figure>
 ```
 
 ### Multi-Tab Code Examples
 
-```mdx
+````mdx
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 
 <Tabs
   defaultValue="docker"
   values={[
-    {label: 'Docker', value: 'docker'},
-    {label: 'Kubernetes', value: 'k8s'},
-    {label: 'PyPI', value: 'pypi'},
-  ]}>
-  <TabItem value="docker">
-    ```bash
-    docker-compose up
-    ```
-  </TabItem>
-  <TabItem value="k8s">
-    ```bash
-    kubectl apply -f superset.yaml
-    ```
-  </TabItem>
-  <TabItem value="pypi">
-    ```bash
-    pip install apache-superset
-    ```
-  </TabItem>
+    { label: 'Docker', value: 'docker' },
+    { label: 'Kubernetes', value: 'k8s' },
+    { label: 'PyPI', value: 'pypi' },
+  ]}
+>
+  <TabItem value="docker">```bash docker-compose up ```</TabItem>
+  <TabItem value="k8s">```bash kubectl apply -f superset.yaml ```</TabItem>
+  <TabItem value="pypi">```bash pip install apache-superset ```</TabItem>
 </Tabs>
-```
+````
 
 ### Configuration File Examples
 
-```mdx
+````mdx
 ```python title="superset_config.py"
 # Database connection example
 SQLALCHEMY_DATABASE_URI = 'postgresql://user:password@localhost/superset'
@@ -565,7 +581,9 @@ FEATURE_FLAGS = {
     'DASHBOARD_NATIVE_FILTERS': True,
 }
 ```
-```
+````
+
+````
 
 ### Cross-Referencing Pattern
 
@@ -578,11 +596,11 @@ For detailed configuration options, see:
 External resources:
 - [SQLAlchemy Documentation](https://docs.sqlalchemy.org/)
 - [Flask Configuration](https://flask.palletsprojects.com/config/)
-```
+````
 
 ### Writing Installation Guides
 
-```mdx
+````mdx
 ## Prerequisites
 
 :::warning
@@ -596,8 +614,10 @@ Ensure you have Python 3.9+ and Node.js 16+ installed before proceeding.
    git clone https://github.com/apache/superset.git
    cd superset
    ```
+````
 
 2. **Install Python dependencies**
+
    ```bash
    pip install -e .
    ```
@@ -611,7 +631,8 @@ Ensure you have Python 3.9+ and Node.js 16+ installed before proceeding.
 :::tip Success Check
 Navigate to http://localhost:8088 and login with admin/admin
 :::
-```
+
+````
 
 ### Documenting API Endpoints
 
@@ -630,9 +651,10 @@ Returns a list of charts.
 ```bash
 curl -X GET "http://localhost:8088/api/v1/chart/" \
   -H "Authorization: Bearer YOUR_ACCESS_TOKEN"
-```
+````
 
 **Example Response:**
+
 ```json
 {
   "count": 42,
@@ -645,8 +667,10 @@ curl -X GET "http://localhost:8088/api/v1/chart/" \
   ]
 }
 ```
+
 ```
 
 ---
 
 **Note**: This documentation site serves as the primary resource for Superset users, administrators, and contributors. Always prioritize clarity, accuracy, and completeness when creating or updating documentation.
+```

docs/README.md

@@ -66,6 +66,7 @@ yarn version:add:components 1.2.0
 ```
 
 What the script does:
+
 1. Refreshes auto-generated content via `generate:smart` (database pages, API reference, component pages).
 2. Calls `yarn docusaurus docs:version` (or the per-section equivalent) to snapshot the section.
 3. Freezes any data-file imports (`@site/static/*.json`, `../../data/*.json`) into a snapshot-local `_versioned_data/` dir so the historical version doesn't silently mutate when the source files change.
@@ -73,6 +74,7 @@ What the script does:
 5. Updates `versions-config.json` and `<section>_versions.json`.
 
 **Do NOT use** the native Docusaurus commands directly (`yarn docusaurus docs:version`), as they will:
+
 - ❌ Create version files but NOT update `versions-config.json`
 - ❌ Skip auto-gen refresh, freezing whatever was on disk
 - ❌ Skip data-import freezing, leaving the snapshot pointed at live data
@@ -82,9 +84,11 @@ What the script does:
 ### Managing Versions
 
 #### With Automated Scripts
+
 The automated scripts handle all configuration updates automatically. No manual editing required!
 
 #### Manual Configuration
+
 If creating versions manually, you'll need to:
 
 1. **Update `versions-config.json`** (or `docusaurus.config.ts` if not using dynamic config):
@@ -109,6 +113,7 @@ If creating versions manually, you'll need to:
 ### Removing a Version
 
 #### Using Automated Scripts (Recommended)
+
 ```bash
 # Main Documentation
 yarn version:remove:user_docs 1.0.0
@@ -124,6 +129,7 @@ yarn version:remove:components 1.0.0
 ```
 
 #### Manual Removal
+
 To manually remove a version:
 
 1. **Delete the version folder** from the appropriate location:
@@ -153,6 +159,7 @@ To manually remove a version:
 ### Version Configuration Examples
 
 #### Main Documentation (default plugin)
+
 ```typescript
 docs: {
   includeCurrentVersion: true,
@@ -174,6 +181,7 @@ docs: {
 ```
 
 #### Developer Docs & Components (custom plugins)
+
 ```typescript
 {
   id: 'developer_docs',
@@ -210,23 +218,28 @@ docs: {
 #### Version Not Showing After Creation
 
 If you accidentally used `yarn docusaurus docs:version` instead of `yarn version:add`:
+
 1. **Problem**: The version files were created but `versions-config.json` wasn't updated
 2. **Solution**: Either:
    - Revert the changes: `git restore user_docs_versions.json && rm -rf user_docs_versioned_docs/ user_docs_versioned_sidebars/`
    - Then use the correct command: `yarn version:add:user_docs <version>`
 
 For other issues:
+
 - **Restart the server**: Changes to version configuration require a server restart
 - **Check config file**: Ensure `versions-config.json` includes the new version
 - **Verify files exist**: Check that versioned docs folder was created
 
 #### Broken Links in Versioned Documentation
+
 When creating a new version, links in the documentation are preserved as-is. Common issues:
+
 - **Cross-section links**: Links between sections (e.g., from developer_docs to docs) need to be version-aware
 - **Absolute vs relative paths**: Use relative paths within the same section
 - **Version-specific URLs**: Update hardcoded URLs to use version variables
 
 To fix broken links:
+
 1. Use `type: 'doc'` with `docId` for version-aware navigation in navbar
 2. Use relative paths within the same documentation section
 3. Test all versions after creation to identify broken links

docs/admin_docs/configuration/alerts-reports.mdx

@@ -9,8 +9,8 @@ version: 2
 
 Users can configure automated alerts and reports to send dashboards or charts to an email recipient or Slack channel.
 
-- *Alerts* are sent when a SQL condition is reached
-- *Reports* are sent on a schedule
+- _Alerts_ are sent when a SQL condition is reached
+- _Reports_ are sent on a schedule
 
 Alerts and reports are disabled by default. To turn them on, you'll need to change configuration settings and install a suitable headless browser in your environment.
 
@@ -26,16 +26,17 @@ Alerts and reports are disabled by default. To turn them on, you'll need to chan
   - emails: `SMTP_*` settings
   - Slack messages: `SLACK_API_TOKEN`
 - Users can customize the email subject by including date code placeholders, which will automatically be replaced with the corresponding UTC date when the email is sent. To enable this functionality, activate the `"DATE_FORMAT_IN_EMAIL_SUBJECT"` [feature flag](/admin-docs/configuration/configuring-superset#feature-flags). This enables date formatting in email subjects, preventing all reporting emails from being grouped into the same thread (optional for the reporting feature).
-    - Use date codes from [strftime.org](https://strftime.org/) to create the email subject.
-    - If no date code is provided, the original string will be used as the email subject.
+  - Use date codes from [strftime.org](https://strftime.org/) to create the email subject.
+  - If no date code is provided, the original string will be used as the email subject.
 
 ##### Disable dry-run mode
 
-Screenshots will be taken but no messages actually sent as long as `ALERT_REPORTS_NOTIFICATION_DRY_RUN = True`, its default value in `docker/pythonpath_dev/superset_config.py`.  To disable dry-run mode and start receiving email/Slack notifications, set `ALERT_REPORTS_NOTIFICATION_DRY_RUN` to `False` in [superset config](https://github.com/apache/superset/blob/master/docker/pythonpath_dev/superset_config.py).
+Screenshots will be taken but no messages actually sent as long as `ALERT_REPORTS_NOTIFICATION_DRY_RUN = True`, its default value in `docker/pythonpath_dev/superset_config.py`. To disable dry-run mode and start receiving email/Slack notifications, set `ALERT_REPORTS_NOTIFICATION_DRY_RUN` to `False` in [superset config](https://github.com/apache/superset/blob/master/docker/pythonpath_dev/superset_config.py).
 
 #### In your `Dockerfile`
 
 You'll need to extend the Superset image to include a headless browser. Your options include:
+
 - Use Playwright with Chromium: this is the recommended approach as of version 4.1.x or greater. Playwright always uses Chromium — the `WEBDRIVER_TYPE` config setting has no effect when Playwright is active. A working example of a Dockerfile that installs these tools is provided under "Building your own production Docker image" on the [Docker Builds](/admin-docs/installation/docker-builds#building-your-own-production-docker-image) page. Enable the `PLAYWRIGHT_REPORTS_AND_THUMBNAILS` feature flag in your config to activate it.
 - Use Firefox (Selenium): you'll need to install geckodriver and Firefox. Set `WEBDRIVER_TYPE` to `"firefox"` in your `superset_config.py`.
 - Use Chrome (Selenium): you'll need to install Chrome. Set `WEBDRIVER_TYPE` to `"chrome"` in your `superset_config.py`.
@@ -204,7 +205,7 @@ You need to replace default values with your custom Redis, Slack and/or SMTP con
 Superset uses Celery beat and Celery worker(s) to send alerts and reports.
 
 - The beat is the scheduler that tells the worker when to perform its tasks. This schedule is defined when you create the alert or report.
-- The worker will process the  tasks that need to be performed when an alert or report is fired.
+- The worker will process the tasks that need to be performed when an alert or report is fired.
 
 In the `CeleryConfig`, only the `beat_schedule` is relevant to this feature, the rest of the `CeleryConfig` can be changed for your needs.
 
@@ -313,7 +314,7 @@ Please refer to `ExecutorType` in the codebase for other executor types.
 
 It's also possible to specify a minimum interval between each report's execution through the config file:
 
-``` python
+```python
 # Set a minimum interval threshold between executions (for each Alert/Report)
 # Value should be an integer
 ALERT_MINIMUM_INTERVAL = int(timedelta(minutes=10).total_seconds())
@@ -322,7 +323,7 @@ REPORT_MINIMUM_INTERVAL = int(timedelta(minutes=5).total_seconds())
 
 Alternatively, you can assign a function to `ALERT_MINIMUM_INTERVAL` and/or `REPORT_MINIMUM_INTERVAL`. This is useful to dynamically retrieve a value as needed:
 
-``` python
+```python
 def alert_dynamic_minimal_interval(**kwargs) -> int:
     """
     Define logic here to retrieve the value dynamically
@@ -335,7 +336,7 @@ ALERT_MINIMUM_INTERVAL = alert_dynamic_minimal_interval
 
 For security, Superset rewrites external links in alert/report email HTML so
 they go through a warning page before the user is navigated to the external
-site.  Internal links (matching your configured base URL) are not affected.
+site. Internal links (matching your configured base URL) are not affected.
 
 ```python
 # Disable external link redirection entirely (default: True)
@@ -347,17 +348,17 @@ to determine which hosts are internal.
 
 ## Troubleshooting
 
-There are many reasons that reports might not be working.  Try these steps to check for specific issues.
+There are many reasons that reports might not be working. Try these steps to check for specific issues.
 
 ### Confirm feature flag is enabled and you have sufficient permissions
 
-If you don't see "Alerts & Reports" under the *Manage* section of the Settings dropdown in the Superset UI, you need to enable the `ALERT_REPORTS` feature flag (see above). Enable another feature flag and check to see that it took effect, to verify that your config file is getting loaded.
+If you don't see "Alerts & Reports" under the _Manage_ section of the Settings dropdown in the Superset UI, you need to enable the `ALERT_REPORTS` feature flag (see above). Enable another feature flag and check to see that it took effect, to verify that your config file is getting loaded.
 
 Log in as an admin user to ensure you have adequate permissions.
 
 ### Check the logs of your Celery worker
 
-This is the best source of information about the problem.  In a docker compose deployment, you can do this with a command like `docker logs superset_worker --since 1h`.
+This is the best source of information about the problem. In a docker compose deployment, you can do this with a command like `docker logs superset_worker --since 1h`.
 
 ### Check web browser and webdriver installation
 
@@ -369,7 +370,7 @@ If you are handling the installation of the headless browser on your own, do you
 
 One symptom of an invalid connection to an email server is receiving an error of `[Errno 110] Connection timed out` in your logs when the report tries to send.
 
-Confirm via testing that your outbound email configuration is correct.  Here is the simplest test, for an un-authenticated email SMTP email service running on port 25.  If you are sending over SSL, for instance, study how [Superset's codebase sends emails](https://github.com/apache/superset/blob/master/superset/utils/core.py#L818) and then test with those commands and arguments.
+Confirm via testing that your outbound email configuration is correct. Here is the simplest test, for an un-authenticated email SMTP email service running on port 25. If you are sending over SSL, for instance, study how [Superset's codebase sends emails](https://github.com/apache/superset/blob/master/superset/utils/core.py#L818) and then test with those commands and arguments.
 
 Start Python in your worker environment, replace all example values, and run:
 
@@ -395,16 +396,16 @@ This should send an email.
 
 Possible fixes:
 
-- Some cloud hosts disable outgoing unauthenticated SMTP email to prevent spam.  For instance, [Azure blocks port 25 by default on some machines](https://learn.microsoft.com/en-us/azure/virtual-network/troubleshoot-outbound-smtp-connectivity). Enable that port or use another sending method.
+- Some cloud hosts disable outgoing unauthenticated SMTP email to prevent spam. For instance, [Azure blocks port 25 by default on some machines](https://learn.microsoft.com/en-us/azure/virtual-network/troubleshoot-outbound-smtp-connectivity). Enable that port or use another sending method.
 - Use another set of SMTP credentials that you verify works in this setup.
 
 ### Browse to your report from the worker
 
-The worker may be unable to reach the report. It will use the value of `WEBDRIVER_BASEURL` to browse to the report.  If that route is invalid, or presents an authentication challenge that the worker can't pass, the report screenshot will fail.
+The worker may be unable to reach the report. It will use the value of `WEBDRIVER_BASEURL` to browse to the report. If that route is invalid, or presents an authentication challenge that the worker can't pass, the report screenshot will fail.
 
 Check this by attempting to `curl` the URL of a report that you see in the error logs of your worker. For instance, from the worker environment, run `curl http://superset_app:8088/superset/dashboard/1/`. You may get different responses depending on whether the dashboard exists - for example, you may need to change the `1` in that URL. If there's a URL in your logs from a failed report screenshot, that's a good place to start. The goal is to determine a valid value for `WEBDRIVER_BASEURL` and determine if an issue like HTTPS or authentication is redirecting your worker.
 
-In a deployment with authentication measures enabled like HTTPS and Single Sign-On, it may make sense to have the worker navigate directly to the Superset application running in the same location, avoiding the need to sign in.  For instance, you could use `WEBDRIVER_BASEURL="http://superset_app:8088"` for a docker compose deployment, and set `"force_https": False,` in your `TALISMAN_CONFIG`.
+In a deployment with authentication measures enabled like HTTPS and Single Sign-On, it may make sense to have the worker navigate directly to the Superset application running in the same location, avoiding the need to sign in. For instance, you could use `WEBDRIVER_BASEURL="http://superset_app:8088"` for a docker compose deployment, and set `"force_https": False,` in your `TALISMAN_CONFIG`.
 
 ### Duplicate report deliveries
 
@@ -512,6 +513,7 @@ schedule the queries that have `schedule_info` in their JSON metadata. For sched
 Airflow, additional fields can be easily added to the configuration file above.
 
 :::resources
+
 - [Tutorial: Automated Alerts and Reporting via Slack/Email in Superset](https://dev.to/ngtduc693/apache-superset-topic-5-automated-alerts-and-reporting-via-slackemail-in-superset-2gbe)
 - [Blog: Integrating Slack alerts and Apache Superset for better data observability](https://medium.com/affinityanswers-tech/integrating-slack-alerts-and-apache-superset-for-better-data-observability-fd2f9a12c350)
-:::
+  :::

docs/admin_docs/configuration/async-queries-celery.mdx

@@ -104,5 +104,6 @@ celery --app=superset.tasks.celery_app:app flower
 ```
 
 :::resources
+
 - [Blog: How to Set Up Global Async Queries (GAQ) in Apache Superset](https://medium.com/@ngigilevis/how-to-set-up-global-async-queries-gaq-in-apache-superset-a-complete-guide-9d2f4a047559)
-:::
+  :::

docs/admin_docs/configuration/aws-iam.mdx

@@ -13,7 +13,7 @@ Cross-account IAM role assumption via STS `AssumeRole` is supported, allowing a
 
 ## Prerequisites
 
-- Enable the `AWS_DATABASE_IAM_AUTH` feature flag in `superset_config.py`. IAM authentication is gated behind this flag; if it is disabled, connections using `aws_iam` fail with *"AWS IAM database authentication is not enabled."*
+- Enable the `AWS_DATABASE_IAM_AUTH` feature flag in `superset_config.py`. IAM authentication is gated behind this flag; if it is disabled, connections using `aws_iam` fail with _"AWS IAM database authentication is not enabled."_
   ```python
   FEATURE_FLAGS = {
       "AWS_DATABASE_IAM_AUTH": True,
@@ -48,14 +48,14 @@ IAM authentication is configured via the **encrypted_extra** field of the databa
 }
 ```
 
-| Field | Required | Description |
-|-------|----------|-------------|
-| `enabled` | Yes | Set to `true` to activate IAM auth |
-| `role_arn` | No | ARN of the cross-account IAM role to assume via STS. Omit for same-account auth |
-| `external_id` | No | External ID for the STS `AssumeRole` call, if required by the target role's trust policy |
-| `region` | Yes | AWS region of the database cluster |
-| `db_username` | Yes | The database username associated with the IAM identity |
-| `session_duration` | No | STS session duration in seconds (default: `3600`) |
+| Field              | Required | Description                                                                              |
+| ------------------ | -------- | ---------------------------------------------------------------------------------------- |
+| `enabled`          | Yes      | Set to `true` to activate IAM auth                                                       |
+| `role_arn`         | No       | ARN of the cross-account IAM role to assume via STS. Omit for same-account auth          |
+| `external_id`      | No       | External ID for the STS `AssumeRole` call, if required by the target role's trust policy |
+| `region`           | Yes      | AWS region of the database cluster                                                       |
+| `db_username`      | Yes      | The database username associated with the IAM identity                                   |
+| `session_duration` | No       | STS session duration in seconds (default: `3600`)                                        |
 
 ### Redshift (Serverless)
 

docs/admin_docs/configuration/cache.mdx

@@ -323,6 +323,7 @@ While database-backed operations work reliably, the Redis backend is recommended
 deployments where low latency and reduced database load are important.
 
 :::resources
+
 - [Blog: The Data Engineer's Guide to Lightning-Fast Superset Dashboards](https://preset.io/blog/the-data-engineers-guide-to-lightning-fast-apache-superset-dashboards/)
 - [Blog: Accelerating Dashboards with Materialized Views](https://preset.io/blog/accelerating-apache-superset-dashboards-with-materialized-views/)
-:::
+  :::

docs/admin_docs/configuration/configuring-superset.mdx

@@ -225,7 +225,7 @@ RequestHeader set X-Forwarded-Proto "https"
 
 ## Configuring the application root
 
-*Please be advised that this feature is in BETA.*
+_Please be advised that this feature is in BETA._
 
 Superset supports running the application under a non-root path. The root path
 prefix can be specified in one of three ways:
@@ -312,10 +312,13 @@ AUTH_USER_REGISTRATION_ROLE = "Public"
 ```
 
 In case you want to assign the `Admin` role on new user registration, it can be assigned as follows:
+
 ```python
 AUTH_USER_REGISTRATION_ROLE = "Admin"
 ```
+
 If you encounter the [issue](https://github.com/apache/superset/issues/13243) of not being able to list users from the Superset main page settings, although a newly registered user has an `Admin` role, please re-run `superset init` to sync the required permissions. Below is the command to re-run `superset init` using docker compose.
+
 ```
 docker-compose exec superset superset init
 ```
@@ -568,5 +571,6 @@ SUPERSET_DASHBOARD_POSITION_DATA_LIMIT = 131072  # double the default
 Alternatively, split a very large dashboard into several smaller ones. Note that this check is enforced when saving layout edits in the UI; a dashboard imported from a ZIP with an oversized layout will load and render, but cannot be edited and re-saved until the limit is raised.
 
 :::resources
+
 - [Blog: Feature Flags in Apache Superset](https://preset.io/blog/feature-flags-in-apache-superset-and-preset/)
-:::
+  :::

docs/admin_docs/configuration/country-map-tools.mdx

@@ -22,10 +22,10 @@ The current list of countries can be found in the src
 
 The Country Maps visualization already ships with the maps for the following countries:
 
-<ul style={{columns: 3}}>
-{countriesData.countries.map((country, index) => (
-  <li key={index}>{country}</li>
-))}
+<ul style={{ columns: 3 }}>
+  {countriesData.countries.map((country, index) => (
+    <li key={index}>{country}</li>
+  ))}
 </ul>
 
 ## Adding a New Country

docs/admin_docs/configuration/feature-flags.mdx

@@ -7,7 +7,7 @@ version: 1
 
 import featureFlags from '@site/static/feature-flags.json';
 
-export const FlagTable = ({flags}) => (
+export const FlagTable = ({ flags }) => (
   <table>
     <thead>
       <tr>
@@ -17,14 +17,21 @@ export const FlagTable = ({flags}) => (
       </tr>
     </thead>
     <tbody>
-      {flags.map((flag) => (
+      {flags.map(flag => (
         <tr key={flag.name}>
-          <td><code>{flag.name}</code></td>
-          <td><code>{flag.default ? 'True' : 'False'}</code></td>
+          <td>
+            <code>{flag.name}</code>
+          </td>
+          <td>
+            <code>{flag.default ? 'True' : 'False'}</code>
+          </td>
           <td>
             {flag.description}
             {flag.docs && (
-              <> (<a href={flag.docs}>docs</a>)</>
+              <>
+                {' '}
+                (<a href={flag.docs}>docs</a>)
+              </>
             )}
           </td>
         </tr>
@@ -50,12 +57,12 @@ FEATURE_FLAGS = {
 
 Feature flags progress through lifecycle stages:
 
-| Stage | Description |
-|-------|-------------|
+| Stage           | Description                                                                    |
+| --------------- | ------------------------------------------------------------------------------ |
 | **Development** | Experimental features under active development. May be incomplete or unstable. |
-| **Testing** | Feature complete but undergoing testing. Usable but may contain bugs. |
-| **Stable** | Production-ready features. Safe for all deployments. |
-| **Deprecated** | Features scheduled for removal. Migrate away from these. |
+| **Testing**     | Feature complete but undergoing testing. Usable but may contain bugs.          |
+| **Stable**      | Production-ready features. Safe for all deployments.                           |
+| **Deprecated**  | Features scheduled for removal. Migrate away from these.                       |
 
 ---
 

docs/admin_docs/configuration/importing-exporting-datasources.mdx

@@ -148,10 +148,10 @@ datasets by saving the following YAML to file and then running the **import_data
 
 ```yaml
 databases:
-- database_name: main
-  tables:
-  - table_name: random_time_series
-    columns:
-    - column_name: ds
-      verbose_name: datetime
+  - database_name: main
+    tables:
+      - table_name: random_time_series
+        columns:
+          - column_name: ds
+            verbose_name: datetime
 ```

docs/admin_docs/configuration/map-tiles.mdx

@@ -18,7 +18,9 @@ DECKGL_BASE_MAP = [
     ['tile://https://your_personal_url/{z}/{x}/{y}.png', 'MyTile']
 ]
 ```
+
 Openstreetmap tiles url can be added without prefix.
+
 ```python
 DECKGL_BASE_MAP = [
     ['https://c.tile.openstreetmap.org/{z}/{x}/{y}.png', 'OpenStreetMap']
@@ -53,6 +55,7 @@ DECKGL_BASE_MAP = [
 ```
 
 Default values are:
+
 ```python
 DECKGL_BASE_MAP = [
     ['https://tile.openstreetmap.org/{z}/{x}/{y}.png', 'Streets (OSM)'],
@@ -73,6 +76,7 @@ Setting `DECKGL_BASE_MAP` overwrite default values
 :::
 
 After defining your map tiles, set them in these variables:
+
 - `CORS_OPTIONS`
 - `connect-src` of `TALISMAN_CONFIG` and `TALISMAN_CONFIG_DEV` variables.
 

docs/admin_docs/configuration/mcp-server.mdx

@@ -55,11 +55,11 @@ The MCP server runs as a separate process alongside Superset:
 superset mcp run --host 127.0.0.1 --port 5008
 ```
 
-| Flag | Default | Description |
-|------|---------|-------------|
-| `--host` | `127.0.0.1` | Host to bind to |
-| `--port` | `5008` | Port to bind to |
-| `--debug` | off | Enable debug logging |
+| Flag      | Default     | Description          |
+| --------- | ----------- | -------------------- |
+| `--host`  | `127.0.0.1` | Host to bind to      |
+| `--port`  | `5008`      | Port to bind to      |
+| `--debug` | off         | Enable debug logging |
 
 The endpoint is available at `http://<host>:<port>/mcp`.
 
@@ -193,22 +193,24 @@ MCP_JWT_AUDIENCE = "your-audience"
 
 :::warning
 Store `MCP_JWT_SECRET` securely. Never commit it to version control. Use environment variables:
+
 ```python
 import os
 MCP_JWT_SECRET = os.environ.get("MCP_JWT_SECRET")
 ```
+
 :::
 
 #### JWT claims
 
 The MCP server validates these standard claims:
 
-| Claim | Config Key | Description |
-|-------|-----------|-------------|
-| `exp` | -- | Expiration time (always validated) |
-| `iss` | `MCP_JWT_ISSUER` | Token issuer (optional but recommended) |
-| `aud` | `MCP_JWT_AUDIENCE` | Token audience (optional but recommended) |
-| `sub` | -- | Subject -- primary claim used to resolve the Superset user |
+| Claim | Config Key         | Description                                                |
+| ----- | ------------------ | ---------------------------------------------------------- |
+| `exp` | --                 | Expiration time (always validated)                         |
+| `iss` | `MCP_JWT_ISSUER`   | Token issuer (optional but recommended)                    |
+| `aud` | `MCP_JWT_AUDIENCE` | Token audience (optional but recommended)                  |
+| `sub` | --                 | Subject -- primary claim used to resolve the Superset user |
 
 #### User resolution
 
@@ -435,7 +437,7 @@ services:
   superset:
     image: apache/superset:latest
     ports:
-      - "8088:8088"
+      - '8088:8088'
     volumes:
       - ./superset_config.py:/app/superset_config.py
     environment:
@@ -443,9 +445,9 @@ services:
 
   mcp:
     image: apache/superset:latest
-    command: ["superset", "mcp", "run", "--host", "0.0.0.0", "--port", "5008"]
+    command: ['superset', 'mcp', 'run', '--host', '0.0.0.0', '--port', '5008']
     ports:
-      - "5008:5008"
+      - '5008:5008'
     volumes:
       - ./superset_config.py:/app/superset_config.py
     environment:
@@ -494,31 +496,31 @@ All MCP settings go in `superset_config.py`. Defaults are defined in `superset/m
 
 ### Core
 
-| Setting | Default | Description |
-|---------|---------|-------------|
-| `MCP_SERVICE_HOST` | `"localhost"` | Host the MCP server binds to |
-| `MCP_SERVICE_PORT` | `5008` | Port the MCP server binds to |
-| `MCP_SERVICE_URL` | `None` | Public base URL for MCP-generated links (set this when behind a reverse proxy) |
-| `MCP_DEBUG` | `False` | Enable debug logging |
-| `MCP_DEV_USERNAME` | -- | Superset username for development mode (no auth) |
-| `MCP_RBAC_ENABLED` | `True` | Enforce Superset's role-based access control on MCP tool calls. When `True`, each tool checks that the authenticated user has the required FAB permission before executing. Disable only for testing or trusted-network deployments. |
-| `MCP_DISABLED_TOOLS` | `set()` | Set of tool names to remove from the MCP server at startup. Disabled tools are never advertised to AI clients during tool discovery. Useful when a custom extension tool should replace a built-in Superset tool. See [Disabling built-in tools](#disabling-built-in-tools). |
+| Setting              | Default       | Description                                                                                                                                                                                                                                                                  |
+| -------------------- | ------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `MCP_SERVICE_HOST`   | `"localhost"` | Host the MCP server binds to                                                                                                                                                                                                                                                 |
+| `MCP_SERVICE_PORT`   | `5008`        | Port the MCP server binds to                                                                                                                                                                                                                                                 |
+| `MCP_SERVICE_URL`    | `None`        | Public base URL for MCP-generated links (set this when behind a reverse proxy)                                                                                                                                                                                               |
+| `MCP_DEBUG`          | `False`       | Enable debug logging                                                                                                                                                                                                                                                         |
+| `MCP_DEV_USERNAME`   | --            | Superset username for development mode (no auth)                                                                                                                                                                                                                             |
+| `MCP_RBAC_ENABLED`   | `True`        | Enforce Superset's role-based access control on MCP tool calls. When `True`, each tool checks that the authenticated user has the required FAB permission before executing. Disable only for testing or trusted-network deployments.                                         |
+| `MCP_DISABLED_TOOLS` | `set()`       | Set of tool names to remove from the MCP server at startup. Disabled tools are never advertised to AI clients during tool discovery. Useful when a custom extension tool should replace a built-in Superset tool. See [Disabling built-in tools](#disabling-built-in-tools). |
 
 ### Authentication
 
-| Setting | Default | Description |
-|---------|---------|-------------|
-| `MCP_AUTH_ENABLED` | `False` | Enable JWT authentication |
-| `MCP_JWT_ALGORITHM` | `"RS256"` | JWT signing algorithm (`RS256` or `HS256`) |
-| `MCP_JWKS_URI` | `None` | JWKS endpoint URL (RS256) |
-| `MCP_JWT_PUBLIC_KEY` | `None` | Static RSA public key string (RS256) |
-| `MCP_JWT_SECRET` | `None` | Shared secret string (HS256) |
-| `MCP_JWT_ISSUER` | `None` | Expected `iss` claim |
-| `MCP_JWT_AUDIENCE` | `None` | Expected `aud` claim |
-| `MCP_REQUIRED_SCOPES` | `[]` | Required JWT scopes |
-| `MCP_JWT_DEBUG_ERRORS` | `False` | Log detailed JWT errors server-side (never exposed in HTTP responses per RFC 6750) |
-| `MCP_AUTH_FACTORY` | `None` | Custom auth provider factory `(flask_app) -> auth_provider`. Takes precedence over built-in JWT |
-| `MCP_USER_RESOLVER` | `None` | Custom function `(app, access_token) -> username` to extract a Superset username from a validated JWT token. When `None`, the default resolver checks `preferred_username`, `username`, `email`, and `sub` claims in that order. |
+| Setting                | Default   | Description                                                                                                                                                                                                                      |
+| ---------------------- | --------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `MCP_AUTH_ENABLED`     | `False`   | Enable JWT authentication                                                                                                                                                                                                        |
+| `MCP_JWT_ALGORITHM`    | `"RS256"` | JWT signing algorithm (`RS256` or `HS256`)                                                                                                                                                                                       |
+| `MCP_JWKS_URI`         | `None`    | JWKS endpoint URL (RS256)                                                                                                                                                                                                        |
+| `MCP_JWT_PUBLIC_KEY`   | `None`    | Static RSA public key string (RS256)                                                                                                                                                                                             |
+| `MCP_JWT_SECRET`       | `None`    | Shared secret string (HS256)                                                                                                                                                                                                     |
+| `MCP_JWT_ISSUER`       | `None`    | Expected `iss` claim                                                                                                                                                                                                             |
+| `MCP_JWT_AUDIENCE`     | `None`    | Expected `aud` claim                                                                                                                                                                                                             |
+| `MCP_REQUIRED_SCOPES`  | `[]`      | Required JWT scopes                                                                                                                                                                                                              |
+| `MCP_JWT_DEBUG_ERRORS` | `False`   | Log detailed JWT errors server-side (never exposed in HTTP responses per RFC 6750)                                                                                                                                               |
+| `MCP_AUTH_FACTORY`     | `None`    | Custom auth provider factory `(flask_app) -> auth_provider`. Takes precedence over built-in JWT                                                                                                                                  |
+| `MCP_USER_RESOLVER`    | `None`    | Custom function `(app, access_token) -> username` to extract a Superset username from a validated JWT token. When `None`, the default resolver checks `preferred_username`, `username`, `email`, and `sub` claims in that order. |
 
 ### Response Size Guard
 
@@ -539,13 +541,13 @@ MCP_RESPONSE_SIZE_CONFIG = {
 }
 ```
 
-| Key | Default | Description |
-|-----|---------|-------------|
-| `enabled` | `True` | Enable response size checking |
-| `token_limit` | `25000` | Maximum estimated token count per response |
-| `warn_threshold_pct` | `80` | Warn when response exceeds this percentage of the limit |
-| `max_list_items` | `100` | Cap on list-field length (e.g. `charts`, `native_filters`) applied to the `get_*_info` tools before falling back to more aggressive truncation. Raised from a hardcoded 30 in earlier versions; the higher default only keeps more data before the same token-budget fallback kicks in, so it's not a breaking change, but tenants that tuned workflows around the old 30-item cap should lower this value explicitly. |
-| `excluded_tools` | See above | Tools exempt from size checking (e.g., tools that return URLs, not data) |
+| Key                  | Default   | Description                                                                                                                                                                                                                                                                                                                                                                                                            |
+| -------------------- | --------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `enabled`            | `True`    | Enable response size checking                                                                                                                                                                                                                                                                                                                                                                                          |
+| `token_limit`        | `25000`   | Maximum estimated token count per response                                                                                                                                                                                                                                                                                                                                                                             |
+| `warn_threshold_pct` | `80`      | Warn when response exceeds this percentage of the limit                                                                                                                                                                                                                                                                                                                                                                |
+| `max_list_items`     | `100`     | Cap on list-field length (e.g. `charts`, `native_filters`) applied to the `get_*_info` tools before falling back to more aggressive truncation. Raised from a hardcoded 30 in earlier versions; the higher default only keeps more data before the same token-budget fallback kicks in, so it's not a breaking change, but tenants that tuned workflows around the old 30-item cap should lower this value explicitly. |
+| `excluded_tools`     | See above | Tools exempt from size checking (e.g., tools that return URLs, not data)                                                                                                                                                                                                                                                                                                                                               |
 
 ### Caching
 
@@ -571,18 +573,18 @@ MCP_CACHE_CONFIG = {
 }
 ```
 
-| Key | Default | Description |
-|-----|---------|-------------|
-| `enabled` | `False` | Enable response caching |
-| `CACHE_KEY_PREFIX` | `None` | Optional prefix for cache keys (useful for shared Redis) |
-| `list_tools_ttl` | `300` | Cache TTL in seconds for `tools/list` |
-| `list_resources_ttl` | `300` | Cache TTL for `resources/list` |
-| `list_prompts_ttl` | `300` | Cache TTL for `prompts/list` |
-| `read_resource_ttl` | `3600` | Cache TTL for `resources/read` |
-| `get_prompt_ttl` | `3600` | Cache TTL for `prompts/get` |
-| `call_tool_ttl` | `3600` | Cache TTL for `tools/call` |
-| `max_item_size` | `1048576` | Maximum cached item size in bytes (1 MB) |
-| `excluded_tools` | See above | Tools that are never cached (mutating or non-deterministic) |
+| Key                  | Default   | Description                                                 |
+| -------------------- | --------- | ----------------------------------------------------------- |
+| `enabled`            | `False`   | Enable response caching                                     |
+| `CACHE_KEY_PREFIX`   | `None`    | Optional prefix for cache keys (useful for shared Redis)    |
+| `list_tools_ttl`     | `300`     | Cache TTL in seconds for `tools/list`                       |
+| `list_resources_ttl` | `300`     | Cache TTL for `resources/list`                              |
+| `list_prompts_ttl`   | `300`     | Cache TTL for `prompts/list`                                |
+| `read_resource_ttl`  | `3600`    | Cache TTL for `resources/read`                              |
+| `get_prompt_ttl`     | `3600`    | Cache TTL for `prompts/get`                                 |
+| `call_tool_ttl`      | `3600`    | Cache TTL for `tools/call`                                  |
+| `max_item_size`      | `1048576` | Maximum cached item size in bytes (1 MB)                    |
+| `excluded_tools`     | See above | Tools that are never cached (mutating or non-deterministic) |
 
 ### Redis Store (Multi-Pod)
 
@@ -597,12 +599,12 @@ MCP_STORE_CONFIG = {
 }
 ```
 
-| Key | Default | Description |
-|-----|---------|-------------|
-| `enabled` | `False` | Enable Redis-backed store |
-| `CACHE_REDIS_URL` | `None` | Redis connection URL (e.g., `redis://redis-host:6379/0`) |
-| `event_store_max_events` | `100` | Maximum events retained per session |
-| `event_store_ttl` | `3600` | Event TTL in seconds |
+| Key                      | Default | Description                                              |
+| ------------------------ | ------- | -------------------------------------------------------- |
+| `enabled`                | `False` | Enable Redis-backed store                                |
+| `CACHE_REDIS_URL`        | `None`  | Redis connection URL (e.g., `redis://redis-host:6379/0`) |
+| `event_store_max_events` | `100`   | Maximum events retained per session                      |
+| `event_store_ttl`        | `3600`  | Event TTL in seconds                                     |
 
 ### Tool Search
 
@@ -625,15 +627,15 @@ MCP_TOOL_SEARCH_CONFIG = {
 }
 ```
 
-| Key | Default | Description |
-|-----|---------|-------------|
-| `enabled` | `True` | Enable tool search. When `False`, all tools are listed upfront |
-| `strategy` | `"bm25"` | Search ranking algorithm. `"bm25"` supports natural language; `"regex"` supports pattern matching |
-| `max_results` | `5` | Maximum tools returned per search query |
-| `always_visible` | See above | Tools that always appear in `list_tools`, regardless of search |
-| `include_schemas` | `False` | When `False` (default, "summary mode"), search results omit `inputSchema` entirely and include a lightweight `parameters_hint` listing top-level parameter names. Set to `True` to include the full `inputSchema` in search results. Full schemas are always used when a tool is actually invoked via `call_tool`. |
-| `compact_schemas` | `True` | Strip `$defs` / `$ref` and replace with `{"type": "object"}` in search results to reduce token cost. Only takes effect when `include_schemas=True` — ignored in summary mode. |
-| `max_description_length` | `300` | Truncate tool descriptions in search results (0 = no truncation). Applies in both summary and full-schema modes. |
+| Key                      | Default   | Description                                                                                                                                                                                                                                                                                                        |
+| ------------------------ | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `enabled`                | `True`    | Enable tool search. When `False`, all tools are listed upfront                                                                                                                                                                                                                                                     |
+| `strategy`               | `"bm25"`  | Search ranking algorithm. `"bm25"` supports natural language; `"regex"` supports pattern matching                                                                                                                                                                                                                  |
+| `max_results`            | `5`       | Maximum tools returned per search query                                                                                                                                                                                                                                                                            |
+| `always_visible`         | See above | Tools that always appear in `list_tools`, regardless of search                                                                                                                                                                                                                                                     |
+| `include_schemas`        | `False`   | When `False` (default, "summary mode"), search results omit `inputSchema` entirely and include a lightweight `parameters_hint` listing top-level parameter names. Set to `True` to include the full `inputSchema` in search results. Full schemas are always used when a tool is actually invoked via `call_tool`. |
+| `compact_schemas`        | `True`    | Strip `$defs` / `$ref` and replace with `{"type": "object"}` in search results to reduce token cost. Only takes effect when `include_schemas=True` — ignored in summary mode.                                                                                                                                      |
+| `max_description_length` | `300`     | Truncate tool descriptions in search results (0 = no truncation). Applies in both summary and full-schema modes.                                                                                                                                                                                                   |
 
 :::tip
 Set `enabled: False` to revert to the traditional "show all tools at once" behavior, which some clients or workflows may prefer.
@@ -670,16 +672,16 @@ The MCP server respects Superset's full role-based access control (RBAC). Every
 
 Each tool declares one or more required FAB permissions. The table below maps tool groups to their permission requirements:
 
-| Tool group | Required FAB permission |
-|------------|------------------------|
-| `list_charts`, `get_chart_info`, `get_chart_data`, `get_chart_preview`, `generate_chart`, `update_chart` | `can_read` on `Chart` (read), `can_write` on `Chart` (mutate) |
-| `list_dashboards`, `get_dashboard_info`, `generate_dashboard`, `add_chart_to_existing_dashboard` | `can_read` on `Dashboard` (read), `can_write` on `Dashboard` (mutate) |
-| `list_datasets`, `get_dataset_info`, `create_virtual_dataset` | `can_read` on `Dataset` (read), `can_write` on `Dataset` (mutate) |
-| `list_databases`, `get_database_info` | `can_read` on `Database` |
-| `execute_sql` | `can_execute_sql_query` on `SQLLab` |
-| `open_sql_lab_with_context` | `can_read` on `SQLLab` |
-| `save_sql_query` | `can_write` on `SavedQuery` |
-| `health_check` | None (public) |
+| Tool group                                                                                               | Required FAB permission                                               |
+| -------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------- |
+| `list_charts`, `get_chart_info`, `get_chart_data`, `get_chart_preview`, `generate_chart`, `update_chart` | `can_read` on `Chart` (read), `can_write` on `Chart` (mutate)         |
+| `list_dashboards`, `get_dashboard_info`, `generate_dashboard`, `add_chart_to_existing_dashboard`         | `can_read` on `Dashboard` (read), `can_write` on `Dashboard` (mutate) |
+| `list_datasets`, `get_dataset_info`, `create_virtual_dataset`                                            | `can_read` on `Dataset` (read), `can_write` on `Dataset` (mutate)     |
+| `list_databases`, `get_database_info`                                                                    | `can_read` on `Database`                                              |
+| `execute_sql`                                                                                            | `can_execute_sql_query` on `SQLLab`                                   |
+| `open_sql_lab_with_context`                                                                              | `can_read` on `SQLLab`                                                |
+| `save_sql_query`                                                                                         | `can_write` on `SavedQuery`                                           |
+| `health_check`                                                                                           | None (public)                                                         |
 
 To disable RBAC checking globally (for trusted-network deployments or testing), set:
 
@@ -706,13 +708,13 @@ This makes MCP activity fully auditable alongside regular Superset activity. The
 
 Every MCP request passes through a middleware stack before reaching the tool function. The default stack (assembled in `build_middleware_list()` in `server.py`) is:
 
-| Middleware | Purpose | Default |
-|------------|---------|---------|
-| `StructuredContentStripperMiddleware` | Strips `structuredContent` from responses for Claude.ai bridge compatibility | Enabled |
-| `LoggingMiddleware` | Logs each tool call with user, parameters, and duration | Enabled |
-| `GlobalErrorHandlerMiddleware` | Catches unhandled exceptions and sanitizes sensitive data before it reaches the client | Enabled |
-| `ResponseSizeGuardMiddleware` | Estimates token count, warns at 80% of limit, blocks at limit | Enabled (configurable via `MCP_RESPONSE_SIZE_CONFIG`) |
-| `ResponseCachingMiddleware` | Caches read-heavy tool responses (in-memory or Redis) | Disabled (enable via `MCP_CACHE_CONFIG`) |
+| Middleware                            | Purpose                                                                                | Default                                               |
+| ------------------------------------- | -------------------------------------------------------------------------------------- | ----------------------------------------------------- |
+| `StructuredContentStripperMiddleware` | Strips `structuredContent` from responses for Claude.ai bridge compatibility           | Enabled                                               |
+| `LoggingMiddleware`                   | Logs each tool call with user, parameters, and duration                                | Enabled                                               |
+| `GlobalErrorHandlerMiddleware`        | Catches unhandled exceptions and sanitizes sensitive data before it reaches the client | Enabled                                               |
+| `ResponseSizeGuardMiddleware`         | Estimates token count, warns at 80% of limit, blocks at limit                          | Enabled (configurable via `MCP_RESPONSE_SIZE_CONFIG`) |
+| `ResponseCachingMiddleware`           | Caches read-heavy tool responses (in-memory or Redis)                                  | Disabled (enable via `MCP_CACHE_CONFIG`)              |
 
 Additional middleware classes (`RateLimitMiddleware`, `FieldPermissionsMiddleware`, `PrivateToolMiddleware`) are implemented in `superset/mcp_service/middleware.py` but are not added to the default pipeline. They are available for operators who want to layer them in via a custom startup path.
 

docs/admin_docs/configuration/networking-settings.mdx

@@ -8,12 +8,10 @@ version: 1
 
 ## CORS
 
-
 :::note
 In Superset versions prior to `5.x` you have to install to install `flask-cors` with `pip install flask-cors` to enable CORS support.
 :::
 
-
 The following keys in `superset_config.py` can be specified to configure CORS:
 
 - `ENABLE_CORS`: Must be set to `True` in order to enable CORS
@@ -54,11 +52,13 @@ Restart Superset for this configuration change to take effect.
 There are two approaches to making dashboards publicly accessible:
 
 **Option 1: Dataset-based access (simpler)**
+
 1. Set `PUBLIC_ROLE_LIKE = "Public"` in `superset_config.py`
 2. Grant the Public role access to the relevant datasets (Menu → Security → List Roles → Public)
 3. All published dashboards using those datasets become visible to anonymous users
 
 **Option 2: Dashboard-level access (selective control)**
+
 1. Set `PUBLIC_ROLE_LIKE = "Public"` in `superset_config.py`
 2. Add the `'ENABLE_VIEWERS': True` [Feature Flag](/admin-docs/configuration/feature-flags)
 3. Edit each dashboard's properties and add the "Public" role subject as a viewer
@@ -75,7 +75,7 @@ Now anybody can directly access the dashboard's URL. You can embed it in an ifra
   width="600"
   height="400"
   seamless
-  frameBorder="0"
+  frameborder="0"
   scrolling="no"
   src="https://superset.my-domain.com/superset/dashboard/10/?standalone=1&height=400"
 >
@@ -123,17 +123,17 @@ running a custom auth postback endpoint), you can add the endpoints to `WTF_CSRF
 ## SSH Tunneling
 
 1. Turn on feature flag
-    - Change [`SSH_TUNNELING`](https://github.com/apache/superset/blob/eb8386e3f0647df6d1bbde8b42073850796cc16f/superset/config.py#L489) to `True`
-    - If you want to add more security when establishing the tunnel we allow users to overwrite the `SSHTunnelManager` class [here](https://github.com/apache/superset/blob/eb8386e3f0647df6d1bbde8b42073850796cc16f/superset/config.py#L507)
-    - You can also set the [`SSH_TUNNEL_LOCAL_BIND_ADDRESS`](https://github.com/apache/superset/blob/eb8386e3f0647df6d1bbde8b42073850796cc16f/superset/config.py#L508) this the host address where the tunnel will be accessible on your VPC
+   - Change [`SSH_TUNNELING`](https://github.com/apache/superset/blob/eb8386e3f0647df6d1bbde8b42073850796cc16f/superset/config.py#L489) to `True`
+   - If you want to add more security when establishing the tunnel we allow users to overwrite the `SSHTunnelManager` class [here](https://github.com/apache/superset/blob/eb8386e3f0647df6d1bbde8b42073850796cc16f/superset/config.py#L507)
+   - You can also set the [`SSH_TUNNEL_LOCAL_BIND_ADDRESS`](https://github.com/apache/superset/blob/eb8386e3f0647df6d1bbde8b42073850796cc16f/superset/config.py#L508) this the host address where the tunnel will be accessible on your VPC
 
 2. Create database w/ ssh tunnel enabled
-    - With the feature flag enabled you should now see ssh tunnel toggle.
-    - Click the toggle to enable SSH tunneling and add your credentials accordingly.
-        - Superset allows for two different types of authentication (Basic + Private Key). These credentials should come from your service provider.
+   - With the feature flag enabled you should now see ssh tunnel toggle.
+   - Click the toggle to enable SSH tunneling and add your credentials accordingly.
+     - Superset allows for two different types of authentication (Basic + Private Key). These credentials should come from your service provider.
 
 3. Verify data is flowing
-    - Once SSH tunneling has been enabled, go to SQL Lab and write a query to verify data is properly flowing.
+   - Once SSH tunneling has been enabled, go to SQL Lab and write a query to verify data is properly flowing.
 
 ## Domain Sharding
 

docs/admin_docs/configuration/sql-templating.mdx

@@ -90,7 +90,7 @@ In the UI you can assign a set of parameters as JSON
 The parameters become available in your SQL (example: `SELECT * FROM {{ my_table }}` ) by using Jinja templating syntax.
 SQL Lab template parameters are stored with the dataset as `TEMPLATE PARAMETERS`.
 
-There is a special ``_filters`` parameter which can be used to test filters used in the jinja template.
+There is a special `_filters` parameter which can be used to test filters used in the jinja template.
 
 ```json
 {
@@ -111,7 +111,7 @@ WHERE action in {{ filter_values('action_type')|where_in }}
 GROUP BY action
 ```
 
-Note ``_filters`` is not stored with the dataset. It's only used within the SQL Lab UI.
+Note `_filters` is not stored with the dataset. It's only used within the SQL Lab UI.
 
 Besides default Jinja templating, SQL lab also supports self-defined template processor by setting
 the `CUSTOM_TEMPLATE_PROCESSORS` in your superset configuration. The values in this dictionary
@@ -245,16 +245,19 @@ cache key by adding the following parameter to your Jinja code:
 ```
 
 You can json-stringify the array by adding `|tojson` to your Jinja code:
+
 ```python
 {{ current_user_roles()|tojson }}
 ```
 
 You can use the `|where_in` filter to use your roles in a SQL statement. For example, if `current_user_roles()` returns `['admin', 'viewer']`, the following template:
+
 ```python
 SELECT * FROM users WHERE role IN {{ current_user_roles()|where_in }}
 ```
 
 Will be rendered as:
+
 ```sql
 SELECT * FROM users WHERE role IN ('admin', 'viewer')
 ```
@@ -280,6 +283,7 @@ Always treat `url_param()` values as untrusted input. Escaping behaviour varies
 {% if cc not in ('US', 'ES', 'FR') %}{% set cc = 'US' %}{% endif %}
 WHERE country_code = '{{ cc }}'
 ```
+
 :::
 
 Here's a concrete example:
@@ -364,6 +368,7 @@ This is useful if:
     AND full_name LIKE '{{ filter.get('val') | replace("'", "''") }}'
 {%- endif -%}
 ```
+
 :::
 
 Here's a concrete example:
@@ -431,7 +436,7 @@ The macro takes the following parameters:
 - `column`: Name of the temporal column. Leave undefined to reference the time range from a Dashboard Native Time Range
   filter (when present).
 - `default`: The default value to fall back to if the time filter is not present, or has the value `No filter`
-- `target_type`: The target temporal type as recognized by the target  database (e.g. `TIMESTAMP`, `DATE` or
+- `target_type`: The target temporal type as recognized by the target database (e.g. `TIMESTAMP`, `DATE` or
   `DATETIME`). If `column` is defined, the format will default to the type of the column. This is used to produce
   the format of the `from_expr` and `to_expr` properties of the returned `TimeFilter` object.
 - `strftime`: format using the `strftime` method of `datetime` for custom time formatting.
@@ -537,6 +542,7 @@ The parameter can be used in SQL Lab, or when fetching a metric from another dat
 Superset supports [builtin filters from the Jinja2 templating package](https://jinja.palletsprojects.com/en/stable/templates/#builtin-filters). Custom filters have also been implemented:
 
 ### Where In
+
 Parses a list into a SQL-compatible statement. This is useful with macros that return an array (for example the `filter_values` macro):
 
 ```
@@ -556,6 +562,7 @@ Dashboard filter without any value applied
 ### To Datetime
 
 Loads a string as a `datetime` object. This is useful when performing date operations. For example:
+
 ```
 {% set from_expr = get_time_filter("dttm", strftime="%Y-%m-%d").from_expr %}
 {% set to_expr = get_time_filter("dttm", strftime="%Y-%m-%d").to_expr %}
@@ -567,5 +574,6 @@ Loads a string as a `datetime` object. This is useful when performing date opera
 ```
 
 :::resources
+
 - [Blog: Intro to Jinja Templating in Apache Superset](https://preset.io/blog/intro-jinja-templating-apache-superset/)
-:::
+  :::

docs/admin_docs/configuration/theming.mdx

@@ -4,6 +4,7 @@ hide_title: true
 sidebar_position: 12
 version: 1
 ---
+
 # Theming Superset
 
 :::note
@@ -34,11 +35,13 @@ You can also extend with Superset-specific tokens (documented in the default the
 When `ENABLE_UI_THEME_ADMINISTRATION = True` is configured, administrators can manage system-wide themes directly from the UI:
 
 #### Setting System Themes
+
 - **System Default Theme**: Click the sun icon on any theme to set it as the system-wide default
 - **System Dark Theme**: Click the moon icon on any theme to set it as the system dark mode theme
 - **Automatic OS Detection**: When both default and dark themes are set, Superset automatically detects and applies the appropriate theme based on OS preferences
 
 #### Managing System Themes
+
 - System themes are indicated with special badges in the theme list
 - Only administrators with write permissions can modify system theme settings
 - Removing a system theme designation reverts to configuration file defaults
@@ -46,6 +49,7 @@ When `ENABLE_UI_THEME_ADMINISTRATION = True` is configured, administrators can m
 ### Applying Themes to Dashboards
 
 Once created, themes can be applied to individual dashboards:
+
 - Edit any dashboard and select your custom theme from the theme dropdown
 - Each dashboard can have its own theme, allowing for branded or context-specific styling
 
@@ -127,6 +131,7 @@ When `ENABLE_UI_THEME_ADMINISTRATION = True`:
 Superset validates theme JSON when it is saved, either through the UI or via configuration. If a theme contains invalid tokens or an unrecognized structure, Superset logs a warning and falls back to the built-in default theme rather than applying a broken configuration. This prevents a bad theme from rendering the application unusable.
 
 The fallback order is:
+
 1. **UI-configured system theme** (highest priority, if `ENABLE_UI_THEME_ADMINISTRATION = True`)
 2. **`THEME_DEFAULT` / `THEME_DARK`** from `superset_config.py`
 3. **Built-in Superset default theme** (always present as a safety net)
@@ -455,9 +460,10 @@ For programmatic theme management, Superset provides REST endpoints:
 These endpoints require appropriate permissions and are subject to RBAC controls.
 
 :::resources
+
 - [Video: Live Demo — Theming Apache Superset](https://www.youtube.com/watch?v=XsZAsO9tC3o)
 - [CSS and Theming](https://docs.preset.io/docs/css-and-theming) - Additional theming techniques and CSS customization
 - [Blog: Customizing Apache Superset Dashboards with CSS](https://preset.io/blog/customizing-superset-dashboards-with-css/)
 - [Blog: Customizing Dashboards with CSS — Tips and Tricks](https://preset.io/blog/customizing-apache-superset-dashboards-with-css-additional-tips-and-tricks/)
 - [Blog: Customizing Chart Colors](https://preset.io/blog/customizing-chart-colors-with-superset-and-preset/)
-:::
+  :::

docs/admin_docs/installation/architecture.mdx

@@ -5,7 +5,7 @@ sidebar_position: 1
 version: 1
 ---
 
-import useBaseUrl from "@docusaurus/useBaseUrl";
+import useBaseUrl from '@docusaurus/useBaseUrl';
 
 # Architecture
 

docs/admin_docs/installation/docker-builds.mdx

@@ -11,8 +11,7 @@ The Apache Superset community extensively uses Docker for development, release,
 and productionizing Superset. This page details our Docker builds and tag naming
 schemes to help users navigate our offerings.
 
-Images are built and pushed to the [Superset Docker Hub repository](
-https://hub.docker.com/r/apache/superset) using GitHub Actions.
+Images are built and pushed to the [Superset Docker Hub repository](https://hub.docker.com/r/apache/superset) using GitHub Actions.
 Different sets of images are built and/or published at different times:
 
 - **Published releases** (`release`): published using

docs/admin_docs/installation/docker-compose.mdx

@@ -5,12 +5,13 @@ sidebar_position: 5
 version: 1
 ---
 
-import useBaseUrl from "@docusaurus/useBaseUrl";
+import useBaseUrl from '@docusaurus/useBaseUrl';
 
 # Using Docker Compose
 
-<img src={useBaseUrl("/img/docker-compose.webp" )} width="150" />
-<br /><br />
+<img src={useBaseUrl('/img/docker-compose.webp')} width="150" />
+<br />
+<br />
 
 :::caution
 Since `docker compose` is primarily designed to run a set of containers on **a single host**
@@ -29,23 +30,23 @@ way to launch a fully functioning **development environment** quickly.
 Note that there are 4 major ways we support to run `docker compose`:
 
 1. **docker-compose.yml:** for interactive development, where we mount your local folder with the
-  frontend/backend files that you can edit and experience the changes you
-  make in the app in real time
+   frontend/backend files that you can edit and experience the changes you
+   make in the app in real time
 1. **docker-compose-light.yml:** a lightweight configuration with minimal services (database,
-  Superset app, and frontend dev server) for development. Uses in-memory caching instead of Redis
-  and is designed for running multiple instances simultaneously
+   Superset app, and frontend dev server) for development. Uses in-memory caching instead of Redis
+   and is designed for running multiple instances simultaneously
 1. **docker-compose-non-dev.yml** where we just build a more immutable image based on the
-  local branch and get all the required images running. Changes in the local branch
-  at the time you fire this up will be reflected, but changes to the code
-  while `up` won't be reflected in the app
+   local branch and get all the required images running. Changes in the local branch
+   at the time you fire this up will be reflected, but changes to the code
+   while `up` won't be reflected in the app
 1. **docker-compose-image-tag.yml** where we fetch an image from docker-hub say for the
-  `5.0.0` release for instance, and fire it up so you can try it. Here what's in
-  the local branch has no effects on what's running, we just fetch and run
-  pre-built images from docker-hub. For `docker compose` to work along with the
-  Postgres image it boots up, you'll want to point to a `-dev`-suffixed TAG, as in
-  `export TAG=5.0.0-dev` or `export TAG=4.1.2-dev`, with `latest-dev` being the default.
-  The `dev` builds include the `psycopg2-binary` required to connect
-  to the Postgres database launched as part of the `docker compose` builds.
+   `5.0.0` release for instance, and fire it up so you can try it. Here what's in
+   the local branch has no effects on what's running, we just fetch and run
+   pre-built images from docker-hub. For `docker compose` to work along with the
+   Postgres image it boots up, you'll want to point to a `-dev`-suffixed TAG, as in
+   `export TAG=5.0.0-dev` or `export TAG=4.1.2-dev`, with `latest-dev` being the default.
+   The `dev` builds include the `psycopg2-binary` required to connect
+   to the Postgres database launched as part of the `docker compose` builds.
 
 More on these approaches after setting up the requirements for either.
 
@@ -92,7 +93,7 @@ like to try out Superset without making any code changes follow the steps docume
 :::tip
 By default, we mount the local superset-frontend folder here and run `npm install` as well
 as `npm run dev` which triggers webpack to compile/bundle the frontend code. Depending
-on your local setup, especially if you have less than 16GB of memory,  it may be very slow to
+on your local setup, especially if you have less than 16GB of memory, it may be very slow to
 perform those operations. In this case, we recommend you set the env var
 `BUILD_SUPERSET_FRONTEND_IN_DOCKER` to `false`, and to run this locally instead in a terminal.
 Simply trigger `npm i && npm run dev`, this should be MUCH faster.
@@ -121,6 +122,7 @@ NODE_PORT=9003 docker compose -p superset-3 -f docker-compose-light.yml up
 ```
 
 This configuration includes:
+
 - PostgreSQL database (internal network only)
 - Superset application server
 - Frontend development server with webpack hot reloading
@@ -165,7 +167,7 @@ looking to fire up.
 
 :::caution
 All of the content belonging to a Superset instance - charts, dashboards, users, etc. - is stored in
-its metadata database. In production, this database should be backed up.  The default installation
+its metadata database. In production, this database should be backed up. The default installation
 with docker compose will store that data in a PostgreSQL database contained in a Docker
 [volume](https://docs.docker.com/storage/volumes/), which is not backed up.
 
@@ -174,7 +176,7 @@ Again, **THE DOCKER-COMPOSE INSTALLATION IS NOT PRODUCTION-READY OUT OF THE BOX.
 :::
 
 You should see a stream of logging output from the containers being launched on your machine. Once
-this output slows, you should have a running instance of Superset on your local machine!  To avoid
+this output slows, you should have a running instance of Superset on your local machine! To avoid
 the wall of text on future runs, add the `-d` option to the end of the `docker compose up` command.
 
 ### Configuring Further
@@ -259,24 +261,24 @@ Superset (which is running in its docker container). Other databases may have sl
 configurations but gist would be same and boils down to 2 steps -
 
 1. **(Mac users may skip this step)** Configuring the local postgresql/database instance to accept
-public incoming connections. By default, postgresql only allows incoming connections from
-`localhost` and under Docker, unless you use `--network=host`, `localhost` will refer to different
-endpoints on the host machine and in a docker container respectively. Allowing postgresql to accept
-connections from the Docker involves making one-line changes to the files `postgresql.conf` and
-`pg_hba.conf`; you can find helpful links tailored to your OS / PG version on the web easily for
-this task. For Docker it suffices to only whitelist IPs `172.0.0.0/8` instead of `*`, but in any
-case you are _warned_ that doing this in a production database _may_ have disastrous consequences as
-you are opening your database to the public internet.
+   public incoming connections. By default, postgresql only allows incoming connections from
+   `localhost` and under Docker, unless you use `--network=host`, `localhost` will refer to different
+   endpoints on the host machine and in a docker container respectively. Allowing postgresql to accept
+   connections from the Docker involves making one-line changes to the files `postgresql.conf` and
+   `pg_hba.conf`; you can find helpful links tailored to your OS / PG version on the web easily for
+   this task. For Docker it suffices to only whitelist IPs `172.0.0.0/8` instead of `*`, but in any
+   case you are _warned_ that doing this in a production database _may_ have disastrous consequences as
+   you are opening your database to the public internet.
 1. Instead of `localhost`, try using `host.docker.internal` (Mac users, Ubuntu) or `172.18.0.1`
-(Linux users) as the hostname when attempting to connect to the database. This is a Docker internal
-detail -- what is happening is that, in Mac systems, Docker Desktop creates a dns entry for the
-hostname `host.docker.internal` which resolves to the correct address for the host machine, whereas
-in Linux this is not the case (at least by default). If neither of these 2 hostnames work then you
-may want to find the exact hostname you want to use, for that you can do `ifconfig` or
-`ip addr show` and look at the IP address of `docker0` interface that must have been created by
-Docker for you. Alternately if you don't even see the `docker0` interface try (if needed with sudo)
-`docker network inspect bridge` and see if there is an entry for `"Gateway"` and note the IP
-address.
+   (Linux users) as the hostname when attempting to connect to the database. This is a Docker internal
+   detail -- what is happening is that, in Mac systems, Docker Desktop creates a dns entry for the
+   hostname `host.docker.internal` which resolves to the correct address for the host machine, whereas
+   in Linux this is not the case (at least by default). If neither of these 2 hostnames work then you
+   may want to find the exact hostname you want to use, for that you can do `ifconfig` or
+   `ip addr show` and look at the IP address of `docker0` interface that must have been created by
+   Docker for you. Alternately if you don't even see the `docker0` interface try (if needed with sudo)
+   `docker network inspect bridge` and see if there is an entry for `"Gateway"` and note the IP
+   address.
 
 ## 4. To build or not to build
 

docs/admin_docs/installation/installation-methods.mdx

@@ -5,7 +5,7 @@ sidebar_position: 2
 version: 1
 ---
 
-import useBaseUrl from "@docusaurus/useBaseUrl";
+import useBaseUrl from '@docusaurus/useBaseUrl';
 
 # Installation Methods
 

docs/admin_docs/installation/kubernetes.mdx

@@ -1,16 +1,17 @@
 ---
-title:  Kubernetes
+title: Kubernetes
 hide_title: true
 sidebar_position: 3
 version: 1
 ---
 
-import useBaseUrl from "@docusaurus/useBaseUrl";
+import useBaseUrl from '@docusaurus/useBaseUrl';
 
 # Installing on Kubernetes
 
-<img src={useBaseUrl("/img/k8s.png" )} width="150" />
-<br /><br />
+<img src={useBaseUrl('/img/k8s.png')} width="150" />
+<br />
+<br />
 
 Running Superset on Kubernetes is supported with the provided [Helm](https://helm.sh/) chart
 found in the official [Superset helm repository](https://apache.github.io/superset/index.yaml).
@@ -134,7 +135,7 @@ init:
 ```
 
 :::note
-Superset uses [Scarf Gateway](https://about.scarf.sh/scarf-gateway) to collect telemetry data.  Knowing the installation counts for different Superset versions informs the  project's decisions about patching and long-term support. Scarf purges personally identifiable information (PII) and provides only aggregated statistics.
+Superset uses [Scarf Gateway](https://about.scarf.sh/scarf-gateway) to collect telemetry data. Knowing the installation counts for different Superset versions informs the project's decisions about patching and long-term support. Scarf purges personally identifiable information (PII) and provides only aggregated statistics.
 
 There are two independent telemetry channels:
 
@@ -143,11 +144,11 @@ There are two independent telemetry channels:
 
   ```yaml
   extraEnv:
-    SCARF_ANALYTICS: "false"
+    SCARF_ANALYTICS: 'false'
   ```
 
   This is read at runtime, so it takes effect on the pre-built images without rebuilding the frontend.
-:::
+  :::
 
 ### Dependencies
 
@@ -205,7 +206,7 @@ Those can be passed as key/values either with `extraEnv` or `extraSecretEnv` if
 extraEnv:
   SMTP_HOST: smtp.gmail.com
   SMTP_USER: user@gmail.com
-  SMTP_PORT: "587"
+  SMTP_PORT: '587'
   SMTP_MAIL_FROM: user@gmail.com
 
 extraSecretEnv:
@@ -366,7 +367,7 @@ supersetCeleryBeat:
 extraEnv:
   SMTP_HOST: smtp.gmail.com
   SMTP_USER: user@gmail.com
-  SMTP_PORT: "587"
+  SMTP_PORT: '587'
   SMTP_MAIL_FROM: user@gmail.com
 
 extraSecretEnv:
@@ -456,6 +457,7 @@ init:
 ```
 
 :::resources
+
 - [Tutorial: Mastering Data Visualization — Installing Superset on Kubernetes with Helm Chart](https://mahira-technology.medium.com/mastering-data-visualization-installing-superset-on-kubernetes-cluster-using-helm-chart-e4ec99199e1e)
 - [Tutorial: Installing Apache Superset in Kubernetes](https://aws.plainenglish.io/installing-apache-superset-in-kubernetes-1aec192ac495)
-:::
+  :::

docs/admin_docs/installation/pypi.mdx

@@ -5,12 +5,13 @@ sidebar_position: 4
 version: 1
 ---
 
-import useBaseUrl from "@docusaurus/useBaseUrl";
+import useBaseUrl from '@docusaurus/useBaseUrl';
 
 # Installing Superset from PyPI
 
-<img src={useBaseUrl("/img/pypi.png" )} width="150" />
-<br /><br />
+<img src={useBaseUrl('/img/pypi.png')} width="150" />
+<br />
+<br />
 
 This page describes how to install Superset using the `apache_superset` package [published on PyPI](https://pypi.org/project/apache_superset/).
 
@@ -126,6 +127,7 @@ pip install apache_superset
 ```
 
 Then, define mandatory configurations, SECRET_KEY and FLASK_APP:
+
 ```bash
 export SUPERSET_SECRET_KEY=YOUR-SECRET-KEY # For production use, make sure this is a strong key, for example generated using `openssl rand -base64 42`. See https://superset.apache.org/admin-docs/configuration/configuring-superset#specifying-a-secret_key
 export FLASK_APP=superset

docs/admin_docs/installation/upgrading-superset.mdx

@@ -55,6 +55,7 @@ For a detailed list of breaking changes and migration notes for each version, se
 
 This file documents backwards-incompatible changes and provides guidance for migrating between
 major versions, including:
+
 - Configuration changes
 - API changes
 - Database migrations

docs/admin_docs/security/cves.mdx

@@ -2,41 +2,42 @@
 title: CVEs fixed by release
 sidebar_position: 2
 ---
+
 #### Version 6.0.0
 
-| CVE            | Title                                                                              | Affected |
-|:---------------|:-----------------------------------------------------------------------------------|---------:|
-| CVE-2026-23980 | Improper Neutralization of Special Elements used in a SQL Command                  |  < 6.0.0 |
-| CVE-2026-23982 | Improper Authorization in Dataset Creation Allows Access Control Bypass            |  < 6.0.0 |
-| CVE-2026-23983 | Information Disclosure of sensitive user info via Tags                             |  < 6.0.0 |
-| CVE-2026-23984 | SQLLab Read-Only Bypass on PostgreSQL (DML execution)                              |  < 6.0.0 |
+| CVE            | Title                                                                   | Affected |
+| :------------- | :---------------------------------------------------------------------- | -------: |
+| CVE-2026-23980 | Improper Neutralization of Special Elements used in a SQL Command       |  < 6.0.0 |
+| CVE-2026-23982 | Improper Authorization in Dataset Creation Allows Access Control Bypass |  < 6.0.0 |
+| CVE-2026-23983 | Information Disclosure of sensitive user info via Tags                  |  < 6.0.0 |
+| CVE-2026-23984 | SQLLab Read-Only Bypass on PostgreSQL (DML execution)                   |  < 6.0.0 |
 
 #### Version 5.0.0
 
-| CVE            | Title                                                                              | Affected |
-|:---------------|:-----------------------------------------------------------------------------------|---------:|
-| CVE-2025-55673 | Exposure of Sensitive Information to an Unauthorized Actor                         |  < 5.0.0 |
-| CVE-2025-55674 | Improper Neutralization of Special Elements used in an SQL Command                 |  < 5.0.0 |
-| CVE-2025-55675 | Improper Access Control leading to Information Disclosure                          |  < 5.0.0 |
+| CVE            | Title                                                              | Affected |
+| :------------- | :----------------------------------------------------------------- | -------: |
+| CVE-2025-55673 | Exposure of Sensitive Information to an Unauthorized Actor         |  < 5.0.0 |
+| CVE-2025-55674 | Improper Neutralization of Special Elements used in an SQL Command |  < 5.0.0 |
+| CVE-2025-55675 | Improper Access Control leading to Information Disclosure          |  < 5.0.0 |
 
 #### Version 4.1.3
 
-| CVE            | Title                                                                              | Affected |
-|:---------------|:-----------------------------------------------------------------------------------|---------:|
-| CVE-2025-55672 | Improper Neutralization of Input During Web Page Generation                        |  < 4.1.3 |
+| CVE            | Title                                                       | Affected |
+| :------------- | :---------------------------------------------------------- | -------: |
+| CVE-2025-55672 | Improper Neutralization of Input During Web Page Generation |  < 4.1.3 |
 
 #### Version 4.1.2
 
-| CVE            | Title                                                                              | Affected |
-|:---------------|:-----------------------------------------------------------------------------------|---------:|
-| CVE-2025-27696 | Improper authorization leading to resource ownership takeover                      |  < 4.1.2 |
-| CVE-2025-48912 | Improper authorization bypass on row level security via SQL Injection              |  < 4.1.2 |
-| CVE-2026-23969 | Exposure of Sensitive Information via Incomplete ClickHouse Function Filtering     |  < 4.1.2 |
+| CVE            | Title                                                                          | Affected |
+| :------------- | :----------------------------------------------------------------------------- | -------: |
+| CVE-2025-27696 | Improper authorization leading to resource ownership takeover                  |  < 4.1.2 |
+| CVE-2025-48912 | Improper authorization bypass on row level security via SQL Injection          |  < 4.1.2 |
+| CVE-2026-23969 | Exposure of Sensitive Information via Incomplete ClickHouse Function Filtering |  < 4.1.2 |
 
 #### Version 4.1.0
 
 | CVE            | Title                                                                              | Affected |
-|:---------------|:-----------------------------------------------------------------------------------|---------:|
+| :------------- | :--------------------------------------------------------------------------------- | -------: |
 | CVE-2024-53947 | Improper SQL authorisation, parse for specific postgres functions                  |  < 4.1.0 |
 | CVE-2024-53948 | Error verbosity exposes metadata in analytics databases                            |  < 4.1.0 |
 | CVE-2024-53949 | Lower privilege users are able to create Role when FAB_ADD_SECURITY_API is enabled |  < 4.1.0 |
@@ -44,84 +45,84 @@ sidebar_position: 2
 
 #### Version 4.0.2
 
-| CVE            | Title                       | Affected |
-|:---------------|:----------------------------|---------:|
-| CVE-2024-39887 | Improper SQL authorization  |  < 4.0.1 |
+| CVE            | Title                      | Affected |
+| :------------- | :------------------------- | -------: |
+| CVE-2024-39887 | Improper SQL authorization |  < 4.0.1 |
 
 #### Version 3.1.3, 4.0.1
 
-| CVE            | Title                       |                    Affected |
-|:---------------|:----------------------------|----------------------------:|
-| CVE-2024-34693 | Server arbitrary file read  |  < 3.1.3, >= 4.0.0, < 4.0.1 |
+| CVE            | Title                      |                   Affected |
+| :------------- | :------------------------- | -------------------------: |
+| CVE-2024-34693 | Server arbitrary file read | < 3.1.3, >= 4.0.0, < 4.0.1 |
 
 #### Version 3.1.2
 
-| CVE            | Title                                                   | Affected |
-|:---------------|:--------------------------------------------------------|---------:|
-| CVE-2024-28148 | Incorrect datasource authorization on explore REST API  |  < 3.1.2 |
+| CVE            | Title                                                  | Affected |
+| :------------- | :----------------------------------------------------- | -------: |
+| CVE-2024-28148 | Incorrect datasource authorization on explore REST API |  < 3.1.2 |
 
 #### Version 3.0.4, 3.1.1
 
-| CVE            | Title                                                                        |                    Affected |
-|:---------------|:-----------------------------------------------------------------------------|----------------------------:|
-| CVE-2024-27315 | Improper error handling on alerts                                            |  < 3.0.4, >= 3.1.0, < 3.1.1 |
-| CVE-2024-24773 | Improper validation of SQL statements allows for unauthorized access to data |  < 3.0.4, >= 3.1.0, < 3.1.1 |
-| CVE-2024-24772 | Improper Neutralisation of custom SQL on embedded context                    |  < 3.0.4, >= 3.1.0, < 3.1.1 |
-| CVE-2024-24779 | Improper data authorization when creating a new dataset                      |  < 3.0.4, >= 3.1.0, < 3.1.1 |
-| CVE-2024-26016 | Improper authorization validation on dashboards and charts import            |  < 3.0.4, >= 3.1.0, < 3.1.1 |
+| CVE            | Title                                                                        |                   Affected |
+| :------------- | :--------------------------------------------------------------------------- | -------------------------: |
+| CVE-2024-27315 | Improper error handling on alerts                                            | < 3.0.4, >= 3.1.0, < 3.1.1 |
+| CVE-2024-24773 | Improper validation of SQL statements allows for unauthorized access to data | < 3.0.4, >= 3.1.0, < 3.1.1 |
+| CVE-2024-24772 | Improper Neutralisation of custom SQL on embedded context                    | < 3.0.4, >= 3.1.0, < 3.1.1 |
+| CVE-2024-24779 | Improper data authorization when creating a new dataset                      | < 3.0.4, >= 3.1.0, < 3.1.1 |
+| CVE-2024-26016 | Improper authorization validation on dashboards and charts import            | < 3.0.4, >= 3.1.0, < 3.1.1 |
 
 #### Version 3.0.3
 
 | CVE            | Title                                         | Affected |
-|:---------------|:----------------------------------------------|---------:|
+| :------------- | :-------------------------------------------- | -------: |
 | CVE-2023-49657 | Stored XSS in Dashboard Title and Chart Title |  < 3.0.3 |
 
 #### Version 3.0.2, 2.1.3
 
 | CVE            | Title                                                       |                   Affected |
-|:---------------|:------------------------------------------------------------|---------------------------:|
+| :------------- | :---------------------------------------------------------- | -------------------------: |
 | CVE-2023-46104 | Allows for uncontrolled resource consumption via a ZIP bomb | < 2.1.3, >= 3.0.0, < 3.0.2 |
 | CVE-2023-49736 | SQL Injection on where_in JINJA macro                       | < 2.1.3, >= 3.0.0, < 3.0.2 |
 | CVE-2023-49734 | Privilege Escalation Vulnerability                          | < 2.1.3, >= 3.0.0, < 3.0.2 |
 
 #### Version 3.0.0
 
-| CVE            | Title                                                                   | Affected |
-|:---------------|:------------------------------------------------------------------------|---------:|
-| CVE-2023-42502 | Open Redirect Vulnerability                                             |  < 3.0.0 |
-| CVE-2023-42505 | Sensitive information disclosure on db connection details               |  < 3.0.0 |
+| CVE            | Title                                                     | Affected |
+| :------------- | :-------------------------------------------------------- | -------: |
+| CVE-2023-42502 | Open Redirect Vulnerability                               |  < 3.0.0 |
+| CVE-2023-42505 | Sensitive information disclosure on db connection details |  < 3.0.0 |
 
 #### Version 2.1.3
 
-| CVE            | Title                                                                   | Affected |
-|:---------------|:------------------------------------------------------------------------|---------:|
-| CVE-2023-42504 | Lack of rate limiting allows for possible denial of service             |  < 2.1.3 |
+| CVE            | Title                                                       | Affected |
+| :------------- | :---------------------------------------------------------- | -------: |
+| CVE-2023-42504 | Lack of rate limiting allows for possible denial of service |  < 2.1.3 |
 
 #### Version 2.1.2
 
-| CVE            | Title                                                                   | Affected |
-|:---------------|:------------------------------------------------------------------------|---------:|
-| CVE-2023-40610 | Privilege escalation with default examples database                     |  < 2.1.2 |
-| CVE-2023-42501 | Unnecessary read permissions within the Gamma role                      |  < 2.1.2 |
-| CVE-2023-43701 | Stored XSS on API endpoint                                              |  < 2.1.2 |
+| CVE            | Title                                               | Affected |
+| :------------- | :-------------------------------------------------- | -------: |
+| CVE-2023-40610 | Privilege escalation with default examples database |  < 2.1.2 |
+| CVE-2023-42501 | Unnecessary read permissions within the Gamma role  |  < 2.1.2 |
+| CVE-2023-43701 | Stored XSS on API endpoint                          |  < 2.1.2 |
 
 #### Version 2.1.1
 
-| CVE            | Title                                                                   | Affected |
-|:---------------|:------------------------------------------------------------------------|---------:|
-| CVE-2023-36387 | Improper API permission for low privilege users                         |  < 2.1.1 |
-| CVE-2023-36388 | Improper API permission for low privilege users allows for SSRF         |  < 2.1.1 |
-| CVE-2023-27523 | Improper data permission validation on Jinja templated queries          |  < 2.1.1 |
-| CVE-2023-27526 | Improper Authorization check on import charts                           |  < 2.1.1 |
-| CVE-2023-39264 | Stack traces enabled by default                                         |  < 2.1.1 |
-| CVE-2023-39265 | Possible Unauthorized Registration of SQLite Database Connections       |  < 2.1.1 |
-| CVE-2023-37941 | Metadata db write access can lead to remote code execution              |  < 2.1.1 |
-| CVE-2023-32672 | SQL parser edge case bypasses data access authorization                 |  < 2.1.1 |
+| CVE            | Title                                                             | Affected |
+| :------------- | :---------------------------------------------------------------- | -------: |
+| CVE-2023-36387 | Improper API permission for low privilege users                   |  < 2.1.1 |
+| CVE-2023-36388 | Improper API permission for low privilege users allows for SSRF   |  < 2.1.1 |
+| CVE-2023-27523 | Improper data permission validation on Jinja templated queries    |  < 2.1.1 |
+| CVE-2023-27526 | Improper Authorization check on import charts                     |  < 2.1.1 |
+| CVE-2023-39264 | Stack traces enabled by default                                   |  < 2.1.1 |
+| CVE-2023-39265 | Possible Unauthorized Registration of SQLite Database Connections |  < 2.1.1 |
+| CVE-2023-37941 | Metadata db write access can lead to remote code execution        |  < 2.1.1 |
+| CVE-2023-32672 | SQL parser edge case bypasses data access authorization           |  < 2.1.1 |
 
 #### Version 2.1.0
 
 | CVE            | Title                                                                   | Affected |
-|:---------------|:------------------------------------------------------------------------|---------:|
+| :------------- | :---------------------------------------------------------------------- | -------: |
 | CVE-2023-25504 | Possible SSRF on import datasets                                        |  < 2.1.0 |
 | CVE-2023-27524 | Session validation vulnerability when using provided default SECRET_KEY |  < 2.1.0 |
 | CVE-2023-27525 | Incorrect default permissions for Gamma role                            |  < 2.1.0 |
@@ -129,8 +130,8 @@ sidebar_position: 2
 
 #### Version 2.0.1
 
-| CVE            | Title                                                       |          Affected  |
-|:---------------|:------------------------------------------------------------|------------------: |
+| CVE            | Title                                                       |           Affected |
+| :------------- | :---------------------------------------------------------- | -----------------: |
 | CVE-2022-41703 | SQL injection vulnerability in adhoc clauses                | < 2.0.1 or < 1.5.2 |
 | CVE-2022-43717 | Cross-Site Scripting on dashboards                          | < 2.0.1 or < 1.5.2 |
 | CVE-2022-43718 | Cross-Site Scripting vulnerability on upload forms          | < 2.0.1 or < 1.5.2 |

docs/admin_docs/security/securing_superset.mdx

@@ -3,7 +3,7 @@ title: Securing Your Superset Installation for Production
 sidebar_position: 3
 ---
 
-> *This guide applies to Apache Superset version 4.0 and later and is an evolving set of best practices that administrators should adapt to their specific deployment architecture.*
+> _This guide applies to Apache Superset version 4.0 and later and is an evolving set of best practices that administrators should adapt to their specific deployment architecture._
 
 The default Apache Superset configuration is optimized for ease of use and development, not for security. For any production deployment, it is **critical** that you review and apply the following security configurations to harden your instance, protect user data, and prevent unauthorized access.
 
@@ -13,25 +13,25 @@ This guide provides a comprehensive checklist of essential security configuratio
 
 Running Superset without HTTPS (TLS) is not secure. Without it, all network traffic—including user credentials, session tokens, and sensitive data—is sent in cleartext and can be easily intercepted.
 
-* **Use a Reverse Proxy:** Your Superset instance should always be deployed behind a reverse proxy (e.g., Nginx, Traefik) or a load balancer (e.g., AWS ALB, Google Cloud Load Balancer) that is configured to handle HTTPS termination.
-* **Enforce Modern TLS:** Configure your proxy to enforce TLS 1.2 or higher with strong, industry-standard cipher suites.
-* **Implement HSTS:** Use the HTTP Strict Transport Security (HSTS) header to ensure browsers only connect to your Superset instance over HTTPS. This can be configured in your reverse proxy or within Superset's Talisman settings.
+- **Use a Reverse Proxy:** Your Superset instance should always be deployed behind a reverse proxy (e.g., Nginx, Traefik) or a load balancer (e.g., AWS ALB, Google Cloud Load Balancer) that is configured to handle HTTPS termination.
+- **Enforce Modern TLS:** Configure your proxy to enforce TLS 1.2 or higher with strong, industry-standard cipher suites.
+- **Implement HSTS:** Use the HTTP Strict Transport Security (HSTS) header to ensure browsers only connect to your Superset instance over HTTPS. This can be configured in your reverse proxy or within Superset's Talisman settings.
 
 ### **`SUPERSET_SECRET_KEY` Management (CRITICAL)**
 
 This is the most critical security setting for your Superset instance. It is used to sign all session cookies and encrypt sensitive information in the metadata database, such as database connection credentials.
 
-* **Generate a Unique, Strong Key:** A unique key must be generated for every Superset instance. Use a cryptographically secure method to create it.
-    ```bash
-    # Example using openssl to generate a strong key
-    openssl rand -base64 42
-    ```
-* **Store the Key Securely:** The key must be kept confidential. The recommended approach is to store it as an environment variable or in a secrets management system (e.g., AWS Secrets Manager, HashiCorp Vault). **Do not hardcode the key in `superset_config.py` or commit it to version control.**
-    ```python
-    # In superset_config.py
-    import os
-    SECRET_KEY = os.environ.get('SUPERSET_SECRET_KEY')
-    ```
+- **Generate a Unique, Strong Key:** A unique key must be generated for every Superset instance. Use a cryptographically secure method to create it.
+  ```bash
+  # Example using openssl to generate a strong key
+  openssl rand -base64 42
+  ```
+- **Store the Key Securely:** The key must be kept confidential. The recommended approach is to store it as an environment variable or in a secrets management system (e.g., AWS Secrets Manager, HashiCorp Vault). **Do not hardcode the key in `superset_config.py` or commit it to version control.**
+  ```python
+  # In superset_config.py
+  import os
+  SECRET_KEY = os.environ.get('SUPERSET_SECRET_KEY')
+  ```
 
 > #### ⚠️ Warning: Your `SUPERSET_SECRET_KEY` Must Be Unique
 >
@@ -75,7 +75,7 @@ SESSION_USE_SIGNER = True
 
 #### **Configure Session Lifetime and Cookie Security Flags**
 
-This is mandatory for *all* deployments, whether stateless or server-side.
+This is mandatory for _all_ deployments, whether stateless or server-side.
 
 ```python
 # superset_config.py
@@ -92,7 +92,8 @@ SESSION_COOKIE_SAMESITE = 'Lax'   # Provide protection against CSRF attacks
 ```
 
 > ##### Note on iFrame Embedding and `SESSION_COOKIE_SAMESITE`
->The recommended default setting `'Lax'` provides good CSRF protection for most use cases. However, if you need to embed Superset dashboards into other applications using an iFrame, you will need to change this setting to `'None'`.
+>
+> The recommended default setting `'Lax'` provides good CSRF protection for most use cases. However, if you need to embed Superset dashboards into other applications using an iFrame, you will need to change this setting to `'None'`.
 
 SESSION_COOKIE_SAMESITE = 'None'
 
@@ -102,9 +103,9 @@ Setting SameSite to 'None' requires that SESSION_COOKIE_SECURE is also set to Tr
 
 While Superset's built-in database authentication is convenient, for production it's highly recommended to integrate with an enterprise-grade identity provider (IdP).
 
-  * **Use an Enterprise IdP:** Configure authentication via OAuth or LDAP to leverage your organization's existing identity management system. This provides benefits like Single Sign-On (SSO), Multi-Factor Authentication (MFA), and centralized user provisioning/deprovisioning.
-  * **Principle of Least Privilege:** Assign users to the most restrictive roles necessary for their jobs. Avoid over-provisioning users with Admin or Alpha roles, and ensure row-level security is applied where appropriate.
-  * **Admin Accounts:** Delete or disable the default admin user after a new administrative account has been configured.
+- **Use an Enterprise IdP:** Configure authentication via OAuth or LDAP to leverage your organization's existing identity management system. This provides benefits like Single Sign-On (SSO), Multi-Factor Authentication (MFA), and centralized user provisioning/deprovisioning.
+- **Principle of Least Privilege:** Assign users to the most restrictive roles necessary for their jobs. Avoid over-provisioning users with Admin or Alpha roles, and ensure row-level security is applied where appropriate.
+- **Admin Accounts:** Delete or disable the default admin user after a new administrative account has been configured.
 
 ### **Content Security Policy (CSP) and Other Headers**
 
@@ -122,48 +123,48 @@ Here's the documentation section how how to set up Talisman: https://superset.ap
 >
 > It is essential to understand that **Apache Superset is a data visualization and exploration platform, not a database firewall or a comprehensive security solution for your data warehouse.** While Superset provides features to help manage data access, the ultimate responsibility for securing your underlying databases lies with your database administrators (DBAs) and security teams. This includes managing network access, user privileges, and fine-grained permissions directly within the database. The configurations below are an important secondary layer of security but should not be your only line of defense.
 
-  * **Use a Dedicated Database User:** The database connection configured in Superset should use a dedicated, limited-privilege database user. This user should only have the minimum required permissions (e.g., `SELECT` on specific schemas) for the data sources it needs to query. It should **not** have `INSERT`, `UPDATE`, `DELETE`, or administrative privileges.
-  * **Restrict Dangerous SQL Functions:** To mitigate potential SQL injection risks, configure the `DISALLOWED_SQL_FUNCTIONS` list in your `superset_config.py`. Be aware that this is a defense-in-depth measure, not a substitute for proper database permissions.
+- **Use a Dedicated Database User:** The database connection configured in Superset should use a dedicated, limited-privilege database user. This user should only have the minimum required permissions (e.g., `SELECT` on specific schemas) for the data sources it needs to query. It should **not** have `INSERT`, `UPDATE`, `DELETE`, or administrative privileges.
+- **Restrict Dangerous SQL Functions:** To mitigate potential SQL injection risks, configure the `DISALLOWED_SQL_FUNCTIONS` list in your `superset_config.py`. Be aware that this is a defense-in-depth measure, not a substitute for proper database permissions.
 
 ### **Additional Security Layers**
 
-  * **Web Application Firewall (WAF):** Deploying Superset behind a WAF (e.g., Cloudflare, AWS WAF) is strongly recommended. A WAF with a standard ruleset (like the OWASP Core Rule Set) provides a critical layer of defense against common attacks like SQL Injection, XSS, and remote code execution.
+- **Web Application Firewall (WAF):** Deploying Superset behind a WAF (e.g., Cloudflare, AWS WAF) is strongly recommended. A WAF with a standard ruleset (like the OWASP Core Rule Set) provides a critical layer of defense against common attacks like SQL Injection, XSS, and remote code execution.
 
 ### **Monitoring and Logging**
 
-  * **Configure Structured Logging:** Set up a robust logging configuration to capture important security events.
-  * **Centralize Logs:** Ship logs from all Superset components (frontend, worker, etc.) to a centralized SIEM (Security Information and Event Management) system for analysis and alerting.
-  * **Monitor Key Events:** Create alerts for suspicious activities, including:
-      * Multiple failed login attempts for a single user or from a single IP address.
-      * Changes to user roles or permissions.
-      * Creation or deletion of high-privilege users.
-      * Attempts to use disallowed SQL functions.
+- **Configure Structured Logging:** Set up a robust logging configuration to capture important security events.
+- **Centralize Logs:** Ship logs from all Superset components (frontend, worker, etc.) to a centralized SIEM (Security Information and Event Management) system for analysis and alerting.
+- **Monitor Key Events:** Create alerts for suspicious activities, including:
+  - Multiple failed login attempts for a single user or from a single IP address.
+  - Changes to user roles or permissions.
+  - Creation or deletion of high-privilege users.
+  - Attempts to use disallowed SQL functions.
 
------
+---
 
 ### **Appendix A: Production Deployment Checklist**
 
 #### **Initial Setup:**
 
-  - [ ] HTTPS/TLS is configured and enforced via a reverse proxy.
-  - [ ] A unique, strong `SUPERSET_SECRET_KEY` is generated and secured in an environment variable or secrets vault.
-  - [ ] Server-side session management is configured (e.g., Redis).
-  - [ ] `PERMANENT_SESSION_LIFETIME` is set to a short duration (e.g., 8 hours).
-  - [ ] All session cookie security flags (`Secure`, `HttpOnly`, `SameSite`) are enabled.
-  - [ ] `DEBUG` mode is set to `False`.
-  - [ ] Talisman is explicitly enabled and configured with a strict Content Security Policy.
-  - [ ] Database connections use dedicated, limited-privilege accounts.
-  - [ ] Authentication is integrated with an enterprise identity provider (OAuth/LDAP).
-  - [ ] A Web Application Firewall (WAF) is deployed in front of Superset.
-  - [ ] Logging is configured and logs are shipped to a central monitoring system.
+- [ ] HTTPS/TLS is configured and enforced via a reverse proxy.
+- [ ] A unique, strong `SUPERSET_SECRET_KEY` is generated and secured in an environment variable or secrets vault.
+- [ ] Server-side session management is configured (e.g., Redis).
+- [ ] `PERMANENT_SESSION_LIFETIME` is set to a short duration (e.g., 8 hours).
+- [ ] All session cookie security flags (`Secure`, `HttpOnly`, `SameSite`) are enabled.
+- [ ] `DEBUG` mode is set to `False`.
+- [ ] Talisman is explicitly enabled and configured with a strict Content Security Policy.
+- [ ] Database connections use dedicated, limited-privilege accounts.
+- [ ] Authentication is integrated with an enterprise identity provider (OAuth/LDAP).
+- [ ] A Web Application Firewall (WAF) is deployed in front of Superset.
+- [ ] Logging is configured and logs are shipped to a central monitoring system.
 
 #### **Ongoing Maintenance:**
 
-  - [ ] Regularly update to the latest major or minor versions of Superset. Those versions receive up-to-date security patches.
-  - [ ] Rotate the `SUPERSET_SECRET_KEY` periodically (e.g., quarterly) and after any potential security incident.
-  - [ ] Rotate the other security-critical secrets (guest-token and async-query JWT secrets, SMTP and database credentials) on the cadence in Appendix C, and after any potential security incident.
-  - [ ] Conduct quarterly access reviews for all users.
-  - [ ] Assuming logging and monitoring is in place, review security monitoring alerts weekly.
+- [ ] Regularly update to the latest major or minor versions of Superset. Those versions receive up-to-date security patches.
+- [ ] Rotate the `SUPERSET_SECRET_KEY` periodically (e.g., quarterly) and after any potential security incident.
+- [ ] Rotate the other security-critical secrets (guest-token and async-query JWT secrets, SMTP and database credentials) on the cadence in Appendix C, and after any potential security incident.
+- [ ] Conduct quarterly access reviews for all users.
+- [ ] Assuming logging and monitoring is in place, review security monitoring alerts weekly.
 
 ### **Appendix B: `SECRET_KEY` Rotation and Compromise Response**
 
@@ -178,13 +179,13 @@ https://superset.apache.org/admin-docs/configuration/configuring-superset/#rotat
 
 `SUPERSET_SECRET_KEY` is not the only security-critical secret in a Superset deployment. Maintain an inventory of all such secrets, store each in a secrets manager (not in `superset_config.py` or version control), assign a responsible maintainer, and rotate them on a defined cadence as well as after any suspected compromise.
 
-| Secret | Purpose | Risk if leaked | Suggested rotation |
-|---|---|---|---|
-| `SUPERSET_SECRET_KEY` | Signs session cookies; key material for encrypting stored DB credentials (Fernet/AES) | Forged sessions (auth bypass / privilege escalation); decryption of exfiltrated metadata-DB secrets | Quarterly + post-incident |
-| `GUEST_TOKEN_JWT_SECRET` | Signs embedded-dashboard guest tokens | Forged guest tokens → unauthorized dashboard/data access | Quarterly + post-incident |
-| `GLOBAL_ASYNC_QUERIES_JWT_SECRET` | Signs the async-query channel JWT | Forged async-query tokens | Quarterly + post-incident |
-| SMTP password | Outbound email for alerts & reports | Email relay abuse / spoofing | Per organizational policy + post-incident |
-| Database connection passwords | Access to analytical databases and the metadata DB | Direct database access | Per organizational policy + post-incident |
+| Secret                            | Purpose                                                                               | Risk if leaked                                                                                      | Suggested rotation                        |
+| --------------------------------- | ------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------- | ----------------------------------------- |
+| `SUPERSET_SECRET_KEY`             | Signs session cookies; key material for encrypting stored DB credentials (Fernet/AES) | Forged sessions (auth bypass / privilege escalation); decryption of exfiltrated metadata-DB secrets | Quarterly + post-incident                 |
+| `GUEST_TOKEN_JWT_SECRET`          | Signs embedded-dashboard guest tokens                                                 | Forged guest tokens → unauthorized dashboard/data access                                            | Quarterly + post-incident                 |
+| `GLOBAL_ASYNC_QUERIES_JWT_SECRET` | Signs the async-query channel JWT                                                     | Forged async-query tokens                                                                           | Quarterly + post-incident                 |
+| SMTP password                     | Outbound email for alerts & reports                                                   | Email relay abuse / spoofing                                                                        | Per organizational policy + post-incident |
+| Database connection passwords     | Access to analytical databases and the metadata DB                                    | Direct database access                                                                              | Per organizational policy + post-incident |
 
 Notes:
 
@@ -193,6 +194,7 @@ Notes:
 - Keep the register under change control so new secrets introduced by future features are added to the rotation schedule.
 
 :::resources
+
 - [Blog: Running Apache Superset on the Open Internet](https://preset.io/blog/running-apache-superset-on-the-open-internet-a-report-from-the-fireline/)
 - [Blog: How Security Vulnerabilities are Reported & Handled in Apache Superset](https://preset.io/blog/how-security-vulnerabilities-are-reported-and-handled-in-apache-superset/)
-:::
+  :::

docs/admin_docs/security/security.mdx

@@ -24,13 +24,13 @@ A table with the permissions for these roles can be found at [/RESOURCES/STANDAR
 Admins have all possible rights, including granting or revoking rights from other
 users and altering other people’s slices and dashboards.
 
->#### Threat Model and Privilege Boundaries: The Admin Role
+> #### Threat Model and Privilege Boundaries: The Admin Role
 >
->Apache Superset is built with a granular permission model where users assigned the Admin role are considered fully trusted. Admins possess complete control over the application's configuration, UI rendering, and access controls.
+> Apache Superset is built with a granular permission model where users assigned the Admin role are considered fully trusted. Admins possess complete control over the application's configuration, UI rendering, and access controls.
 >
->Consequently, actions performed by an Admin that alter the application's behavior or presentation—such as injecting custom CSS, modifying Jinja templates, or altering security flags—are intended administrative capabilities by design.
+> Consequently, actions performed by an Admin that alter the application's behavior or presentation—such as injecting custom CSS, modifying Jinja templates, or altering security flags—are intended administrative capabilities by design.
 >
->In accordance with MITRE CNA Rule 4.1, a vulnerability must represent a violation of an explicit security policy. Because the Admin role is defined as a trusted operational boundary, actions executed with Admin privileges do not cross a security perimeter. Therefore, exploit vectors that strictly require Admin access are not classified as security vulnerabilities and are ineligible for CVE assignment.
+> In accordance with MITRE CNA Rule 4.1, a vulnerability must represent a violation of an explicit security policy. Because the Admin role is defined as a trusted operational boundary, actions executed with Admin privileges do not cross a security perimeter. Therefore, exploit vectors that strictly require Admin access are not classified as security vulnerabilities and are ineligible for CVE assignment.
 
 ### Alpha
 
@@ -54,10 +54,10 @@ to all databases by default, both **Alpha** and **Gamma** users need to be given
 
 Beyond the base `sql_lab` role, two additional SQL Lab permissions must be explicitly granted for users who need these capabilities:
 
-| Permission | Feature |
-|------------|---------|
-| `can_estimate_query_cost` on `SQLLab` | Estimate query cost before running |
-| `can_format_sql` on `SQLLab` | Format SQL using the database's dialect |
+| Permission                            | Feature                                 |
+| ------------------------------------- | --------------------------------------- |
+| `can_estimate_query_cost` on `SQLLab` | Estimate query cost before running      |
+| `can_format_sql` on `SQLLab`          | Format SQL using the database's dialect |
 
 Grant these in **Security → List Roles** by adding the permissions to the relevant role.
 
@@ -73,6 +73,7 @@ users who need to view dashboards. It provides minimal read-only access for:
 - Viewing annotations on charts
 
 The Public role explicitly excludes:
+
 - Any write permissions on dashboards, charts, or datasets
 - SQL Lab access
 - Share functionality
@@ -236,6 +237,7 @@ viewers returns the resource to the dataset-based fallback. Explicit Viewers are
 going forward; the implicit fallback may be deprecated and removed in a later major version.
 
 **Important considerations:**
+
 - Viewer access uses normal dataset checks unless `VIEWER_PROMISCUOUS_MODE` is enabled
 - With `VIEWER_PROMISCUOUS_MODE`, dashboard viewer access can bypass dataset-level checks for
   charts and datasets in that dashboard
@@ -243,6 +245,7 @@ going forward; the implicit fallback may be deprecated and removed in a later ma
 - The dashboard must still be published to be visible
 
 This feature is particularly useful for:
+
 - Making specific dashboards public while keeping others private
 - Granting access to dashboards without exposing the underlying datasets for other uses
 - Creating dashboard-specific access patterns that don't align with dataset permissions
@@ -305,10 +308,11 @@ However, it is crucial to understand the following:
 **Database Security is Paramount**: The ultimate responsibility for securing database access, controlling permissions, and preventing unauthorized function execution lies with the database administrators (DBAs) and security teams managing the underlying database instance.
 
 **Recommended Database Practices**: We strongly recommend implementing security best practices at the database level, including:
-* **Least Privilege**: Connecting Superset using dedicated database user accounts with the minimum permissions required for Superset's operation (typically read-only access to necessary schemas/tables).
-* **Database Roles & Permissions**: Utilizing database-native roles and permissions to restrict access to sensitive functions, system variables (like `@@hostname`), schemas, or tables.
-* **Network Security**: Employing network-level controls like database firewalls or proxies to restrict connections.
-* **Auditing**: Enabling database-level auditing to monitor executed queries and access patterns.
+
+- **Least Privilege**: Connecting Superset using dedicated database user accounts with the minimum permissions required for Superset's operation (typically read-only access to necessary schemas/tables).
+- **Database Roles & Permissions**: Utilizing database-native roles and permissions to restrict access to sensitive functions, system variables (like `@@hostname`), schemas, or tables.
+- **Network Security**: Employing network-level controls like database firewalls or proxies to restrict connections.
+- **Auditing**: Enabling database-level auditing to monitor executed queries and access patterns.
 
 By combining Superset's configurable safeguards with strong database-level security practices, you can achieve a more robust and layered security posture.
 
@@ -464,11 +468,11 @@ rules are:
 
 For example, if a dataset has three filters:
 
-| Filter | Clause | Group Key |
-|--------|--------|-----------|
-| F1 | `department = 'Finance'` | `department` |
-| F2 | `department = 'Marketing'` | `department` |
-| F3 | `region = 'Europe'` | `region` |
+| Filter | Clause                     | Group Key    |
+| ------ | -------------------------- | ------------ |
+| F1     | `department = 'Finance'`   | `department` |
+| F2     | `department = 'Marketing'` | `department` |
+| F3     | `region = 'Europe'`        | `region`     |
 
 The resulting WHERE clause would be:
 
@@ -552,7 +556,7 @@ GET /api/v1/rowlevelsecurity/<id>
 ```
 
 The response includes the filter's `name`, `filter_type` (Regular or Base), `clause`,
-`group_key`, assigned `tables` (with id, schema, and table\_name), and assigned `subjects`.
+`group_key`, assigned `tables` (with id, schema, and table_name), and assigned `subjects`.
 
 :::tip Auditing RLS for virtual datasets
 To find all RLS rules that could affect a particular virtual dataset, query the list
@@ -598,13 +602,13 @@ This reduces the risk for replay attacks and session hijacking.
 Superset uses [Flask-Session](https://flask-session.readthedocs.io/en/latest/) to manage server side sessions.
 To enable this extension you have to set:
 
-``` python
+```python
 SESSION_SERVER_SIDE = True
 ```
 
 Flask-Session offers multiple backend session interfaces for Flask, here's an example for Redis:
 
-``` python
+```python
 from redis import Redis
 
 SESSION_TYPE = "redis"
@@ -633,8 +637,8 @@ It's extremely important to correctly configure a Content Security Policy when d
 prevent many types of attacks. Superset provides two variables in `config.py` for deploying a CSP:
 
 - `TALISMAN_ENABLED` defaults to `True`; set this to `False` in order to disable CSP
-- `TALISMAN_CONFIG` holds the actual the policy definition (*see example below*) as well as any
-other arguments to be passed to Talisman.
+- `TALISMAN_CONFIG` holds the actual the policy definition (_see example below_) as well as any
+  other arguments to be passed to Talisman.
 
 When running in production mode, Superset will check at startup for the presence
 of a CSP. If one is not found, it will issue a warning with the security risks. For environments
@@ -650,12 +654,12 @@ this warning using the `CONTENT_SECURITY_POLICY_WARNING` key in `config.py`.
   ```
 
 - Only scripts marked with a [nonce](https://content-security-policy.com/nonce/) can be loaded and executed.
-Nonce is a random string automatically generated by Talisman on each page load.
-You can get current nonce value by calling jinja macro `csp_nonce()`.
+  Nonce is a random string automatically generated by Talisman on each page load.
+  You can get current nonce value by calling jinja macro `csp_nonce()`.
 
   ```html
   <script nonce="{{ csp_nonce() }}">
-  /* my script */
+    /* my script */
   </script>
   ```
 
@@ -673,7 +677,7 @@ You can get current nonce value by calling jinja macro `csp_nonce()`.
   ```
 
 - Cartodiagram charts request map data (image and json) from external resources that can be edited by users,
-and therefore either require a list of allowed domains to request from or a wildcard (`'*'`) for `img-src` and `connect-src`.
+  and therefore either require a list of allowed domains to request from or a wildcard (`'*'`) for `img-src` and `connect-src`.
 
 - Other CSP directives default to `'self'` to limit content to the same origin as the Superset server.
 
@@ -684,12 +688,12 @@ In order to adjust provided CSP configuration to your needs, follow the instruct
 
 Setting `TALISMAN_ENABLED = True` will invoke Talisman's protection with its default arguments,
 of which `content_security_policy` is only one. Those can be found in the
-[Talisman documentation](https://pypi.org/project/flask-talisman/) under *Options*.
+[Talisman documentation](https://pypi.org/project/flask-talisman/) under _Options_.
 These generally improve security, but administrators should be aware of their existence.
 
 In particular, the option of `force_https = True` (`False` by default) may break Superset's Alerts & Reports
 if workers are configured to access charts via a `WEBDRIVER_BASEURL` beginning
-with `http://`.  As long as a Superset deployment enforces https upstream, e.g.,
+with `http://`. As long as a Superset deployment enforces https upstream, e.g.,
 through a load balancer or application gateway, it should be acceptable to keep this
 option disabled. Otherwise, you may want to enable `force_https` like this:
 

docs/admin_docs_versioned_docs/version-6.1.0/configuration/alerts-reports.mdx

@@ -9,8 +9,8 @@ version: 2
 
 Users can configure automated alerts and reports to send dashboards or charts to an email recipient or Slack channel.
 
-- *Alerts* are sent when a SQL condition is reached
-- *Reports* are sent on a schedule
+- _Alerts_ are sent when a SQL condition is reached
+- _Reports_ are sent on a schedule
 
 Alerts and reports are disabled by default. To turn them on, you'll need to change configuration settings and install a suitable headless browser in your environment.
 
@@ -26,16 +26,17 @@ Alerts and reports are disabled by default. To turn them on, you'll need to chan
   - emails: `SMTP_*` settings
   - Slack messages: `SLACK_API_TOKEN`
 - Users can customize the email subject by including date code placeholders, which will automatically be replaced with the corresponding UTC date when the email is sent. To enable this functionality, activate the `"DATE_FORMAT_IN_EMAIL_SUBJECT"` [feature flag](/admin-docs/configuration/configuring-superset#feature-flags). This enables date formatting in email subjects, preventing all reporting emails from being grouped into the same thread (optional for the reporting feature).
-    - Use date codes from [strftime.org](https://strftime.org/) to create the email subject.
-    - If no date code is provided, the original string will be used as the email subject.
+  - Use date codes from [strftime.org](https://strftime.org/) to create the email subject.
+  - If no date code is provided, the original string will be used as the email subject.
 
 ##### Disable dry-run mode
 
-Screenshots will be taken but no messages actually sent as long as `ALERT_REPORTS_NOTIFICATION_DRY_RUN = True`, its default value in `docker/pythonpath_dev/superset_config.py`.  To disable dry-run mode and start receiving email/Slack notifications, set `ALERT_REPORTS_NOTIFICATION_DRY_RUN` to `False` in [superset config](https://github.com/apache/superset/blob/master/docker/pythonpath_dev/superset_config.py).
+Screenshots will be taken but no messages actually sent as long as `ALERT_REPORTS_NOTIFICATION_DRY_RUN = True`, its default value in `docker/pythonpath_dev/superset_config.py`. To disable dry-run mode and start receiving email/Slack notifications, set `ALERT_REPORTS_NOTIFICATION_DRY_RUN` to `False` in [superset config](https://github.com/apache/superset/blob/master/docker/pythonpath_dev/superset_config.py).
 
 #### In your `Dockerfile`
 
 You'll need to extend the Superset image to include a headless browser. Your options include:
+
 - Use Playwright with Chrome: this is the recommended approach as of version 4.1.x or greater. A working example of a Dockerfile that installs these tools is provided under "Building your own production Docker image" on the [Docker Builds](/admin-docs/installation/docker-builds#building-your-own-production-docker-image) page. Read the code comments there as you'll also need to change a feature flag in your config.
 - Use Firefox: you'll need to install geckodriver and Firefox.
 - Use Chrome without Playwright: you'll need to install Chrome and set the value of `WEBDRIVER_TYPE` to `"chrome"` in your `superset_config.py`.
@@ -189,7 +190,7 @@ You need to replace default values with your custom Redis, Slack and/or SMTP con
 Superset uses Celery beat and Celery worker(s) to send alerts and reports.
 
 - The beat is the scheduler that tells the worker when to perform its tasks. This schedule is defined when you create the alert or report.
-- The worker will process the  tasks that need to be performed when an alert or report is fired.
+- The worker will process the tasks that need to be performed when an alert or report is fired.
 
 In the `CeleryConfig`, only the `beat_schedule` is relevant to this feature, the rest of the `CeleryConfig` can be changed for your needs.
 
@@ -296,7 +297,7 @@ Please refer to `ExecutorType` in the codebase for other executor types.
 
 It's also possible to specify a minimum interval between each report's execution through the config file:
 
-``` python
+```python
 # Set a minimum interval threshold between executions (for each Alert/Report)
 # Value should be an integer
 ALERT_MINIMUM_INTERVAL = int(timedelta(minutes=10).total_seconds())
@@ -305,7 +306,7 @@ REPORT_MINIMUM_INTERVAL = int(timedelta(minutes=5).total_seconds())
 
 Alternatively, you can assign a function to `ALERT_MINIMUM_INTERVAL` and/or `REPORT_MINIMUM_INTERVAL`. This is useful to dynamically retrieve a value as needed:
 
-``` python
+```python
 def alert_dynamic_minimal_interval(**kwargs) -> int:
     """
     Define logic here to retrieve the value dynamically
@@ -318,7 +319,7 @@ ALERT_MINIMUM_INTERVAL = alert_dynamic_minimal_interval
 
 For security, Superset rewrites external links in alert/report email HTML so
 they go through a warning page before the user is navigated to the external
-site.  Internal links (matching your configured base URL) are not affected.
+site. Internal links (matching your configured base URL) are not affected.
 
 ```python
 # Disable external link redirection entirely (default: True)
@@ -330,17 +331,17 @@ to determine which hosts are internal.
 
 ## Troubleshooting
 
-There are many reasons that reports might not be working.  Try these steps to check for specific issues.
+There are many reasons that reports might not be working. Try these steps to check for specific issues.
 
 ### Confirm feature flag is enabled and you have sufficient permissions
 
-If you don't see "Alerts & Reports" under the *Manage* section of the Settings dropdown in the Superset UI, you need to enable the `ALERT_REPORTS` feature flag (see above). Enable another feature flag and check to see that it took effect, to verify that your config file is getting loaded.
+If you don't see "Alerts & Reports" under the _Manage_ section of the Settings dropdown in the Superset UI, you need to enable the `ALERT_REPORTS` feature flag (see above). Enable another feature flag and check to see that it took effect, to verify that your config file is getting loaded.
 
 Log in as an admin user to ensure you have adequate permissions.
 
 ### Check the logs of your Celery worker
 
-This is the best source of information about the problem.  In a docker compose deployment, you can do this with a command like `docker logs superset_worker --since 1h`.
+This is the best source of information about the problem. In a docker compose deployment, you can do this with a command like `docker logs superset_worker --since 1h`.
 
 ### Check web browser and webdriver installation
 
@@ -352,7 +353,7 @@ If you are handling the installation of the headless browser on your own, do you
 
 One symptom of an invalid connection to an email server is receiving an error of `[Errno 110] Connection timed out` in your logs when the report tries to send.
 
-Confirm via testing that your outbound email configuration is correct.  Here is the simplest test, for an un-authenticated email SMTP email service running on port 25.  If you are sending over SSL, for instance, study how [Superset's codebase sends emails](https://github.com/apache/superset/blob/master/superset/utils/core.py#L818) and then test with those commands and arguments.
+Confirm via testing that your outbound email configuration is correct. Here is the simplest test, for an un-authenticated email SMTP email service running on port 25. If you are sending over SSL, for instance, study how [Superset's codebase sends emails](https://github.com/apache/superset/blob/master/superset/utils/core.py#L818) and then test with those commands and arguments.
 
 Start Python in your worker environment, replace all example values, and run:
 
@@ -378,16 +379,16 @@ This should send an email.
 
 Possible fixes:
 
-- Some cloud hosts disable outgoing unauthenticated SMTP email to prevent spam.  For instance, [Azure blocks port 25 by default on some machines](https://learn.microsoft.com/en-us/azure/virtual-network/troubleshoot-outbound-smtp-connectivity). Enable that port or use another sending method.
+- Some cloud hosts disable outgoing unauthenticated SMTP email to prevent spam. For instance, [Azure blocks port 25 by default on some machines](https://learn.microsoft.com/en-us/azure/virtual-network/troubleshoot-outbound-smtp-connectivity). Enable that port or use another sending method.
 - Use another set of SMTP credentials that you verify works in this setup.
 
 ### Browse to your report from the worker
 
-The worker may be unable to reach the report. It will use the value of `WEBDRIVER_BASEURL` to browse to the report.  If that route is invalid, or presents an authentication challenge that the worker can't pass, the report screenshot will fail.
+The worker may be unable to reach the report. It will use the value of `WEBDRIVER_BASEURL` to browse to the report. If that route is invalid, or presents an authentication challenge that the worker can't pass, the report screenshot will fail.
 
 Check this by attempting to `curl` the URL of a report that you see in the error logs of your worker. For instance, from the worker environment, run `curl http://superset_app:8088/superset/dashboard/1/`. You may get different responses depending on whether the dashboard exists - for example, you may need to change the `1` in that URL. If there's a URL in your logs from a failed report screenshot, that's a good place to start. The goal is to determine a valid value for `WEBDRIVER_BASEURL` and determine if an issue like HTTPS or authentication is redirecting your worker.
 
-In a deployment with authentication measures enabled like HTTPS and Single Sign-On, it may make sense to have the worker navigate directly to the Superset application running in the same location, avoiding the need to sign in.  For instance, you could use `WEBDRIVER_BASEURL="http://superset_app:8088"` for a docker compose deployment, and set `"force_https": False,` in your `TALISMAN_CONFIG`.
+In a deployment with authentication measures enabled like HTTPS and Single Sign-On, it may make sense to have the worker navigate directly to the Superset application running in the same location, avoiding the need to sign in. For instance, you could use `WEBDRIVER_BASEURL="http://superset_app:8088"` for a docker compose deployment, and set `"force_https": False,` in your `TALISMAN_CONFIG`.
 
 ### Duplicate report deliveries
 
@@ -495,6 +496,7 @@ schedule the queries that have `schedule_info` in their JSON metadata. For sched
 Airflow, additional fields can be easily added to the configuration file above.
 
 :::resources
+
 - [Tutorial: Automated Alerts and Reporting via Slack/Email in Superset](https://dev.to/ngtduc693/apache-superset-topic-5-automated-alerts-and-reporting-via-slackemail-in-superset-2gbe)
 - [Blog: Integrating Slack alerts and Apache Superset for better data observability](https://medium.com/affinityanswers-tech/integrating-slack-alerts-and-apache-superset-for-better-data-observability-fd2f9a12c350)
-:::
+  :::

docs/admin_docs_versioned_docs/version-6.1.0/configuration/async-queries-celery.mdx

@@ -104,5 +104,6 @@ celery --app=superset.tasks.celery_app:app flower
 ```
 
 :::resources
+
 - [Blog: How to Set Up Global Async Queries (GAQ) in Apache Superset](https://medium.com/@ngigilevis/how-to-set-up-global-async-queries-gaq-in-apache-superset-a-complete-guide-9d2f4a047559)
-:::
+  :::

docs/admin_docs_versioned_docs/version-6.1.0/configuration/aws-iam.mdx

@@ -1,26 +1,28 @@
 {/*
 Licensed to the Apache Software Foundation (ASF) under one
-or more contributor license agreements.  See the NOTICE file
+or more contributor license agreements. See the NOTICE file
 distributed with this work for additional information
-regarding copyright ownership.  The ASF licenses this file
+regarding copyright ownership. The ASF licenses this file
 to you under the Apache License, Version 2.0 (the
 "License"); you may not use this file except in compliance
-with the License.  You may obtain a copy of the License at
+with the License. You may obtain a copy of the License at
 
-  http://www.apache.org/licenses/LICENSE-2.0
+http://www.apache.org/licenses/LICENSE-2.0
 
 Unless required by applicable law or agreed to in writing,
 software distributed under the License is distributed on an
 "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-KIND, either express or implied.  See the License for the
+KIND, either express or implied. See the License for the
 specific language governing permissions and limitations
 under the License.
 */}
 
 ---
+
 title: AWS IAM Authentication
 sidebar_label: AWS IAM Authentication
 sidebar_position: 15
+
 ---
 
 # AWS IAM Authentication for AWS Databases
@@ -31,7 +33,7 @@ Cross-account IAM role assumption via STS `AssumeRole` is supported, allowing a
 
 ## Prerequisites
 
-- Enable the `AWS_DATABASE_IAM_AUTH` feature flag in `superset_config.py`. IAM authentication is gated behind this flag; if it is disabled, connections using `aws_iam` fail with *"AWS IAM database authentication is not enabled."*
+- Enable the `AWS_DATABASE_IAM_AUTH` feature flag in `superset_config.py`. IAM authentication is gated behind this flag; if it is disabled, connections using `aws_iam` fail with _"AWS IAM database authentication is not enabled."_
   ```python
   FEATURE_FLAGS = {
       "AWS_DATABASE_IAM_AUTH": True,
@@ -66,14 +68,14 @@ IAM authentication is configured via the **encrypted_extra** field of the databa
 }
 ```
 
-| Field | Required | Description |
-|-------|----------|-------------|
-| `enabled` | Yes | Set to `true` to activate IAM auth |
-| `role_arn` | No | ARN of the cross-account IAM role to assume via STS. Omit for same-account auth |
-| `external_id` | No | External ID for the STS `AssumeRole` call, if required by the target role's trust policy |
-| `region` | Yes | AWS region of the database cluster |
-| `db_username` | Yes | The database username associated with the IAM identity |
-| `session_duration` | No | STS session duration in seconds (default: `3600`) |
+| Field              | Required | Description                                                                              |
+| ------------------ | -------- | ---------------------------------------------------------------------------------------- |
+| `enabled`          | Yes      | Set to `true` to activate IAM auth                                                       |
+| `role_arn`         | No       | ARN of the cross-account IAM role to assume via STS. Omit for same-account auth          |
+| `external_id`      | No       | External ID for the STS `AssumeRole` call, if required by the target role's trust policy |
+| `region`           | Yes      | AWS region of the database cluster                                                       |
+| `db_username`      | Yes      | The database username associated with the IAM identity                                   |
+| `session_duration` | No       | STS session duration in seconds (default: `3600`)                                        |
 
 ### Redshift (Serverless)
 

docs/admin_docs_versioned_docs/version-6.1.0/configuration/cache.mdx

@@ -271,6 +271,7 @@ While database-backed operations work reliably, the Redis backend is recommended
 deployments where low latency and reduced database load are important.
 
 :::resources
+
 - [Blog: The Data Engineer's Guide to Lightning-Fast Superset Dashboards](https://preset.io/blog/the-data-engineers-guide-to-lightning-fast-apache-superset-dashboards/)
 - [Blog: Accelerating Dashboards with Materialized Views](https://preset.io/blog/accelerating-apache-superset-dashboards-with-materialized-views/)
-:::
+  :::

docs/admin_docs_versioned_docs/version-6.1.0/configuration/configuring-superset.mdx

@@ -225,7 +225,7 @@ RequestHeader set X-Forwarded-Proto "https"
 
 ## Configuring the application root
 
-*Please be advised that this feature is in BETA.*
+_Please be advised that this feature is in BETA._
 
 Superset supports running the application under a non-root path. The root path
 prefix can be specified in one of three ways:
@@ -312,10 +312,13 @@ AUTH_USER_REGISTRATION_ROLE = "Public"
 ```
 
 In case you want to assign the `Admin` role on new user registration, it can be assigned as follows:
+
 ```python
 AUTH_USER_REGISTRATION_ROLE = "Admin"
 ```
+
 If you encounter the [issue](https://github.com/apache/superset/issues/13243) of not being able to list users from the Superset main page settings, although a newly registered user has an `Admin` role, please re-run `superset init` to sync the required permissions. Below is the command to re-run `superset init` using docker compose.
+
 ```
 docker-compose exec superset superset init
 ```
@@ -505,5 +508,6 @@ CELERY_BEAT_SCHEDULE = {
 Adjust `retention_period_days` to control how long query rows are kept. Companion opt-in tasks (`prune_logs`, `prune_tasks`) exist for pruning the logs and tasks tables; see the commented-out examples in `superset/config.py`. Without enabling these tasks, the metadata database will grow unbounded over time.
 
 :::resources
+
 - [Blog: Feature Flags in Apache Superset](https://preset.io/blog/feature-flags-in-apache-superset-and-preset/)
-:::
+  :::

docs/admin_docs_versioned_docs/version-6.1.0/configuration/country-map-tools.mdx

@@ -22,10 +22,10 @@ The current list of countries can be found in the src
 
 The Country Maps visualization already ships with the maps for the following countries:
 
-<ul style={{columns: 3}}>
-{countriesData.countries.map((country, index) => (
-  <li key={index}>{country}</li>
-))}
+<ul style={{ columns: 3 }}>
+  {countriesData.countries.map((country, index) => (
+    <li key={index}>{country}</li>
+  ))}
 </ul>
 
 ## Adding a New Country

docs/admin_docs_versioned_docs/version-6.1.0/configuration/feature-flags.mdx

@@ -7,7 +7,7 @@ version: 1
 
 import featureFlags from '../_versioned_data/static/feature-flags.json';
 
-export const FlagTable = ({flags}) => (
+export const FlagTable = ({ flags }) => (
   <table>
     <thead>
       <tr>
@@ -17,14 +17,21 @@ export const FlagTable = ({flags}) => (
       </tr>
     </thead>
     <tbody>
-      {flags.map((flag) => (
+      {flags.map(flag => (
         <tr key={flag.name}>
-          <td><code>{flag.name}</code></td>
-          <td><code>{flag.default ? 'True' : 'False'}</code></td>
+          <td>
+            <code>{flag.name}</code>
+          </td>
+          <td>
+            <code>{flag.default ? 'True' : 'False'}</code>
+          </td>
           <td>
             {flag.description}
             {flag.docs && (
-              <> (<a href={flag.docs}>docs</a>)</>
+              <>
+                {' '}
+                (<a href={flag.docs}>docs</a>)
+              </>
             )}
           </td>
         </tr>
@@ -50,12 +57,12 @@ FEATURE_FLAGS = {
 
 Feature flags progress through lifecycle stages:
 
-| Stage | Description |
-|-------|-------------|
+| Stage           | Description                                                                    |
+| --------------- | ------------------------------------------------------------------------------ |
 | **Development** | Experimental features under active development. May be incomplete or unstable. |
-| **Testing** | Feature complete but undergoing testing. Usable but may contain bugs. |
-| **Stable** | Production-ready features. Safe for all deployments. |
-| **Deprecated** | Features scheduled for removal. Migrate away from these. |
+| **Testing**     | Feature complete but undergoing testing. Usable but may contain bugs.          |
+| **Stable**      | Production-ready features. Safe for all deployments.                           |
+| **Deprecated**  | Features scheduled for removal. Migrate away from these.                       |
 
 ---
 

docs/admin_docs_versioned_docs/version-6.1.0/configuration/importing-exporting-datasources.mdx

@@ -148,10 +148,10 @@ datasets by saving the following YAML to file and then running the **import_data
 
 ```yaml
 databases:
-- database_name: main
-  tables:
-  - table_name: random_time_series
-    columns:
-    - column_name: ds
-      verbose_name: datetime
+  - database_name: main
+    tables:
+      - table_name: random_time_series
+        columns:
+          - column_name: ds
+            verbose_name: datetime
 ```

docs/admin_docs_versioned_docs/version-6.1.0/configuration/map-tiles.mdx

@@ -18,7 +18,9 @@ DECKGL_BASE_MAP = [
     ['tile://https://your_personal_url/{z}/{x}/{y}.png', 'MyTile']
 ]
 ```
+
 Openstreetmap tiles url can be added without prefix.
+
 ```python
 DECKGL_BASE_MAP = [
     ['https://c.tile.openstreetmap.org/{z}/{x}/{y}.png', 'OpenStreetMap']
@@ -26,6 +28,7 @@ DECKGL_BASE_MAP = [
 ```
 
 Default values are:
+
 ```python
 DECKGL_BASE_MAP = [
     ['https://tile.openstreetmap.org/{z}/{x}/{y}.png', 'Streets (OSM)'],
@@ -46,6 +49,7 @@ Setting `DECKGL_BASE_MAP` overwrite default values
 :::
 
 After defining your map tiles, set them in these variables:
+
 - `CORS_OPTIONS`
 - `connect-src` of `TALISMAN_CONFIG` and `TALISMAN_CONFIG_DEV` variables.
 

docs/admin_docs_versioned_docs/version-6.1.0/configuration/mcp-server.mdx

@@ -55,11 +55,11 @@ The MCP server runs as a separate process alongside Superset:
 superset mcp run --host 127.0.0.1 --port 5008
 ```
 
-| Flag | Default | Description |
-|------|---------|-------------|
-| `--host` | `127.0.0.1` | Host to bind to |
-| `--port` | `5008` | Port to bind to |
-| `--debug` | off | Enable debug logging |
+| Flag      | Default     | Description          |
+| --------- | ----------- | -------------------- |
+| `--host`  | `127.0.0.1` | Host to bind to      |
+| `--port`  | `5008`      | Port to bind to      |
+| `--debug` | off         | Enable debug logging |
 
 The endpoint is available at `http://<host>:<port>/mcp`.
 
@@ -193,22 +193,24 @@ MCP_JWT_AUDIENCE = "your-audience"
 
 :::warning
 Store `MCP_JWT_SECRET` securely. Never commit it to version control. Use environment variables:
+
 ```python
 import os
 MCP_JWT_SECRET = os.environ.get("MCP_JWT_SECRET")
 ```
+
 :::
 
 #### JWT claims
 
 The MCP server validates these standard claims:
 
-| Claim | Config Key | Description |
-|-------|-----------|-------------|
-| `exp` | -- | Expiration time (always validated) |
-| `iss` | `MCP_JWT_ISSUER` | Token issuer (optional but recommended) |
-| `aud` | `MCP_JWT_AUDIENCE` | Token audience (optional but recommended) |
-| `sub` | -- | Subject -- primary claim used to resolve the Superset user |
+| Claim | Config Key         | Description                                                |
+| ----- | ------------------ | ---------------------------------------------------------- |
+| `exp` | --                 | Expiration time (always validated)                         |
+| `iss` | `MCP_JWT_ISSUER`   | Token issuer (optional but recommended)                    |
+| `aud` | `MCP_JWT_AUDIENCE` | Token audience (optional but recommended)                  |
+| `sub` | --                 | Subject -- primary claim used to resolve the Superset user |
 
 #### User resolution
 
@@ -435,7 +437,7 @@ services:
   superset:
     image: apache/superset:latest
     ports:
-      - "8088:8088"
+      - '8088:8088'
     volumes:
       - ./superset_config.py:/app/superset_config.py
     environment:
@@ -443,9 +445,9 @@ services:
 
   mcp:
     image: apache/superset:latest
-    command: ["superset", "mcp", "run", "--host", "0.0.0.0", "--port", "5008"]
+    command: ['superset', 'mcp', 'run', '--host', '0.0.0.0', '--port', '5008']
     ports:
-      - "5008:5008"
+      - '5008:5008'
     volumes:
       - ./superset_config.py:/app/superset_config.py
     environment:
@@ -494,30 +496,30 @@ All MCP settings go in `superset_config.py`. Defaults are defined in `superset/m
 
 ### Core
 
-| Setting | Default | Description |
-|---------|---------|-------------|
-| `MCP_SERVICE_HOST` | `"localhost"` | Host the MCP server binds to |
-| `MCP_SERVICE_PORT` | `5008` | Port the MCP server binds to |
-| `MCP_SERVICE_URL` | `None` | Public base URL for MCP-generated links (set this when behind a reverse proxy) |
-| `MCP_DEBUG` | `False` | Enable debug logging |
-| `MCP_DEV_USERNAME` | -- | Superset username for development mode (no auth) |
-| `MCP_RBAC_ENABLED` | `True` | Enforce Superset's role-based access control on MCP tool calls. When `True`, each tool checks that the authenticated user has the required FAB permission before executing. Disable only for testing or trusted-network deployments. |
+| Setting            | Default       | Description                                                                                                                                                                                                                          |
+| ------------------ | ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `MCP_SERVICE_HOST` | `"localhost"` | Host the MCP server binds to                                                                                                                                                                                                         |
+| `MCP_SERVICE_PORT` | `5008`        | Port the MCP server binds to                                                                                                                                                                                                         |
+| `MCP_SERVICE_URL`  | `None`        | Public base URL for MCP-generated links (set this when behind a reverse proxy)                                                                                                                                                       |
+| `MCP_DEBUG`        | `False`       | Enable debug logging                                                                                                                                                                                                                 |
+| `MCP_DEV_USERNAME` | --            | Superset username for development mode (no auth)                                                                                                                                                                                     |
+| `MCP_RBAC_ENABLED` | `True`        | Enforce Superset's role-based access control on MCP tool calls. When `True`, each tool checks that the authenticated user has the required FAB permission before executing. Disable only for testing or trusted-network deployments. |
 
 ### Authentication
 
-| Setting | Default | Description |
-|---------|---------|-------------|
-| `MCP_AUTH_ENABLED` | `False` | Enable JWT authentication |
-| `MCP_JWT_ALGORITHM` | `"RS256"` | JWT signing algorithm (`RS256` or `HS256`) |
-| `MCP_JWKS_URI` | `None` | JWKS endpoint URL (RS256) |
-| `MCP_JWT_PUBLIC_KEY` | `None` | Static RSA public key string (RS256) |
-| `MCP_JWT_SECRET` | `None` | Shared secret string (HS256) |
-| `MCP_JWT_ISSUER` | `None` | Expected `iss` claim |
-| `MCP_JWT_AUDIENCE` | `None` | Expected `aud` claim |
-| `MCP_REQUIRED_SCOPES` | `[]` | Required JWT scopes |
-| `MCP_JWT_DEBUG_ERRORS` | `False` | Log detailed JWT errors server-side (never exposed in HTTP responses per RFC 6750) |
-| `MCP_AUTH_FACTORY` | `None` | Custom auth provider factory `(flask_app) -> auth_provider`. Takes precedence over built-in JWT |
-| `MCP_USER_RESOLVER` | `None` | Custom function `(app, access_token) -> username` to extract a Superset username from a validated JWT token. When `None`, the default resolver checks `preferred_username`, `username`, `email`, and `sub` claims in that order. |
+| Setting                | Default   | Description                                                                                                                                                                                                                      |
+| ---------------------- | --------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `MCP_AUTH_ENABLED`     | `False`   | Enable JWT authentication                                                                                                                                                                                                        |
+| `MCP_JWT_ALGORITHM`    | `"RS256"` | JWT signing algorithm (`RS256` or `HS256`)                                                                                                                                                                                       |
+| `MCP_JWKS_URI`         | `None`    | JWKS endpoint URL (RS256)                                                                                                                                                                                                        |
+| `MCP_JWT_PUBLIC_KEY`   | `None`    | Static RSA public key string (RS256)                                                                                                                                                                                             |
+| `MCP_JWT_SECRET`       | `None`    | Shared secret string (HS256)                                                                                                                                                                                                     |
+| `MCP_JWT_ISSUER`       | `None`    | Expected `iss` claim                                                                                                                                                                                                             |
+| `MCP_JWT_AUDIENCE`     | `None`    | Expected `aud` claim                                                                                                                                                                                                             |
+| `MCP_REQUIRED_SCOPES`  | `[]`      | Required JWT scopes                                                                                                                                                                                                              |
+| `MCP_JWT_DEBUG_ERRORS` | `False`   | Log detailed JWT errors server-side (never exposed in HTTP responses per RFC 6750)                                                                                                                                               |
+| `MCP_AUTH_FACTORY`     | `None`    | Custom auth provider factory `(flask_app) -> auth_provider`. Takes precedence over built-in JWT                                                                                                                                  |
+| `MCP_USER_RESOLVER`    | `None`    | Custom function `(app, access_token) -> username` to extract a Superset username from a validated JWT token. When `None`, the default resolver checks `preferred_username`, `username`, `email`, and `sub` claims in that order. |
 
 ### Response Size Guard
 
@@ -537,12 +539,12 @@ MCP_RESPONSE_SIZE_CONFIG = {
 }
 ```
 
-| Key | Default | Description |
-|-----|---------|-------------|
-| `enabled` | `True` | Enable response size checking |
-| `token_limit` | `25000` | Maximum estimated token count per response |
-| `warn_threshold_pct` | `80` | Warn when response exceeds this percentage of the limit |
-| `excluded_tools` | See above | Tools exempt from size checking (e.g., tools that return URLs, not data) |
+| Key                  | Default   | Description                                                              |
+| -------------------- | --------- | ------------------------------------------------------------------------ |
+| `enabled`            | `True`    | Enable response size checking                                            |
+| `token_limit`        | `25000`   | Maximum estimated token count per response                               |
+| `warn_threshold_pct` | `80`      | Warn when response exceeds this percentage of the limit                  |
+| `excluded_tools`     | See above | Tools exempt from size checking (e.g., tools that return URLs, not data) |
 
 ### Caching
 
@@ -568,18 +570,18 @@ MCP_CACHE_CONFIG = {
 }
 ```
 
-| Key | Default | Description |
-|-----|---------|-------------|
-| `enabled` | `False` | Enable response caching |
-| `CACHE_KEY_PREFIX` | `None` | Optional prefix for cache keys (useful for shared Redis) |
-| `list_tools_ttl` | `300` | Cache TTL in seconds for `tools/list` |
-| `list_resources_ttl` | `300` | Cache TTL for `resources/list` |
-| `list_prompts_ttl` | `300` | Cache TTL for `prompts/list` |
-| `read_resource_ttl` | `3600` | Cache TTL for `resources/read` |
-| `get_prompt_ttl` | `3600` | Cache TTL for `prompts/get` |
-| `call_tool_ttl` | `3600` | Cache TTL for `tools/call` |
-| `max_item_size` | `1048576` | Maximum cached item size in bytes (1 MB) |
-| `excluded_tools` | See above | Tools that are never cached (mutating or non-deterministic) |
+| Key                  | Default   | Description                                                 |
+| -------------------- | --------- | ----------------------------------------------------------- |
+| `enabled`            | `False`   | Enable response caching                                     |
+| `CACHE_KEY_PREFIX`   | `None`    | Optional prefix for cache keys (useful for shared Redis)    |
+| `list_tools_ttl`     | `300`     | Cache TTL in seconds for `tools/list`                       |
+| `list_resources_ttl` | `300`     | Cache TTL for `resources/list`                              |
+| `list_prompts_ttl`   | `300`     | Cache TTL for `prompts/list`                                |
+| `read_resource_ttl`  | `3600`    | Cache TTL for `resources/read`                              |
+| `get_prompt_ttl`     | `3600`    | Cache TTL for `prompts/get`                                 |
+| `call_tool_ttl`      | `3600`    | Cache TTL for `tools/call`                                  |
+| `max_item_size`      | `1048576` | Maximum cached item size in bytes (1 MB)                    |
+| `excluded_tools`     | See above | Tools that are never cached (mutating or non-deterministic) |
 
 ### Redis Store (Multi-Pod)
 
@@ -594,12 +596,12 @@ MCP_STORE_CONFIG = {
 }
 ```
 
-| Key | Default | Description |
-|-----|---------|-------------|
-| `enabled` | `False` | Enable Redis-backed store |
-| `CACHE_REDIS_URL` | `None` | Redis connection URL (e.g., `redis://redis-host:6379/0`) |
-| `event_store_max_events` | `100` | Maximum events retained per session |
-| `event_store_ttl` | `3600` | Event TTL in seconds |
+| Key                      | Default | Description                                              |
+| ------------------------ | ------- | -------------------------------------------------------- |
+| `enabled`                | `False` | Enable Redis-backed store                                |
+| `CACHE_REDIS_URL`        | `None`  | Redis connection URL (e.g., `redis://redis-host:6379/0`) |
+| `event_store_max_events` | `100`   | Maximum events retained per session                      |
+| `event_store_ttl`        | `3600`  | Event TTL in seconds                                     |
 
 ### Tool Search
 
@@ -622,15 +624,15 @@ MCP_TOOL_SEARCH_CONFIG = {
 }
 ```
 
-| Key | Default | Description |
-|-----|---------|-------------|
-| `enabled` | `True` | Enable tool search. When `False`, all tools are listed upfront |
-| `strategy` | `"bm25"` | Search ranking algorithm. `"bm25"` supports natural language; `"regex"` supports pattern matching |
-| `max_results` | `5` | Maximum tools returned per search query |
-| `always_visible` | See above | Tools that always appear in `list_tools`, regardless of search |
-| `include_schemas` | `False` | When `False` (default, "summary mode"), search results omit `inputSchema` entirely and include a lightweight `parameters_hint` listing top-level parameter names. Set to `True` to include the full `inputSchema` in search results. Full schemas are always used when a tool is actually invoked via `call_tool`. |
-| `compact_schemas` | `True` | Strip `$defs` / `$ref` and replace with `{"type": "object"}` in search results to reduce token cost. Only takes effect when `include_schemas=True` — ignored in summary mode. |
-| `max_description_length` | `300` | Truncate tool descriptions in search results (0 = no truncation). Applies in both summary and full-schema modes. |
+| Key                      | Default   | Description                                                                                                                                                                                                                                                                                                        |
+| ------------------------ | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `enabled`                | `True`    | Enable tool search. When `False`, all tools are listed upfront                                                                                                                                                                                                                                                     |
+| `strategy`               | `"bm25"`  | Search ranking algorithm. `"bm25"` supports natural language; `"regex"` supports pattern matching                                                                                                                                                                                                                  |
+| `max_results`            | `5`       | Maximum tools returned per search query                                                                                                                                                                                                                                                                            |
+| `always_visible`         | See above | Tools that always appear in `list_tools`, regardless of search                                                                                                                                                                                                                                                     |
+| `include_schemas`        | `False`   | When `False` (default, "summary mode"), search results omit `inputSchema` entirely and include a lightweight `parameters_hint` listing top-level parameter names. Set to `True` to include the full `inputSchema` in search results. Full schemas are always used when a tool is actually invoked via `call_tool`. |
+| `compact_schemas`        | `True`    | Strip `$defs` / `$ref` and replace with `{"type": "object"}` in search results to reduce token cost. Only takes effect when `include_schemas=True` — ignored in summary mode.                                                                                                                                      |
+| `max_description_length` | `300`     | Truncate tool descriptions in search results (0 = no truncation). Applies in both summary and full-schema modes.                                                                                                                                                                                                   |
 
 :::tip
 Set `enabled: False` to revert to the traditional "show all tools at once" behavior, which some clients or workflows may prefer.
@@ -667,16 +669,16 @@ The MCP server respects Superset's full role-based access control (RBAC). Every
 
 Each tool declares one or more required FAB permissions. The table below maps tool groups to their permission requirements:
 
-| Tool group | Required FAB permission |
-|------------|------------------------|
-| `list_charts`, `get_chart_info`, `get_chart_data`, `get_chart_preview`, `generate_chart`, `update_chart` | `can_read` on `Chart` (read), `can_write` on `Chart` (mutate) |
-| `list_dashboards`, `get_dashboard_info`, `generate_dashboard`, `add_chart_to_existing_dashboard` | `can_read` on `Dashboard` (read), `can_write` on `Dashboard` (mutate) |
-| `list_datasets`, `get_dataset_info`, `create_virtual_dataset` | `can_read` on `Dataset` (read), `can_write` on `Dataset` (mutate) |
-| `list_databases`, `get_database_info` | `can_read` on `Database` |
-| `execute_sql` | `can_execute_sql_query` on `SQLLab` |
-| `open_sql_lab_with_context` | `can_read` on `SQLLab` |
-| `save_sql_query` | `can_write` on `SavedQuery` |
-| `health_check` | None (public) |
+| Tool group                                                                                               | Required FAB permission                                               |
+| -------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------- |
+| `list_charts`, `get_chart_info`, `get_chart_data`, `get_chart_preview`, `generate_chart`, `update_chart` | `can_read` on `Chart` (read), `can_write` on `Chart` (mutate)         |
+| `list_dashboards`, `get_dashboard_info`, `generate_dashboard`, `add_chart_to_existing_dashboard`         | `can_read` on `Dashboard` (read), `can_write` on `Dashboard` (mutate) |
+| `list_datasets`, `get_dataset_info`, `create_virtual_dataset`                                            | `can_read` on `Dataset` (read), `can_write` on `Dataset` (mutate)     |
+| `list_databases`, `get_database_info`                                                                    | `can_read` on `Database`                                              |
+| `execute_sql`                                                                                            | `can_execute_sql_query` on `SQLLab`                                   |
+| `open_sql_lab_with_context`                                                                              | `can_read` on `SQLLab`                                                |
+| `save_sql_query`                                                                                         | `can_write` on `SavedQuery`                                           |
+| `health_check`                                                                                           | None (public)                                                         |
 
 To disable RBAC checking globally (for trusted-network deployments or testing), set:
 
@@ -703,13 +705,13 @@ This makes MCP activity fully auditable alongside regular Superset activity. The
 
 Every MCP request passes through a middleware stack before reaching the tool function. The default stack (assembled in `build_middleware_list()` in `server.py`) is:
 
-| Middleware | Purpose | Default |
-|------------|---------|---------|
-| `StructuredContentStripperMiddleware` | Strips `structuredContent` from responses for Claude.ai bridge compatibility | Enabled |
-| `LoggingMiddleware` | Logs each tool call with user, parameters, and duration | Enabled |
-| `GlobalErrorHandlerMiddleware` | Catches unhandled exceptions and sanitizes sensitive data before it reaches the client | Enabled |
-| `ResponseSizeGuardMiddleware` | Estimates token count, warns at 80% of limit, blocks at limit | Enabled (configurable via `MCP_RESPONSE_SIZE_CONFIG`) |
-| `ResponseCachingMiddleware` | Caches read-heavy tool responses (in-memory or Redis) | Disabled (enable via `MCP_CACHE_CONFIG`) |
+| Middleware                            | Purpose                                                                                | Default                                               |
+| ------------------------------------- | -------------------------------------------------------------------------------------- | ----------------------------------------------------- |
+| `StructuredContentStripperMiddleware` | Strips `structuredContent` from responses for Claude.ai bridge compatibility           | Enabled                                               |
+| `LoggingMiddleware`                   | Logs each tool call with user, parameters, and duration                                | Enabled                                               |
+| `GlobalErrorHandlerMiddleware`        | Catches unhandled exceptions and sanitizes sensitive data before it reaches the client | Enabled                                               |
+| `ResponseSizeGuardMiddleware`         | Estimates token count, warns at 80% of limit, blocks at limit                          | Enabled (configurable via `MCP_RESPONSE_SIZE_CONFIG`) |
+| `ResponseCachingMiddleware`           | Caches read-heavy tool responses (in-memory or Redis)                                  | Disabled (enable via `MCP_CACHE_CONFIG`)              |
 
 Additional middleware classes (`RateLimitMiddleware`, `FieldPermissionsMiddleware`, `PrivateToolMiddleware`) are implemented in `superset/mcp_service/middleware.py` but are not added to the default pipeline. They are available for operators who want to layer them in via a custom startup path.
 

docs/admin_docs_versioned_docs/version-6.1.0/configuration/networking-settings.mdx

@@ -8,12 +8,10 @@ version: 1
 
 ## CORS
 
-
 :::note
 In Superset versions prior to `5.x` you have to install to install `flask-cors` with `pip install flask-cors` to enable CORS support.
 :::
 
-
 The following keys in `superset_config.py` can be specified to configure CORS:
 
 - `ENABLE_CORS`: Must be set to `True` in order to enable CORS
@@ -54,11 +52,13 @@ Restart Superset for this configuration change to take effect.
 There are two approaches to making dashboards publicly accessible:
 
 **Option 1: Dataset-based access (simpler)**
+
 1. Set `PUBLIC_ROLE_LIKE = "Public"` in `superset_config.py`
 2. Grant the Public role access to the relevant datasets (Menu → Security → List Roles → Public)
 3. All published dashboards using those datasets become visible to anonymous users
 
 **Option 2: Dashboard-level access (selective control)**
+
 1. Set `PUBLIC_ROLE_LIKE = "Public"` in `superset_config.py`
 2. Add the `'DASHBOARD_RBAC': True` [Feature Flag](/admin-docs/configuration/feature-flags)
 3. Edit each dashboard's properties and add the "Public" role
@@ -75,7 +75,7 @@ Now anybody can directly access the dashboard's URL. You can embed it in an ifra
   width="600"
   height="400"
   seamless
-  frameBorder="0"
+  frameborder="0"
   scrolling="no"
   src="https://superset.my-domain.com/superset/dashboard/10/?standalone=1&height=400"
 >
@@ -123,17 +123,17 @@ running a custom auth postback endpoint), you can add the endpoints to `WTF_CSRF
 ## SSH Tunneling
 
 1. Turn on feature flag
-    - Change [`SSH_TUNNELING`](https://github.com/apache/superset/blob/eb8386e3f0647df6d1bbde8b42073850796cc16f/superset/config.py#L489) to `True`
-    - If you want to add more security when establishing the tunnel we allow users to overwrite the `SSHTunnelManager` class [here](https://github.com/apache/superset/blob/eb8386e3f0647df6d1bbde8b42073850796cc16f/superset/config.py#L507)
-    - You can also set the [`SSH_TUNNEL_LOCAL_BIND_ADDRESS`](https://github.com/apache/superset/blob/eb8386e3f0647df6d1bbde8b42073850796cc16f/superset/config.py#L508) this the host address where the tunnel will be accessible on your VPC
+   - Change [`SSH_TUNNELING`](https://github.com/apache/superset/blob/eb8386e3f0647df6d1bbde8b42073850796cc16f/superset/config.py#L489) to `True`
+   - If you want to add more security when establishing the tunnel we allow users to overwrite the `SSHTunnelManager` class [here](https://github.com/apache/superset/blob/eb8386e3f0647df6d1bbde8b42073850796cc16f/superset/config.py#L507)
+   - You can also set the [`SSH_TUNNEL_LOCAL_BIND_ADDRESS`](https://github.com/apache/superset/blob/eb8386e3f0647df6d1bbde8b42073850796cc16f/superset/config.py#L508) this the host address where the tunnel will be accessible on your VPC
 
 2. Create database w/ ssh tunnel enabled
-    - With the feature flag enabled you should now see ssh tunnel toggle.
-    - Click the toggle to enable SSH tunneling and add your credentials accordingly.
-        - Superset allows for two different types of authentication (Basic + Private Key). These credentials should come from your service provider.
+   - With the feature flag enabled you should now see ssh tunnel toggle.
+   - Click the toggle to enable SSH tunneling and add your credentials accordingly.
+     - Superset allows for two different types of authentication (Basic + Private Key). These credentials should come from your service provider.
 
 3. Verify data is flowing
-    - Once SSH tunneling has been enabled, go to SQL Lab and write a query to verify data is properly flowing.
+   - Once SSH tunneling has been enabled, go to SQL Lab and write a query to verify data is properly flowing.
 
 ## Domain Sharding
 

docs/admin_docs_versioned_docs/version-6.1.0/configuration/sql-templating.mdx

@@ -106,6 +106,7 @@ WHERE dttm_col > '{{ from_dttm | default("2024-01-01", true) }}'
 **Option 2: Use SQL Lab Parameters**
 
 Set parameters in the SQL Lab UI (Parameters menu):
+
 ```json
 {
   "from_dttm": "2024-01-01",
@@ -151,7 +152,7 @@ In the UI you can assign a set of parameters as JSON
 The parameters become available in your SQL (example: `SELECT * FROM {{ my_table }}` ) by using Jinja templating syntax.
 SQL Lab template parameters are stored with the dataset as `TEMPLATE PARAMETERS`.
 
-There is a special ``_filters`` parameter which can be used to test filters used in the jinja template.
+There is a special `_filters` parameter which can be used to test filters used in the jinja template.
 
 ```json
 {
@@ -172,7 +173,7 @@ WHERE action in {{ filter_values('action_type')|where_in }}
 GROUP BY action
 ```
 
-Note ``_filters`` is not stored with the dataset. It's only used within the SQL Lab UI.
+Note `_filters` is not stored with the dataset. It's only used within the SQL Lab UI.
 
 Besides default Jinja templating, SQL lab also supports self-defined template processor by setting
 the `CUSTOM_TEMPLATE_PROCESSORS` in your superset configuration. The values in this dictionary
@@ -306,16 +307,19 @@ cache key by adding the following parameter to your Jinja code:
 ```
 
 You can json-stringify the array by adding `|tojson` to your Jinja code:
+
 ```python
 {{ current_user_roles()|tojson }}
 ```
 
 You can use the `|where_in` filter to use your roles in a SQL statement. For example, if `current_user_roles()` returns `['admin', 'viewer']`, the following template:
+
 ```python
 SELECT * FROM users WHERE role IN {{ current_user_roles()|where_in }}
 ```
 
 Will be rendered as:
+
 ```sql
 SELECT * FROM users WHERE role IN ('admin', 'viewer')
 ```
@@ -341,6 +345,7 @@ Always treat `url_param()` values as untrusted input. Escaping behaviour varies
 {% if cc not in ('US', 'ES', 'FR') %}{% set cc = 'US' %}{% endif %}
 WHERE country_code = '{{ cc }}'
 ```
+
 :::
 
 Here's a concrete example:
@@ -425,6 +430,7 @@ This is useful if:
     AND full_name LIKE '{{ filter.get('val') | replace("'", "''") }}'
 {%- endif -%}
 ```
+
 :::
 
 Here's a concrete example:
@@ -489,7 +495,7 @@ The macro takes the following parameters:
 - `column`: Name of the temporal column. Leave undefined to reference the time range from a Dashboard Native Time Range
   filter (when present).
 - `default`: The default value to fall back to if the time filter is not present, or has the value `No filter`
-- `target_type`: The target temporal type as recognized by the target  database (e.g. `TIMESTAMP`, `DATE` or
+- `target_type`: The target temporal type as recognized by the target database (e.g. `TIMESTAMP`, `DATE` or
   `DATETIME`). If `column` is defined, the format will default to the type of the column. This is used to produce
   the format of the `from_expr` and `to_expr` properties of the returned `TimeFilter` object.
 - `strftime`: format using the `strftime` method of `datetime` for custom time formatting.
@@ -595,6 +601,7 @@ The parameter can be used in SQL Lab, or when fetching a metric from another dat
 Superset supports [builtin filters from the Jinja2 templating package](https://jinja.palletsprojects.com/en/stable/templates/#builtin-filters). Custom filters have also been implemented:
 
 ### Where In
+
 Parses a list into a SQL-compatible statement. This is useful with macros that return an array (for example the `filter_values` macro):
 
 ```
@@ -614,6 +621,7 @@ Dashboard filter without any value applied
 ### To Datetime
 
 Loads a string as a `datetime` object. This is useful when performing date operations. For example:
+
 ```
 {% set from_expr = get_time_filter("dttm", strftime="%Y-%m-%d").from_expr %}
 {% set to_expr = get_time_filter("dttm", strftime="%Y-%m-%d").to_expr %}
@@ -625,5 +633,6 @@ Loads a string as a `datetime` object. This is useful when performing date opera
 ```
 
 :::resources
+
 - [Blog: Intro to Jinja Templating in Apache Superset](https://preset.io/blog/intro-jinja-templating-apache-superset/)
-:::
+  :::

docs/admin_docs_versioned_docs/version-6.1.0/configuration/theming.mdx

@@ -4,6 +4,7 @@ hide_title: true
 sidebar_position: 12
 version: 1
 ---
+
 # Theming Superset
 
 :::note
@@ -34,11 +35,13 @@ You can also extend with Superset-specific tokens (documented in the default the
 When `ENABLE_UI_THEME_ADMINISTRATION = True` is configured, administrators can manage system-wide themes directly from the UI:
 
 #### Setting System Themes
+
 - **System Default Theme**: Click the sun icon on any theme to set it as the system-wide default
 - **System Dark Theme**: Click the moon icon on any theme to set it as the system dark mode theme
 - **Automatic OS Detection**: When both default and dark themes are set, Superset automatically detects and applies the appropriate theme based on OS preferences
 
 #### Managing System Themes
+
 - System themes are indicated with special badges in the theme list
 - Only administrators with write permissions can modify system theme settings
 - Removing a system theme designation reverts to configuration file defaults
@@ -46,6 +49,7 @@ When `ENABLE_UI_THEME_ADMINISTRATION = True` is configured, administrators can m
 ### Applying Themes to Dashboards
 
 Once created, themes can be applied to individual dashboards:
+
 - Edit any dashboard and select your custom theme from the theme dropdown
 - Each dashboard can have its own theme, allowing for branded or context-specific styling
 
@@ -127,6 +131,7 @@ When `ENABLE_UI_THEME_ADMINISTRATION = True`:
 Superset validates theme JSON when it is saved, either through the UI or via configuration. If a theme contains invalid tokens or an unrecognized structure, Superset logs a warning and falls back to the built-in default theme rather than applying a broken configuration. This prevents a bad theme from rendering the application unusable.
 
 The fallback order is:
+
 1. **UI-configured system theme** (highest priority, if `ENABLE_UI_THEME_ADMINISTRATION = True`)
 2. **`THEME_DEFAULT` / `THEME_DARK`** from `superset_config.py`
 3. **Built-in Superset default theme** (always present as a safety net)
@@ -455,9 +460,10 @@ For programmatic theme management, Superset provides REST endpoints:
 These endpoints require appropriate permissions and are subject to RBAC controls.
 
 :::resources
+
 - [Video: Live Demo — Theming Apache Superset](https://www.youtube.com/watch?v=XsZAsO9tC3o)
 - [CSS and Theming](https://docs.preset.io/docs/css-and-theming) - Additional theming techniques and CSS customization
 - [Blog: Customizing Apache Superset Dashboards with CSS](https://preset.io/blog/customizing-superset-dashboards-with-css/)
 - [Blog: Customizing Dashboards with CSS — Tips and Tricks](https://preset.io/blog/customizing-apache-superset-dashboards-with-css-additional-tips-and-tricks/)
 - [Blog: Customizing Chart Colors](https://preset.io/blog/customizing-chart-colors-with-superset-and-preset/)
-:::
+  :::

docs/admin_docs_versioned_docs/version-6.1.0/installation/architecture.mdx

@@ -5,7 +5,7 @@ sidebar_position: 1
 version: 1
 ---
 
-import useBaseUrl from "@docusaurus/useBaseUrl";
+import useBaseUrl from '@docusaurus/useBaseUrl';
 
 # Architecture
 

docs/admin_docs_versioned_docs/version-6.1.0/installation/docker-builds.mdx

@@ -11,8 +11,7 @@ The Apache Superset community extensively uses Docker for development, release,
 and productionizing Superset. This page details our Docker builds and tag naming
 schemes to help users navigate our offerings.
 
-Images are built and pushed to the [Superset Docker Hub repository](
-https://hub.docker.com/r/apache/superset) using GitHub Actions.
+Images are built and pushed to the [Superset Docker Hub repository](https://hub.docker.com/r/apache/superset) using GitHub Actions.
 Different sets of images are built and/or published at different times:
 
 - **Published releases** (`release`): published using

docs/admin_docs_versioned_docs/version-6.1.0/installation/docker-compose.mdx

@@ -5,12 +5,13 @@ sidebar_position: 5
 version: 1
 ---
 
-import useBaseUrl from "@docusaurus/useBaseUrl";
+import useBaseUrl from '@docusaurus/useBaseUrl';
 
 # Using Docker Compose
 
-<img src={useBaseUrl("/img/docker-compose.webp" )} width="150" />
-<br /><br />
+<img src={useBaseUrl('/img/docker-compose.webp')} width="150" />
+<br />
+<br />
 
 :::caution
 Since `docker compose` is primarily designed to run a set of containers on **a single host**
@@ -29,23 +30,23 @@ way to launch a fully functioning **development environment** quickly.
 Note that there are 4 major ways we support to run `docker compose`:
 
 1. **docker-compose.yml:** for interactive development, where we mount your local folder with the
-  frontend/backend files that you can edit and experience the changes you
-  make in the app in real time
+   frontend/backend files that you can edit and experience the changes you
+   make in the app in real time
 1. **docker-compose-light.yml:** a lightweight configuration with minimal services (database,
-  Superset app, and frontend dev server) for development. Uses in-memory caching instead of Redis
-  and is designed for running multiple instances simultaneously
+   Superset app, and frontend dev server) for development. Uses in-memory caching instead of Redis
+   and is designed for running multiple instances simultaneously
 1. **docker-compose-non-dev.yml** where we just build a more immutable image based on the
-  local branch and get all the required images running. Changes in the local branch
-  at the time you fire this up will be reflected, but changes to the code
-  while `up` won't be reflected in the app
+   local branch and get all the required images running. Changes in the local branch
+   at the time you fire this up will be reflected, but changes to the code
+   while `up` won't be reflected in the app
 1. **docker-compose-image-tag.yml** where we fetch an image from docker-hub say for the
-  `5.0.0` release for instance, and fire it up so you can try it. Here what's in
-  the local branch has no effects on what's running, we just fetch and run
-  pre-built images from docker-hub. For `docker compose` to work along with the
-  Postgres image it boots up, you'll want to point to a `-dev`-suffixed TAG, as in
-  `export TAG=5.0.0-dev` or `export TAG=4.1.2-dev`, with `latest-dev` being the default.
-  The `dev` builds include the `psycopg2-binary` required to connect
-  to the Postgres database launched as part of the `docker compose` builds.
+   `5.0.0` release for instance, and fire it up so you can try it. Here what's in
+   the local branch has no effects on what's running, we just fetch and run
+   pre-built images from docker-hub. For `docker compose` to work along with the
+   Postgres image it boots up, you'll want to point to a `-dev`-suffixed TAG, as in
+   `export TAG=5.0.0-dev` or `export TAG=4.1.2-dev`, with `latest-dev` being the default.
+   The `dev` builds include the `psycopg2-binary` required to connect
+   to the Postgres database launched as part of the `docker compose` builds.
 
 More on these approaches after setting up the requirements for either.
 
@@ -92,7 +93,7 @@ like to try out Superset without making any code changes follow the steps docume
 :::tip
 By default, we mount the local superset-frontend folder here and run `npm install` as well
 as `npm run dev` which triggers webpack to compile/bundle the frontend code. Depending
-on your local setup, especially if you have less than 16GB of memory,  it may be very slow to
+on your local setup, especially if you have less than 16GB of memory, it may be very slow to
 perform those operations. In this case, we recommend you set the env var
 `BUILD_SUPERSET_FRONTEND_IN_DOCKER` to `false`, and to run this locally instead in a terminal.
 Simply trigger `npm i && npm run dev`, this should be MUCH faster.
@@ -121,6 +122,7 @@ NODE_PORT=9003 docker compose -p superset-3 -f docker-compose-light.yml up
 ```
 
 This configuration includes:
+
 - PostgreSQL database (internal network only)
 - Superset application server
 - Frontend development server with webpack hot reloading
@@ -165,7 +167,7 @@ looking to fire up.
 
 :::caution
 All of the content belonging to a Superset instance - charts, dashboards, users, etc. - is stored in
-its metadata database. In production, this database should be backed up.  The default installation
+its metadata database. In production, this database should be backed up. The default installation
 with docker compose will store that data in a PostgreSQL database contained in a Docker
 [volume](https://docs.docker.com/storage/volumes/), which is not backed up.
 
@@ -174,7 +176,7 @@ Again, **THE DOCKER-COMPOSE INSTALLATION IS NOT PRODUCTION-READY OUT OF THE BOX.
 :::
 
 You should see a stream of logging output from the containers being launched on your machine. Once
-this output slows, you should have a running instance of Superset on your local machine!  To avoid
+this output slows, you should have a running instance of Superset on your local machine! To avoid
 the wall of text on future runs, add the `-d` option to the end of the `docker compose up` command.
 
 ### Configuring Further
@@ -258,24 +260,24 @@ Superset (which is running in its docker container). Other databases may have sl
 configurations but gist would be same and boils down to 2 steps -
 
 1. **(Mac users may skip this step)** Configuring the local postgresql/database instance to accept
-public incoming connections. By default, postgresql only allows incoming connections from
-`localhost` and under Docker, unless you use `--network=host`, `localhost` will refer to different
-endpoints on the host machine and in a docker container respectively. Allowing postgresql to accept
-connections from the Docker involves making one-line changes to the files `postgresql.conf` and
-`pg_hba.conf`; you can find helpful links tailored to your OS / PG version on the web easily for
-this task. For Docker it suffices to only whitelist IPs `172.0.0.0/8` instead of `*`, but in any
-case you are _warned_ that doing this in a production database _may_ have disastrous consequences as
-you are opening your database to the public internet.
+   public incoming connections. By default, postgresql only allows incoming connections from
+   `localhost` and under Docker, unless you use `--network=host`, `localhost` will refer to different
+   endpoints on the host machine and in a docker container respectively. Allowing postgresql to accept
+   connections from the Docker involves making one-line changes to the files `postgresql.conf` and
+   `pg_hba.conf`; you can find helpful links tailored to your OS / PG version on the web easily for
+   this task. For Docker it suffices to only whitelist IPs `172.0.0.0/8` instead of `*`, but in any
+   case you are _warned_ that doing this in a production database _may_ have disastrous consequences as
+   you are opening your database to the public internet.
 1. Instead of `localhost`, try using `host.docker.internal` (Mac users, Ubuntu) or `172.18.0.1`
-(Linux users) as the hostname when attempting to connect to the database. This is a Docker internal
-detail -- what is happening is that, in Mac systems, Docker Desktop creates a dns entry for the
-hostname `host.docker.internal` which resolves to the correct address for the host machine, whereas
-in Linux this is not the case (at least by default). If neither of these 2 hostnames work then you
-may want to find the exact hostname you want to use, for that you can do `ifconfig` or
-`ip addr show` and look at the IP address of `docker0` interface that must have been created by
-Docker for you. Alternately if you don't even see the `docker0` interface try (if needed with sudo)
-`docker network inspect bridge` and see if there is an entry for `"Gateway"` and note the IP
-address.
+   (Linux users) as the hostname when attempting to connect to the database. This is a Docker internal
+   detail -- what is happening is that, in Mac systems, Docker Desktop creates a dns entry for the
+   hostname `host.docker.internal` which resolves to the correct address for the host machine, whereas
+   in Linux this is not the case (at least by default). If neither of these 2 hostnames work then you
+   may want to find the exact hostname you want to use, for that you can do `ifconfig` or
+   `ip addr show` and look at the IP address of `docker0` interface that must have been created by
+   Docker for you. Alternately if you don't even see the `docker0` interface try (if needed with sudo)
+   `docker network inspect bridge` and see if there is an entry for `"Gateway"` and note the IP
+   address.
 
 ## 4. To build or not to build
 

docs/admin_docs_versioned_docs/version-6.1.0/installation/installation-methods.mdx

@@ -5,7 +5,7 @@ sidebar_position: 2
 version: 1
 ---
 
-import useBaseUrl from "@docusaurus/useBaseUrl";
+import useBaseUrl from '@docusaurus/useBaseUrl';
 
 # Installation Methods
 

docs/admin_docs_versioned_docs/version-6.1.0/installation/kubernetes.mdx

@@ -1,16 +1,17 @@
 ---
-title:  Kubernetes
+title: Kubernetes
 hide_title: true
 sidebar_position: 3
 version: 1
 ---
 
-import useBaseUrl from "@docusaurus/useBaseUrl";
+import useBaseUrl from '@docusaurus/useBaseUrl';
 
 # Installing on Kubernetes
 
-<img src={useBaseUrl("/img/k8s.png" )} width="150" />
-<br /><br />
+<img src={useBaseUrl('/img/k8s.png')} width="150" />
+<br />
+<br />
 
 Running Superset on Kubernetes is supported with the provided [Helm](https://helm.sh/) chart
 found in the official [Superset helm repository](https://apache.github.io/superset/index.yaml).
@@ -134,7 +135,7 @@ init:
 ```
 
 :::note
-Superset uses [Scarf Gateway](https://about.scarf.sh/scarf-gateway) to collect telemetry data.  Knowing the installation counts for different Superset versions informs the  project's decisions about patching and long-term support. Scarf purges personally identifiable information (PII) and provides only aggregated statistics.
+Superset uses [Scarf Gateway](https://about.scarf.sh/scarf-gateway) to collect telemetry data. Knowing the installation counts for different Superset versions informs the project's decisions about patching and long-term support. Scarf purges personally identifiable information (PII) and provides only aggregated statistics.
 
 To opt-out of this data collection in your Helm-based installation, edit the `repository:` line in your `helm/superset/values.yaml` file, replacing `apachesuperset.docker.scarf.sh/apache/superset` with `apache/superset` to pull the image directly from Docker Hub.
 :::
@@ -195,7 +196,7 @@ Those can be passed as key/values either with `extraEnv` or `extraSecretEnv` if
 extraEnv:
   SMTP_HOST: smtp.gmail.com
   SMTP_USER: user@gmail.com
-  SMTP_PORT: "587"
+  SMTP_PORT: '587'
   SMTP_MAIL_FROM: user@gmail.com
 
 extraSecretEnv:
@@ -356,7 +357,7 @@ supersetCeleryBeat:
 extraEnv:
   SMTP_HOST: smtp.gmail.com
   SMTP_USER: user@gmail.com
-  SMTP_PORT: "587"
+  SMTP_PORT: '587'
   SMTP_MAIL_FROM: user@gmail.com
 
 extraSecretEnv:
@@ -446,6 +447,7 @@ init:
 ```
 
 :::resources
+
 - [Tutorial: Mastering Data Visualization — Installing Superset on Kubernetes with Helm Chart](https://mahira-technology.medium.com/mastering-data-visualization-installing-superset-on-kubernetes-cluster-using-helm-chart-e4ec99199e1e)
 - [Tutorial: Installing Apache Superset in Kubernetes](https://aws.plainenglish.io/installing-apache-superset-in-kubernetes-1aec192ac495)
-:::
+  :::

docs/admin_docs_versioned_docs/version-6.1.0/installation/pypi.mdx

@@ -5,12 +5,13 @@ sidebar_position: 4
 version: 1
 ---
 
-import useBaseUrl from "@docusaurus/useBaseUrl";
+import useBaseUrl from '@docusaurus/useBaseUrl';
 
 # Installing Superset from PyPI
 
-<img src={useBaseUrl("/img/pypi.png" )} width="150" />
-<br /><br />
+<img src={useBaseUrl('/img/pypi.png')} width="150" />
+<br />
+<br />
 
 This page describes how to install Superset using the `apache_superset` package [published on PyPI](https://pypi.org/project/apache_superset/).
 
@@ -23,6 +24,7 @@ level dependencies.
 **Debian and Ubuntu**
 
 Ubuntu **24.04** uses python 3.12 per default, which currently is not supported by Superset. You need to add a second python installation of 3.11 and install the required additional dependencies.
+
 ```bash
 sudo add-apt-repository ppa:deadsnakes/ppa
 sudo apt update
@@ -133,6 +135,7 @@ pip install apache_superset
 ```
 
 Then, define mandatory configurations, SECRET_KEY and FLASK_APP:
+
 ```bash
 export SUPERSET_SECRET_KEY=YOUR-SECRET-KEY # For production use, make sure this is a strong key, for example generated using `openssl rand -base64 42`. See https://superset.apache.org/admin-docs/configuration/configuring-superset#specifying-a-secret_key
 export FLASK_APP=superset

docs/admin_docs_versioned_docs/version-6.1.0/installation/upgrading-superset.mdx

@@ -55,6 +55,7 @@ For a detailed list of breaking changes and migration notes for each version, se
 
 This file documents backwards-incompatible changes and provides guidance for migrating between
 major versions, including:
+
 - Configuration changes
 - API changes
 - Database migrations

docs/admin_docs_versioned_docs/version-6.1.0/security/cves.mdx

@@ -2,41 +2,42 @@
 title: CVEs fixed by release
 sidebar_position: 2
 ---
+
 #### Version 6.0.0
 
-| CVE            | Title                                                                              | Affected |
-|:---------------|:-----------------------------------------------------------------------------------|---------:|
-| CVE-2026-23980 | Improper Neutralization of Special Elements used in a SQL Command                  |  < 6.0.0 |
-| CVE-2026-23982 | Improper Authorization in Dataset Creation Allows Access Control Bypass            |  < 6.0.0 |
-| CVE-2026-23983 | Information Disclosure of sensitive user info via Tags                             |  < 6.0.0 |
-| CVE-2026-23984 | SQLLab Read-Only Bypass on PostgreSQL (DML execution)                              |  < 6.0.0 |
+| CVE            | Title                                                                   | Affected |
+| :------------- | :---------------------------------------------------------------------- | -------: |
+| CVE-2026-23980 | Improper Neutralization of Special Elements used in a SQL Command       |  < 6.0.0 |
+| CVE-2026-23982 | Improper Authorization in Dataset Creation Allows Access Control Bypass |  < 6.0.0 |
+| CVE-2026-23983 | Information Disclosure of sensitive user info via Tags                  |  < 6.0.0 |
+| CVE-2026-23984 | SQLLab Read-Only Bypass on PostgreSQL (DML execution)                   |  < 6.0.0 |
 
 #### Version 5.0.0
 
-| CVE            | Title                                                                              | Affected |
-|:---------------|:-----------------------------------------------------------------------------------|---------:|
-| CVE-2025-55673 | Exposure of Sensitive Information to an Unauthorized Actor                         |  < 5.0.0 |
-| CVE-2025-55674 | Improper Neutralization of Special Elements used in an SQL Command                 |  < 5.0.0 |
-| CVE-2025-55675 | Improper Access Control leading to Information Disclosure                          |  < 5.0.0 |
+| CVE            | Title                                                              | Affected |
+| :------------- | :----------------------------------------------------------------- | -------: |
+| CVE-2025-55673 | Exposure of Sensitive Information to an Unauthorized Actor         |  < 5.0.0 |
+| CVE-2025-55674 | Improper Neutralization of Special Elements used in an SQL Command |  < 5.0.0 |
+| CVE-2025-55675 | Improper Access Control leading to Information Disclosure          |  < 5.0.0 |
 
 #### Version 4.1.3
 
-| CVE            | Title                                                                              | Affected |
-|:---------------|:-----------------------------------------------------------------------------------|---------:|
-| CVE-2025-55672 | Improper Neutralization of Input During Web Page Generation                        |  < 4.1.3 |
+| CVE            | Title                                                       | Affected |
+| :------------- | :---------------------------------------------------------- | -------: |
+| CVE-2025-55672 | Improper Neutralization of Input During Web Page Generation |  < 4.1.3 |
 
 #### Version 4.1.2
 
-| CVE            | Title                                                                              | Affected |
-|:---------------|:-----------------------------------------------------------------------------------|---------:|
-| CVE-2025-27696 | Improper authorization leading to resource ownership takeover                      |  < 4.1.2 |
-| CVE-2025-48912 | Improper authorization bypass on row level security via SQL Injection              |  < 4.1.2 |
-| CVE-2026-23969 | Exposure of Sensitive Information via Incomplete ClickHouse Function Filtering     |  < 4.1.2 |
+| CVE            | Title                                                                          | Affected |
+| :------------- | :----------------------------------------------------------------------------- | -------: |
+| CVE-2025-27696 | Improper authorization leading to resource ownership takeover                  |  < 4.1.2 |
+| CVE-2025-48912 | Improper authorization bypass on row level security via SQL Injection          |  < 4.1.2 |
+| CVE-2026-23969 | Exposure of Sensitive Information via Incomplete ClickHouse Function Filtering |  < 4.1.2 |
 
 #### Version 4.1.0
 
 | CVE            | Title                                                                              | Affected |
-|:---------------|:-----------------------------------------------------------------------------------|---------:|
+| :------------- | :--------------------------------------------------------------------------------- | -------: |
 | CVE-2024-53947 | Improper SQL authorisation, parse for specific postgres functions                  |  < 4.1.0 |
 | CVE-2024-53948 | Error verbosity exposes metadata in analytics databases                            |  < 4.1.0 |
 | CVE-2024-53949 | Lower privilege users are able to create Role when FAB_ADD_SECURITY_API is enabled |  < 4.1.0 |
@@ -44,84 +45,84 @@ sidebar_position: 2
 
 #### Version 4.0.2
 
-| CVE            | Title                       | Affected |
-|:---------------|:----------------------------|---------:|
-| CVE-2024-39887 | Improper SQL authorization  |  < 4.0.1 |
+| CVE            | Title                      | Affected |
+| :------------- | :------------------------- | -------: |
+| CVE-2024-39887 | Improper SQL authorization |  < 4.0.1 |
 
 #### Version 3.1.3, 4.0.1
 
-| CVE            | Title                       |                    Affected |
-|:---------------|:----------------------------|----------------------------:|
-| CVE-2024-34693 | Server arbitrary file read  |  < 3.1.3, >= 4.0.0, < 4.0.1 |
+| CVE            | Title                      |                   Affected |
+| :------------- | :------------------------- | -------------------------: |
+| CVE-2024-34693 | Server arbitrary file read | < 3.1.3, >= 4.0.0, < 4.0.1 |
 
 #### Version 3.1.2
 
-| CVE            | Title                                                   | Affected |
-|:---------------|:--------------------------------------------------------|---------:|
-| CVE-2024-28148 | Incorrect datasource authorization on explore REST API  |  < 3.1.2 |
+| CVE            | Title                                                  | Affected |
+| :------------- | :----------------------------------------------------- | -------: |
+| CVE-2024-28148 | Incorrect datasource authorization on explore REST API |  < 3.1.2 |
 
 #### Version 3.0.4, 3.1.1
 
-| CVE            | Title                                                                        |                    Affected |
-|:---------------|:-----------------------------------------------------------------------------|----------------------------:|
-| CVE-2024-27315 | Improper error handling on alerts                                            |  < 3.0.4, >= 3.1.0, < 3.1.1 |
-| CVE-2024-24773 | Improper validation of SQL statements allows for unauthorized access to data |  < 3.0.4, >= 3.1.0, < 3.1.1 |
-| CVE-2024-24772 | Improper Neutralisation of custom SQL on embedded context                    |  < 3.0.4, >= 3.1.0, < 3.1.1 |
-| CVE-2024-24779 | Improper data authorization when creating a new dataset                      |  < 3.0.4, >= 3.1.0, < 3.1.1 |
-| CVE-2024-26016 | Improper authorization validation on dashboards and charts import            |  < 3.0.4, >= 3.1.0, < 3.1.1 |
+| CVE            | Title                                                                        |                   Affected |
+| :------------- | :--------------------------------------------------------------------------- | -------------------------: |
+| CVE-2024-27315 | Improper error handling on alerts                                            | < 3.0.4, >= 3.1.0, < 3.1.1 |
+| CVE-2024-24773 | Improper validation of SQL statements allows for unauthorized access to data | < 3.0.4, >= 3.1.0, < 3.1.1 |
+| CVE-2024-24772 | Improper Neutralisation of custom SQL on embedded context                    | < 3.0.4, >= 3.1.0, < 3.1.1 |
+| CVE-2024-24779 | Improper data authorization when creating a new dataset                      | < 3.0.4, >= 3.1.0, < 3.1.1 |
+| CVE-2024-26016 | Improper authorization validation on dashboards and charts import            | < 3.0.4, >= 3.1.0, < 3.1.1 |
 
 #### Version 3.0.3
 
 | CVE            | Title                                         | Affected |
-|:---------------|:----------------------------------------------|---------:|
+| :------------- | :-------------------------------------------- | -------: |
 | CVE-2023-49657 | Stored XSS in Dashboard Title and Chart Title |  < 3.0.3 |
 
 #### Version 3.0.2, 2.1.3
 
 | CVE            | Title                                                       |                   Affected |
-|:---------------|:------------------------------------------------------------|---------------------------:|
+| :------------- | :---------------------------------------------------------- | -------------------------: |
 | CVE-2023-46104 | Allows for uncontrolled resource consumption via a ZIP bomb | < 2.1.3, >= 3.0.0, < 3.0.2 |
 | CVE-2023-49736 | SQL Injection on where_in JINJA macro                       | < 2.1.3, >= 3.0.0, < 3.0.2 |
 | CVE-2023-49734 | Privilege Escalation Vulnerability                          | < 2.1.3, >= 3.0.0, < 3.0.2 |
 
 #### Version 3.0.0
 
-| CVE            | Title                                                                   | Affected |
-|:---------------|:------------------------------------------------------------------------|---------:|
-| CVE-2023-42502 | Open Redirect Vulnerability                                             |  < 3.0.0 |
-| CVE-2023-42505 | Sensitive information disclosure on db connection details               |  < 3.0.0 |
+| CVE            | Title                                                     | Affected |
+| :------------- | :-------------------------------------------------------- | -------: |
+| CVE-2023-42502 | Open Redirect Vulnerability                               |  < 3.0.0 |
+| CVE-2023-42505 | Sensitive information disclosure on db connection details |  < 3.0.0 |
 
 #### Version 2.1.3
 
-| CVE            | Title                                                                   | Affected |
-|:---------------|:------------------------------------------------------------------------|---------:|
-| CVE-2023-42504 | Lack of rate limiting allows for possible denial of service             |  < 2.1.3 |
+| CVE            | Title                                                       | Affected |
+| :------------- | :---------------------------------------------------------- | -------: |
+| CVE-2023-42504 | Lack of rate limiting allows for possible denial of service |  < 2.1.3 |
 
 #### Version 2.1.2
 
-| CVE            | Title                                                                   | Affected |
-|:---------------|:------------------------------------------------------------------------|---------:|
-| CVE-2023-40610 | Privilege escalation with default examples database                     |  < 2.1.2 |
-| CVE-2023-42501 | Unnecessary read permissions within the Gamma role                      |  < 2.1.2 |
-| CVE-2023-43701 | Stored XSS on API endpoint                                              |  < 2.1.2 |
+| CVE            | Title                                               | Affected |
+| :------------- | :-------------------------------------------------- | -------: |
+| CVE-2023-40610 | Privilege escalation with default examples database |  < 2.1.2 |
+| CVE-2023-42501 | Unnecessary read permissions within the Gamma role  |  < 2.1.2 |
+| CVE-2023-43701 | Stored XSS on API endpoint                          |  < 2.1.2 |
 
 #### Version 2.1.1
 
-| CVE            | Title                                                                   | Affected |
-|:---------------|:------------------------------------------------------------------------|---------:|
-| CVE-2023-36387 | Improper API permission for low privilege users                         |  < 2.1.1 |
-| CVE-2023-36388 | Improper API permission for low privilege users allows for SSRF         |  < 2.1.1 |
-| CVE-2023-27523 | Improper data permission validation on Jinja templated queries          |  < 2.1.1 |
-| CVE-2023-27526 | Improper Authorization check on import charts                           |  < 2.1.1 |
-| CVE-2023-39264 | Stack traces enabled by default                                         |  < 2.1.1 |
-| CVE-2023-39265 | Possible Unauthorized Registration of SQLite Database Connections       |  < 2.1.1 |
-| CVE-2023-37941 | Metadata db write access can lead to remote code execution              |  < 2.1.1 |
-| CVE-2023-32672 | SQL parser edge case bypasses data access authorization                 |  < 2.1.1 |
+| CVE            | Title                                                             | Affected |
+| :------------- | :---------------------------------------------------------------- | -------: |
+| CVE-2023-36387 | Improper API permission for low privilege users                   |  < 2.1.1 |
+| CVE-2023-36388 | Improper API permission for low privilege users allows for SSRF   |  < 2.1.1 |
+| CVE-2023-27523 | Improper data permission validation on Jinja templated queries    |  < 2.1.1 |
+| CVE-2023-27526 | Improper Authorization check on import charts                     |  < 2.1.1 |
+| CVE-2023-39264 | Stack traces enabled by default                                   |  < 2.1.1 |
+| CVE-2023-39265 | Possible Unauthorized Registration of SQLite Database Connections |  < 2.1.1 |
+| CVE-2023-37941 | Metadata db write access can lead to remote code execution        |  < 2.1.1 |
+| CVE-2023-32672 | SQL parser edge case bypasses data access authorization           |  < 2.1.1 |
 
 #### Version 2.1.0
 
 | CVE            | Title                                                                   | Affected |
-|:---------------|:------------------------------------------------------------------------|---------:|
+| :------------- | :---------------------------------------------------------------------- | -------: |
 | CVE-2023-25504 | Possible SSRF on import datasets                                        |  < 2.1.0 |
 | CVE-2023-27524 | Session validation vulnerability when using provided default SECRET_KEY |  < 2.1.0 |
 | CVE-2023-27525 | Incorrect default permissions for Gamma role                            |  < 2.1.0 |
@@ -129,8 +130,8 @@ sidebar_position: 2
 
 #### Version 2.0.1
 
-| CVE            | Title                                                       |          Affected  |
-|:---------------|:------------------------------------------------------------|------------------: |
+| CVE            | Title                                                       |           Affected |
+| :------------- | :---------------------------------------------------------- | -----------------: |
 | CVE-2022-41703 | SQL injection vulnerability in adhoc clauses                | < 2.0.1 or < 1.5.2 |
 | CVE-2022-43717 | Cross-Site Scripting on dashboards                          | < 2.0.1 or < 1.5.2 |
 | CVE-2022-43718 | Cross-Site Scripting vulnerability on upload forms          | < 2.0.1 or < 1.5.2 |

docs/admin_docs_versioned_docs/version-6.1.0/security/securing_superset.mdx

@@ -3,7 +3,7 @@ title: Securing Your Superset Installation for Production
 sidebar_position: 3
 ---
 
-> *This guide applies to Apache Superset version 4.0 and later and is an evolving set of best practices that administrators should adapt to their specific deployment architecture.*
+> _This guide applies to Apache Superset version 4.0 and later and is an evolving set of best practices that administrators should adapt to their specific deployment architecture._
 
 The default Apache Superset configuration is optimized for ease of use and development, not for security. For any production deployment, it is **critical** that you review and apply the following security configurations to harden your instance, protect user data, and prevent unauthorized access.
 
@@ -13,25 +13,25 @@ This guide provides a comprehensive checklist of essential security configuratio
 
 Running Superset without HTTPS (TLS) is not secure. Without it, all network traffic—including user credentials, session tokens, and sensitive data—is sent in cleartext and can be easily intercepted.
 
-* **Use a Reverse Proxy:** Your Superset instance should always be deployed behind a reverse proxy (e.g., Nginx, Traefik) or a load balancer (e.g., AWS ALB, Google Cloud Load Balancer) that is configured to handle HTTPS termination.
-* **Enforce Modern TLS:** Configure your proxy to enforce TLS 1.2 or higher with strong, industry-standard cipher suites.
-* **Implement HSTS:** Use the HTTP Strict Transport Security (HSTS) header to ensure browsers only connect to your Superset instance over HTTPS. This can be configured in your reverse proxy or within Superset's Talisman settings.
+- **Use a Reverse Proxy:** Your Superset instance should always be deployed behind a reverse proxy (e.g., Nginx, Traefik) or a load balancer (e.g., AWS ALB, Google Cloud Load Balancer) that is configured to handle HTTPS termination.
+- **Enforce Modern TLS:** Configure your proxy to enforce TLS 1.2 or higher with strong, industry-standard cipher suites.
+- **Implement HSTS:** Use the HTTP Strict Transport Security (HSTS) header to ensure browsers only connect to your Superset instance over HTTPS. This can be configured in your reverse proxy or within Superset's Talisman settings.
 
 ### **`SUPERSET_SECRET_KEY` Management (CRITICAL)**
 
 This is the most critical security setting for your Superset instance. It is used to sign all session cookies and encrypt sensitive information in the metadata database, such as database connection credentials.
 
-* **Generate a Unique, Strong Key:** A unique key must be generated for every Superset instance. Use a cryptographically secure method to create it.
-    ```bash
-    # Example using openssl to generate a strong key
-    openssl rand -base64 42
-    ```
-* **Store the Key Securely:** The key must be kept confidential. The recommended approach is to store it as an environment variable or in a secrets management system (e.g., AWS Secrets Manager, HashiCorp Vault). **Do not hardcode the key in `superset_config.py` or commit it to version control.**
-    ```python
-    # In superset_config.py
-    import os
-    SECRET_KEY = os.environ.get('SUPERSET_SECRET_KEY')
-    ```
+- **Generate a Unique, Strong Key:** A unique key must be generated for every Superset instance. Use a cryptographically secure method to create it.
+  ```bash
+  # Example using openssl to generate a strong key
+  openssl rand -base64 42
+  ```
+- **Store the Key Securely:** The key must be kept confidential. The recommended approach is to store it as an environment variable or in a secrets management system (e.g., AWS Secrets Manager, HashiCorp Vault). **Do not hardcode the key in `superset_config.py` or commit it to version control.**
+  ```python
+  # In superset_config.py
+  import os
+  SECRET_KEY = os.environ.get('SUPERSET_SECRET_KEY')
+  ```
 
 > #### ⚠️ Warning: Your `SUPERSET_SECRET_KEY` Must Be Unique
 >
@@ -75,7 +75,7 @@ SESSION_USE_SIGNER = True
 
 #### **Configure Session Lifetime and Cookie Security Flags**
 
-This is mandatory for *all* deployments, whether stateless or server-side.
+This is mandatory for _all_ deployments, whether stateless or server-side.
 
 ```python
 # superset_config.py
@@ -92,7 +92,8 @@ SESSION_COOKIE_SAMESITE = 'Lax'   # Provide protection against CSRF attacks
 ```
 
 > ##### Note on iFrame Embedding and `SESSION_COOKIE_SAMESITE`
->The recommended default setting `'Lax'` provides good CSRF protection for most use cases. However, if you need to embed Superset dashboards into other applications using an iFrame, you will need to change this setting to `'None'`.
+>
+> The recommended default setting `'Lax'` provides good CSRF protection for most use cases. However, if you need to embed Superset dashboards into other applications using an iFrame, you will need to change this setting to `'None'`.
 
 SESSION_COOKIE_SAMESITE = 'None'
 
@@ -102,9 +103,9 @@ Setting SameSite to 'None' requires that SESSION_COOKIE_SECURE is also set to Tr
 
 While Superset's built-in database authentication is convenient, for production it's highly recommended to integrate with an enterprise-grade identity provider (IdP).
 
-  * **Use an Enterprise IdP:** Configure authentication via OAuth or LDAP to leverage your organization's existing identity management system. This provides benefits like Single Sign-On (SSO), Multi-Factor Authentication (MFA), and centralized user provisioning/deprovisioning.
-  * **Principle of Least Privilege:** Assign users to the most restrictive roles necessary for their jobs. Avoid over-provisioning users with Admin or Alpha roles, and ensure row-level security is applied where appropriate.
-  * **Admin Accounts:** Delete or disable the default admin user after a new administrative account has been configured.
+- **Use an Enterprise IdP:** Configure authentication via OAuth or LDAP to leverage your organization's existing identity management system. This provides benefits like Single Sign-On (SSO), Multi-Factor Authentication (MFA), and centralized user provisioning/deprovisioning.
+- **Principle of Least Privilege:** Assign users to the most restrictive roles necessary for their jobs. Avoid over-provisioning users with Admin or Alpha roles, and ensure row-level security is applied where appropriate.
+- **Admin Accounts:** Delete or disable the default admin user after a new administrative account has been configured.
 
 ### **Content Security Policy (CSP) and Other Headers**
 
@@ -122,47 +123,47 @@ Here's the documentation section how how to set up Talisman: https://superset.ap
 >
 > It is essential to understand that **Apache Superset is a data visualization and exploration platform, not a database firewall or a comprehensive security solution for your data warehouse.** While Superset provides features to help manage data access, the ultimate responsibility for securing your underlying databases lies with your database administrators (DBAs) and security teams. This includes managing network access, user privileges, and fine-grained permissions directly within the database. The configurations below are an important secondary layer of security but should not be your only line of defense.
 
-  * **Use a Dedicated Database User:** The database connection configured in Superset should use a dedicated, limited-privilege database user. This user should only have the minimum required permissions (e.g., `SELECT` on specific schemas) for the data sources it needs to query. It should **not** have `INSERT`, `UPDATE`, `DELETE`, or administrative privileges.
-  * **Restrict Dangerous SQL Functions:** To mitigate potential SQL injection risks, configure the `DISALLOWED_SQL_FUNCTIONS` list in your `superset_config.py`. Be aware that this is a defense-in-depth measure, not a substitute for proper database permissions.
+- **Use a Dedicated Database User:** The database connection configured in Superset should use a dedicated, limited-privilege database user. This user should only have the minimum required permissions (e.g., `SELECT` on specific schemas) for the data sources it needs to query. It should **not** have `INSERT`, `UPDATE`, `DELETE`, or administrative privileges.
+- **Restrict Dangerous SQL Functions:** To mitigate potential SQL injection risks, configure the `DISALLOWED_SQL_FUNCTIONS` list in your `superset_config.py`. Be aware that this is a defense-in-depth measure, not a substitute for proper database permissions.
 
 ### **Additional Security Layers**
 
-  * **Web Application Firewall (WAF):** Deploying Superset behind a WAF (e.g., Cloudflare, AWS WAF) is strongly recommended. A WAF with a standard ruleset (like the OWASP Core Rule Set) provides a critical layer of defense against common attacks like SQL Injection, XSS, and remote code execution.
+- **Web Application Firewall (WAF):** Deploying Superset behind a WAF (e.g., Cloudflare, AWS WAF) is strongly recommended. A WAF with a standard ruleset (like the OWASP Core Rule Set) provides a critical layer of defense against common attacks like SQL Injection, XSS, and remote code execution.
 
 ### **Monitoring and Logging**
 
-  * **Configure Structured Logging:** Set up a robust logging configuration to capture important security events.
-  * **Centralize Logs:** Ship logs from all Superset components (frontend, worker, etc.) to a centralized SIEM (Security Information and Event Management) system for analysis and alerting.
-  * **Monitor Key Events:** Create alerts for suspicious activities, including:
-      * Multiple failed login attempts for a single user or from a single IP address.
-      * Changes to user roles or permissions.
-      * Creation or deletion of high-privilege users.
-      * Attempts to use disallowed SQL functions.
+- **Configure Structured Logging:** Set up a robust logging configuration to capture important security events.
+- **Centralize Logs:** Ship logs from all Superset components (frontend, worker, etc.) to a centralized SIEM (Security Information and Event Management) system for analysis and alerting.
+- **Monitor Key Events:** Create alerts for suspicious activities, including:
+  - Multiple failed login attempts for a single user or from a single IP address.
+  - Changes to user roles or permissions.
+  - Creation or deletion of high-privilege users.
+  - Attempts to use disallowed SQL functions.
 
------
+---
 
 ### **Appendix A: Production Deployment Checklist**
 
 #### **Initial Setup:**
 
-  - [ ] HTTPS/TLS is configured and enforced via a reverse proxy.
-  - [ ] A unique, strong `SUPERSET_SECRET_KEY` is generated and secured in an environment variable or secrets vault.
-  - [ ] Server-side session management is configured (e.g., Redis).
-  - [ ] `PERMANENT_SESSION_LIFETIME` is set to a short duration (e.g., 8 hours).
-  - [ ] All session cookie security flags (`Secure`, `HttpOnly`, `SameSite`) are enabled.
-  - [ ] `DEBUG` mode is set to `False`.
-  - [ ] Talisman is explicitly enabled and configured with a strict Content Security Policy.
-  - [ ] Database connections use dedicated, limited-privilege accounts.
-  - [ ] Authentication is integrated with an enterprise identity provider (OAuth/LDAP).
-  - [ ] A Web Application Firewall (WAF) is deployed in front of Superset.
-  - [ ] Logging is configured and logs are shipped to a central monitoring system.
+- [ ] HTTPS/TLS is configured and enforced via a reverse proxy.
+- [ ] A unique, strong `SUPERSET_SECRET_KEY` is generated and secured in an environment variable or secrets vault.
+- [ ] Server-side session management is configured (e.g., Redis).
+- [ ] `PERMANENT_SESSION_LIFETIME` is set to a short duration (e.g., 8 hours).
+- [ ] All session cookie security flags (`Secure`, `HttpOnly`, `SameSite`) are enabled.
+- [ ] `DEBUG` mode is set to `False`.
+- [ ] Talisman is explicitly enabled and configured with a strict Content Security Policy.
+- [ ] Database connections use dedicated, limited-privilege accounts.
+- [ ] Authentication is integrated with an enterprise identity provider (OAuth/LDAP).
+- [ ] A Web Application Firewall (WAF) is deployed in front of Superset.
+- [ ] Logging is configured and logs are shipped to a central monitoring system.
 
 #### **Ongoing Maintenance:**
 
-  - [ ] Regularly update to the latest major or minor versions of Superset. Those versions receive up-to-date security patches.
-  - [ ] Rotate the `SUPERSET_SECRET_KEY` periodically (e.g., quarterly) and after any potential security incident.
-  - [ ] Conduct quarterly access reviews for all users.
-  - [ ] Assuming logging and monitoring is in place, review security monitoring alerts weekly.
+- [ ] Regularly update to the latest major or minor versions of Superset. Those versions receive up-to-date security patches.
+- [ ] Rotate the `SUPERSET_SECRET_KEY` periodically (e.g., quarterly) and after any potential security incident.
+- [ ] Conduct quarterly access reviews for all users.
+- [ ] Assuming logging and monitoring is in place, review security monitoring alerts weekly.
 
 ### **Appendix B: `SECRET_KEY` Rotation and Compromise Response**
 
@@ -174,6 +175,7 @@ The procedure for safely rotating the SECRET_KEY must be followed precisely to a
 https://superset.apache.org/admin-docs/configuration/configuring-superset/#rotating-to-a-newer-secret_key
 
 :::resources
+
 - [Blog: Running Apache Superset on the Open Internet](https://preset.io/blog/running-apache-superset-on-the-open-internet-a-report-from-the-fireline/)
 - [Blog: How Security Vulnerabilities are Reported & Handled in Apache Superset](https://preset.io/blog/how-security-vulnerabilities-are-reported-and-handled-in-apache-superset/)
-:::
+  :::

docs/admin_docs_versioned_docs/version-6.1.0/security/security.mdx

@@ -24,13 +24,13 @@ A table with the permissions for these roles can be found at [/RESOURCES/STANDAR
 Admins have all possible rights, including granting or revoking rights from other
 users and altering other people’s slices and dashboards.
 
->#### Threat Model and Privilege Boundaries: The Admin Role
+> #### Threat Model and Privilege Boundaries: The Admin Role
 >
->Apache Superset is built with a granular permission model where users assigned the Admin role are considered fully trusted. Admins possess complete control over the application's configuration, UI rendering, and access controls.
+> Apache Superset is built with a granular permission model where users assigned the Admin role are considered fully trusted. Admins possess complete control over the application's configuration, UI rendering, and access controls.
 >
->Consequently, actions performed by an Admin that alter the application's behavior or presentation—such as injecting custom CSS, modifying Jinja templates, or altering security flags—are intended administrative capabilities by design.
+> Consequently, actions performed by an Admin that alter the application's behavior or presentation—such as injecting custom CSS, modifying Jinja templates, or altering security flags—are intended administrative capabilities by design.
 >
->In accordance with MITRE CNA Rule 4.1, a vulnerability must represent a violation of an explicit security policy. Because the Admin role is defined as a trusted operational boundary, actions executed with Admin privileges do not cross a security perimeter. Therefore, exploit vectors that strictly require Admin access are not classified as security vulnerabilities and are ineligible for CVE assignment.
+> In accordance with MITRE CNA Rule 4.1, a vulnerability must represent a violation of an explicit security policy. Because the Admin role is defined as a trusted operational boundary, actions executed with Admin privileges do not cross a security perimeter. Therefore, exploit vectors that strictly require Admin access are not classified as security vulnerabilities and are ineligible for CVE assignment.
 
 ### Alpha
 
@@ -54,10 +54,10 @@ to all databases by default, both **Alpha** and **Gamma** users need to be given
 
 Beyond the base `sql_lab` role, two additional SQL Lab permissions must be explicitly granted for users who need these capabilities:
 
-| Permission | Feature |
-|------------|---------|
-| `can_estimate_query_cost` on `SQLLab` | Estimate query cost before running |
-| `can_format_sql` on `SQLLab` | Format SQL using the database's dialect |
+| Permission                            | Feature                                 |
+| ------------------------------------- | --------------------------------------- |
+| `can_estimate_query_cost` on `SQLLab` | Estimate query cost before running      |
+| `can_format_sql` on `SQLLab`          | Format SQL using the database's dialect |
 
 Grant these in **Security → List Roles** by adding the permissions to the relevant role.
 
@@ -73,6 +73,7 @@ users who need to view dashboards. It provides minimal read-only access for:
 - Viewing annotations on charts
 
 The Public role explicitly excludes:
+
 - Any write permissions on dashboards, charts, or datasets
 - SQL Lab access
 - Share functionality
@@ -161,12 +162,14 @@ With this enabled, you can assign specific roles to each dashboard in its proper
 will only see dashboards where their role is explicitly added.
 
 **Important considerations:**
+
 - Dashboard access **bypasses** dataset-level checks—granting a role access to a dashboard
   implicitly grants read access to all charts and datasets in that dashboard
 - Dashboards without any assigned roles fall back to dataset-based access
 - The dashboard must still be published to be visible
 
 This feature is particularly useful for:
+
 - Making specific dashboards public while keeping others private
 - Granting access to dashboards without exposing the underlying datasets for other uses
 - Creating dashboard-specific access patterns that don't align with dataset ownership
@@ -184,10 +187,11 @@ However, it is crucial to understand the following:
 **Database Security is Paramount**: The ultimate responsibility for securing database access, controlling permissions, and preventing unauthorized function execution lies with the database administrators (DBAs) and security teams managing the underlying database instance.
 
 **Recommended Database Practices**: We strongly recommend implementing security best practices at the database level, including:
-* **Least Privilege**: Connecting Superset using dedicated database user accounts with the minimum permissions required for Superset's operation (typically read-only access to necessary schemas/tables).
-* **Database Roles & Permissions**: Utilizing database-native roles and permissions to restrict access to sensitive functions, system variables (like `@@hostname`), schemas, or tables.
-* **Network Security**: Employing network-level controls like database firewalls or proxies to restrict connections.
-* **Auditing**: Enabling database-level auditing to monitor executed queries and access patterns.
+
+- **Least Privilege**: Connecting Superset using dedicated database user accounts with the minimum permissions required for Superset's operation (typically read-only access to necessary schemas/tables).
+- **Database Roles & Permissions**: Utilizing database-native roles and permissions to restrict access to sensitive functions, system variables (like `@@hostname`), schemas, or tables.
+- **Network Security**: Employing network-level controls like database firewalls or proxies to restrict connections.
+- **Auditing**: Enabling database-level auditing to monitor executed queries and access patterns.
 
 By combining Superset's configurable safeguards with strong database-level security practices, you can achieve a more robust and layered security posture.
 
@@ -341,11 +345,11 @@ rules are:
 
 For example, if a dataset has three filters:
 
-| Filter | Clause | Group Key |
-|--------|--------|-----------|
-| F1 | `department = 'Finance'` | `department` |
-| F2 | `department = 'Marketing'` | `department` |
-| F3 | `region = 'Europe'` | `region` |
+| Filter | Clause                     | Group Key    |
+| ------ | -------------------------- | ------------ |
+| F1     | `department = 'Finance'`   | `department` |
+| F2     | `department = 'Marketing'` | `department` |
+| F3     | `region = 'Europe'`        | `region`     |
 
 The resulting WHERE clause would be:
 
@@ -429,7 +433,7 @@ GET /api/v1/rowlevelsecurity/<id>
 ```
 
 The response includes the filter's `name`, `filter_type` (Regular or Base), `clause`,
-`group_key`, assigned `tables` (with id, schema, and table\_name), and assigned `roles`
+`group_key`, assigned `tables` (with id, schema, and table_name), and assigned `roles`
 (with id and name).
 
 :::tip Auditing RLS for virtual datasets
@@ -476,13 +480,13 @@ This reduces the risk for replay attacks and session hijacking.
 Superset uses [Flask-Session](https://flask-session.readthedocs.io/en/latest/) to manage server side sessions.
 To enable this extension you have to set:
 
-``` python
+```python
 SESSION_SERVER_SIDE = True
 ```
 
 Flask-Session offers multiple backend session interfaces for Flask, here's an example for Redis:
 
-``` python
+```python
 from redis import Redis
 
 SESSION_TYPE = "redis"
@@ -511,8 +515,8 @@ It's extremely important to correctly configure a Content Security Policy when d
 prevent many types of attacks. Superset provides two variables in `config.py` for deploying a CSP:
 
 - `TALISMAN_ENABLED` defaults to `True`; set this to `False` in order to disable CSP
-- `TALISMAN_CONFIG` holds the actual the policy definition (*see example below*) as well as any
-other arguments to be passed to Talisman.
+- `TALISMAN_CONFIG` holds the actual the policy definition (_see example below_) as well as any
+  other arguments to be passed to Talisman.
 
 When running in production mode, Superset will check at startup for the presence
 of a CSP. If one is not found, it will issue a warning with the security risks. For environments
@@ -528,12 +532,12 @@ this warning using the `CONTENT_SECURITY_POLICY_WARNING` key in `config.py`.
   ```
 
 - Only scripts marked with a [nonce](https://content-security-policy.com/nonce/) can be loaded and executed.
-Nonce is a random string automatically generated by Talisman on each page load.
-You can get current nonce value by calling jinja macro `csp_nonce()`.
+  Nonce is a random string automatically generated by Talisman on each page load.
+  You can get current nonce value by calling jinja macro `csp_nonce()`.
 
   ```html
   <script nonce="{{ csp_nonce() }}">
-  /* my script */
+    /* my script */
   </script>
   ```
 
@@ -551,7 +555,7 @@ You can get current nonce value by calling jinja macro `csp_nonce()`.
   ```
 
 - Cartodiagram charts request map data (image and json) from external resources that can be edited by users,
-and therefore either require a list of allowed domains to request from or a wildcard (`'*'`) for `img-src` and `connect-src`.
+  and therefore either require a list of allowed domains to request from or a wildcard (`'*'`) for `img-src` and `connect-src`.
 
 - Other CSP directives default to `'self'` to limit content to the same origin as the Superset server.
 
@@ -562,12 +566,12 @@ In order to adjust provided CSP configuration to your needs, follow the instruct
 
 Setting `TALISMAN_ENABLED = True` will invoke Talisman's protection with its default arguments,
 of which `content_security_policy` is only one. Those can be found in the
-[Talisman documentation](https://pypi.org/project/flask-talisman/) under *Options*.
+[Talisman documentation](https://pypi.org/project/flask-talisman/) under _Options_.
 These generally improve security, but administrators should be aware of their existence.
 
 In particular, the option of `force_https = True` (`False` by default) may break Superset's Alerts & Reports
 if workers are configured to access charts via a `WEBDRIVER_BASEURL` beginning
-with `http://`.  As long as a Superset deployment enforces https upstream, e.g.,
+with `http://`. As long as a Superset deployment enforces https upstream, e.g.,
 through a load balancer or application gateway, it should be acceptable to keep this
 option disabled. Otherwise, you may want to enable `force_https` like this:
 

docs/admin_docs_versions.json

@@ -1,3 +1 @@
-[
-  "6.1.0"
-]
+["6.1.0"]

docs/components/chart-components/bar-chart.md

@@ -16,7 +16,9 @@
     specific language governing permissions and limitations
     under the License.
 -->
+
 ---
+
 title: Bar Chart
 sidebar_position: 1
 ---
@@ -27,18 +29,18 @@ The Bar Chart component is used to visualize categorical data with rectangular b
 
 ## Props
 
-| Prop | Type | Default | Description |
-|------|------|---------|-------------|
-| `data` | `array` | `[]` | Array of data objects to visualize |
-| `width` | `number` | `800` | Width of the chart in pixels |
-| `height` | `number` | `600` | Height of the chart in pixels |
-| `xField` | `string` | - | Field name for x-axis values |
-| `yField` | `string` | - | Field name for y-axis values |
-| `colorField` | `string` | - | Field name for color encoding |
-| `colorScheme` | `string` | `'supersetColors'` | Color scheme to use |
-| `showLegend` | `boolean` | `true` | Whether to show the legend |
-| `showGrid` | `boolean` | `true` | Whether to show grid lines |
-| `labelPosition` | `string` | `'top'` | Position of bar labels: 'top', 'middle', 'bottom' |
+| Prop            | Type      | Default            | Description                                       |
+| --------------- | --------- | ------------------ | ------------------------------------------------- |
+| `data`          | `array`   | `[]`               | Array of data objects to visualize                |
+| `width`         | `number`  | `800`              | Width of the chart in pixels                      |
+| `height`        | `number`  | `600`              | Height of the chart in pixels                     |
+| `xField`        | `string`  | -                  | Field name for x-axis values                      |
+| `yField`        | `string`  | -                  | Field name for y-axis values                      |
+| `colorField`    | `string`  | -                  | Field name for color encoding                     |
+| `colorScheme`   | `string`  | `'supersetColors'` | Color scheme to use                               |
+| `showLegend`    | `boolean` | `true`             | Whether to show the legend                        |
+| `showGrid`      | `boolean` | `true`             | Whether to show grid lines                        |
+| `labelPosition` | `string`  | `'top'`            | Position of bar labels: 'top', 'middle', 'bottom' |
 
 ## Examples
 

docs/components/index.md

@@ -16,7 +16,9 @@
     specific language governing permissions and limitations
     under the License.
 -->
+
 ---
+
 title: Component Library
 sidebar_position: 1
 ---