fix(charts): fix Bubble chart crash and correct example's time_range to a year with real data

Two issues surfaced while verifying #42328's live thumbnail-capture work against this example chart: 1. Bubble/transformProps.ts set `xAxis.interval` directly from the xAxisLabelInterval control ('auto'/'0'), but xAxis.interval forces echarts' IntervalScale into a fixed-tick-spacing mode that expects a number. This crashed the axis "nice" tick calculation for every bubble_v2 chart -- not just this example, any bubble chart with the control at its default. The interval belongs nested under axisLabel, where it only controls how many labels are skipped, matching how every other echarts chart in this codebase (e.g. Timeseries) wires it. There was no existing test coverage for this file; added one. 2. Once the crash was fixed, the chart rendered with zero visible bubbles: the previous commit's `time_range` (2014, matching the convention used by sibling examples on this dataset) has zero non-null SP_DYN_LE00_IN (life expectancy) values in this particular dataset. The original legacy chart's own choice of 2011 was deliberate -- that year has real data for all three metrics used.
fix(examples): migrate Life Expectancy VS Rural % example off the removed legacy bubble viz_type
2026-09-09 16:54:29 +00:00 · 2026-08-14 14:05:06 -07:00 · 2026-08-13 22:52:33 -07:00
1526 changed files with 62100 additions and 148774 deletions
@@ -3,7 +3,9 @@ codecov:
        after_n_builds: 4
 ignore:
  - "superset/migrations/versions/*.py"
+  - "superset-frontend/packages/superset-ui-demo/**/*"
  - "**/*.stories.tsx"
+  - "**/*.stories.jsx"
 coverage:
  status:
    project:
@@ -19,7 +19,7 @@

 # Notify PMC members of changes to extension-related files

-/docs/developer_docs/extensions/ @michael-s-molina @villebro @rusackas
+/docs/developer_portal/extensions/ @michael-s-molina @villebro @rusackas
 /superset-extensions-cli/ @michael-s-molina @villebro @rusackas @sadpandajoe
 /superset/extensions/ @michael-s-molina @villebro @rusackas @sadpandajoe
 /superset-frontend/src/extensions/ @michael-s-molina @villebro @rusackas @sadpandajoe
@@ -1,6 +1,6 @@
 name: Bug report
 description: Report a bug to improve Superset's stability
-labels: ["#bug"]
+labels: ["bug"]
 body:
  - type: markdown
    attributes:
@@ -1,7 +1,7 @@
 ---
 name: Cosmetic Issue
 about: Describe a cosmetic issue with CSS, positioning, layout, labeling, or similar
-labels: "#bug:cosmetic"
+labels: "cosmetic-issue"
 ---

 ## Screenshot
@@ -5,10 +5,6 @@ updates:
    directory: "/"
    schedule:
      interval: "daily"
-    groups:
-      security:
-        applies-to: "security-updates"
-        patterns: ["*"]
    cooldown:
      default-days: 7

@@ -24,6 +20,14 @@ updates:
      - dependency-name: "@types/react-dom"
        update-types: ["version-update:semver-major"]
      - dependency-name: "react-icons"
+      # JSDOM v30 doesn't play well with Jest v30
+      # Source: https://jestjs.io/blog#known-issues
+      # GH thread: https://github.com/jsdom/jsdom/issues/3492
+      - dependency-name: "jest-environment-jsdom"
+      # `@swc/plugin-transform-imports` doesn't work with current Webpack-SWC hybrid setup
+      # See https://github.com/apache/superset/pull/37384#issuecomment-3793991389
+      # TODO: remove the plugin once Lodash usage has been migrated to a more readily tree-shakeable alternative
+      - dependency-name: "@swc/plugin-transform-imports"
      # deck.gl and luma.gl share strict peer constraints across the root and
      # plugin workspaces, and root overrides pin their transitive versions.
      # Upgrade both families together in a manually validated change.
@@ -57,9 +61,6 @@ updates:
      - npm
      - dependabot
    groups:
-      security:
-        applies-to: "security-updates"
-        patterns: ["*"]
      rjsf:
        patterns:
          - "@rjsf/*"
@@ -79,23 +80,6 @@ updates:
        patterns:
          - "ag-grid-react"
          - "ag-grid-community"
-      swc:
-        patterns:
-          - "@swc/core"
-          - "@swc/plugin-emotion"
-          - "@swc/plugin-transform-imports"
-      jsonforms:
-        patterns:
-          - "@jsonforms/*"
-      visx:
-        patterns:
-          - "@visx/*"
-      emotion:
-        patterns:
-          - "@emotion/*"
-      fontsource:
-        patterns:
-          - "@fontsource/*"
    open-pull-requests-limit: 30
    versioning-strategy: increase
    cooldown:
@@ -114,10 +98,6 @@ updates:
    labels:
      - pip
      - dependabot
-    groups:
-      security:
-        applies-to: "security-updates"
-        patterns: ["*"]
    cooldown:
      default-days: 7

@@ -125,10 +105,6 @@ updates:
    directory: ".github/actions"
    schedule:
      interval: "daily"
-    groups:
-      security:
-        applies-to: "security-updates"
-        patterns: ["*"]
    open-pull-requests-limit: 10
    versioning-strategy: increase
    cooldown:
@@ -139,9 +115,6 @@ updates:
    schedule:
      interval: "daily"
    groups:
-      security:
-        applies-to: "security-updates"
-        patterns: ["*"]
      storybook:
        patterns:
          - "@storybook/*"
@@ -169,10 +142,6 @@ updates:
    labels:
      - npm
      - dependabot
-    groups:
-      security:
-        applies-to: "security-updates"
-        patterns: ["*"]
    versioning-strategy: increase
    cooldown:
      default-days: 7
@@ -184,29 +153,7 @@ updates:
    labels:
      - npm
      - dependabot
-    groups:
-      security:
-        applies-to: "security-updates"
-        patterns: ["*"]
    open-pull-requests-limit: 10
    versioning-strategy: increase
    cooldown:
      default-days: 7
-
-  - package-ecosystem: "npm"
-    directory: "/superset-embedded-sdk/"
-    schedule:
-      interval: "daily"
-    labels:
-      - npm
-      - dependabot
-    groups:
-      security:
-        applies-to: "security-updates"
-        patterns: ["*"]
-      babel:
-        patterns:
-          - "@babel/*"
-    versioning-strategy: increase
-    cooldown:
-      default-days: 7
@@ -29,7 +29,7 @@
 "dependencies:python":
 - changed-files:
  - any-glob-to-any-file:
-    - 'requirements/**'
+    - 'superset/requirements/**'
    - 'superset/translations/requirements.txt'
    - 'RELEASING/requirements.txt'

@@ -21,9 +21,6 @@ on:
  #schedule:
  #  - cron: '0 0 * * *'  # Runs daily at midnight UTC

-permissions:
-  contents: read
-
 jobs:
  bump-python-package:
    runs-on: ubuntu-slim
@@ -48,7 +45,7 @@ jobs:
          python-version: "3.11"

      - name: Install uv
-        uses: astral-sh/setup-uv@20cfd1bf945f4377ade1205e4dbc17946fc9a30d # v10.0.1
+        uses: astral-sh/setup-uv@c771a70e6277c0a99b617c7a806ffedaca235ff9 # v9.0.0
        with:
          python-version: "3.11"
          enable-cache: true
@@ -16,9 +16,6 @@ concurrency:
  group: ${{ github.workflow }}-${{ github.event.pull_request.number || github.run_id }}
  cancel-in-progress: true

-permissions:
-  contents: read
-
 jobs:
  check_db_migration_conflict:
    name: Check DB migration conflict
@@ -1,99 +0,0 @@
-# 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
-# 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
-#
-#   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
-# specific language governing permissions and limitations
-# under the License.
-name: Check OpenAPI spec drift
-on:
-  push:
-    branches:
-      - "master"
-      - "[0-9].[0-9]*"
-  pull_request:
-    types: [synchronize, opened, reopened, ready_for_review]
-
-# Deliberately unfiltered by `paths`: a required check that does not run on a
-# PR blocks it from merging forever.
-
-concurrency:
-  group: ${{ github.workflow }}-${{ github.event.pull_request.number || github.run_id }}
-  cancel-in-progress: true
-
-permissions:
-  contents: read
-
-jobs:
-  check-openapi-spec-drift:
-    runs-on: ubuntu-26.04
-    steps:
-      - name: "Checkout ${{ github.ref }} ( ${{ github.sha }} )"
-        uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
-        with:
-          persist-credentials: false
-      - name: Setup Python
-        uses: ./.github/actions/setup-backend/
-        with:
-          # The generated output depends on the pinned apispec version.
-          requirements-type: base
-      - name: Regenerate the spec
-        env:
-          # No config file: the spec documents what a default deployment
-          # registers, so feature flags must stay off.
-          SUPERSET__SQLALCHEMY_DATABASE_URI: "sqlite:///:memory:"
-          FLASK_APP: "superset.app:create_app()"
-        run: superset update-api-docs
-      - name: Assert the published spec is up to date
-        env:
-          SPEC: docs/static/resources/openapi.json
-        run: |
-          if git diff --quiet -- "$SPEC"; then
-            exit 0
-          fi
-
-          # Staged to a file, not piped: `head` closing the pipe would
-          # SIGPIPE-kill `git diff` under pipefail and abort this step.
-          diff_file="$RUNNER_TEMP/openapi.diff"
-          git diff -- "$SPEC" > "$diff_file"
-
-          regen="SUPERSET__SQLALCHEMY_DATABASE_URI='sqlite:///:memory:' FLASK_APP='superset.app:create_app()' superset update-api-docs"
-
-          echo "::error::$SPEC is stale. Regenerate it on the pinned requirements:"
-          echo "$regen"
-          git diff --stat -- "$SPEC"
-
-          # Summaries cap at 1 MiB, well under a full regeneration.
-          {
-            echo '### OpenAPI spec is stale'
-            echo
-            git diff --stat -- "$SPEC"
-            echo
-            echo 'Regenerate with:'
-            echo
-            echo '```bash'
-            echo "$regen"
-            echo '```'
-            echo
-            echo '```diff'
-            head -300 "$diff_file"
-            echo '```'
-            if [ "$(wc -l < "$diff_file")" -gt 300 ]; then
-              echo
-              echo '_Truncated at 300 lines; see the job log for the full diff._'
-            fi
-          } >> "$GITHUB_STEP_SUMMARY"
-
-          echo "::group::Full diff"
-          cat "$diff_file"
-          echo "::endgroup::"
-          exit 1
@@ -14,9 +14,6 @@ concurrency:
  group: ${{ github.workflow }}-${{ github.event.pull_request.number || github.run_id }}
  cancel-in-progress: true

-permissions:
-  contents: read
-
 jobs:
  changes:
    runs-on: ubuntu-26.04
@@ -67,7 +64,7 @@ jobs:

      # Initializes the CodeQL tools for scanning.
      - name: Initialize CodeQL
-        uses: github/codeql-action/init@cdf488f595d80d6e07e03d4674febd5ab45fa938 # v4.37.9
+        uses: github/codeql-action/init@5595ccaf912efad79be6eef63a5619ff05969be3 # v4.37.6
        with:
          languages: ${{ matrix.language }}
          # If you wish to specify custom queries, you can do so here or in a config file.
@@ -78,6 +75,6 @@ jobs:
          # queries: security-extended,security-and-quality

      - name: Perform CodeQL Analysis
-        uses: github/codeql-action/analyze@cdf488f595d80d6e07e03d4674febd5ab45fa938 # v4.37.9
+        uses: github/codeql-action/analyze@5595ccaf912efad79be6eef63a5619ff05969be3 # v4.37.6
        with:
          category: "/language:${{matrix.language}}"
@@ -66,27 +66,6 @@ jobs:

      - name: "Set up liccheck"
        run: |
-          # liccheck (as of 0.9.2) still does a bare `import pkg_resources`
-          # without declaring setuptools as a dependency, relying on it
-          # having historically been bundled. setuptools 81+ (installed
-          # above via requirements/base.txt) dropped the pkg_resources
-          # subpackage entirely, so liccheck's own import breaks outright.
-          #
-          # Reinstalling an older setuptools would restore pkg_resources but
-          # would also downgrade the *real* setuptools install, which then
-          # trips liccheck's own working_set.resolve() -- it cross-checks
-          # requirements/base.txt's declared `setuptools==84.0.0` against
-          # what's actually installed, and a downgrade makes those disagree.
-          #
-          # Instead, vendor just the pkg_resources/ package files from an
-          # old setuptools wheel into site-packages, leaving the real
-          # setuptools install (and its dist-info metadata) untouched. This
-          # gives liccheck an importable pkg_resources whose own working-set
-          # scan still correctly reports the real installed setuptools
-          # version, so no conflict is raised.
-          pip download "setuptools<81" --no-deps -d /tmp/old-setuptools
-          python -m zipfile -e /tmp/old-setuptools/setuptools-*.whl /tmp/old-setuptools-extracted/
-          cp -r /tmp/old-setuptools-extracted/pkg_resources "$(python -c 'import site; print(site.getsitepackages()[0])')/"
          uv pip install --system liccheck
      - name: "Run liccheck"
        run: |
@@ -51,53 +51,6 @@ jobs:
          echo "matrix_config=${MATRIX_CONFIG}" >> $GITHUB_OUTPUT
          echo $GITHUB_OUTPUT

-  # Runs unconditionally (no dependency on `changes`, and no build-preset
-  # matrix restriction) so a regression in the PY_VER override logic is
-  # always caught on PRs. Without this, the real docker-build job only runs
-  # when the change detector flags docker/python/frontend changes (a
-  # workflow-only edit like this one does not), and even then the PR build
-  # matrix never includes the "py311"/"py312" presets that logic protects -
-  # so a break here would otherwise first surface on a push to master.
-  pyver-override-check:
-    name: verify docker build PY_VER override
-    runs-on: ubuntu-26.04
-    timeout-minutes: 5
-    steps:
-      - name: Checkout
-        uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
-        with:
-          persist-credentials: false
-      - name: Setup supersetbot
-        uses: ./.github/actions/setup-supersetbot/
-      - name: Assert PY_VER override applies to every preset except py311/py312
-        shell: bash
-        env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-        run: |
-          set -euo pipefail
-          # Asserts against the actual buildx command line `supersetbot docker
-          # --dry-run` would run, not just this repo's own extra-flags helper,
-          # so a regression in supersetbot itself (dropping the py311/py312
-          # PY_VER pin, or reordering args so our override no longer lands
-          # last) is caught here too, instead of only surfacing on master.
-          assert_effective_py_ver() {
-            local preset="$1" expected="$2" extra_flags command actual
-            extra_flags="$(scripts/docker-build-extra-flags.sh "$preset" dummy-tag)"
-            command="$(supersetbot docker --preset "$preset" --platform linux/amd64 --extra-flags "$extra_flags" --dry-run)"
-            # docker buildx keeps the LAST value of a repeated --build-arg key.
-            actual="$(grep -oE -- '--build-arg PY_VER=[^[:space:]]+' <<<"$command" | tail -1)"
-            if [ "$actual" != "--build-arg PY_VER=$expected" ]; then
-              echo "::error::preset '$preset' expected effective --build-arg PY_VER=$expected, got: ${actual:-<none>} (full command: $command)"
-              exit 1
-            fi
-          }
-          for preset in dev lean websocket dockerize; do
-            assert_effective_py_ver "$preset" "3.11.14-slim-trixie"
-          done
-          assert_effective_py_ver py311 "3.11-slim-bookworm"
-          assert_effective_py_ver py312 "3.12-slim-bookworm"
-          echo "PY_VER override logic verified against the assembled buildx command for all build presets"
-
  docker-build:
    name: docker-build
    needs: [setup_matrix, changes]
@@ -171,21 +124,19 @@ jobs:
          # the whole job. buildx reuses the buildkit layer cache from the
          # failed attempt, so a retry mostly re-does just the failed push.
          #
-          # See scripts/docker-build-extra-flags.sh for why "py311"/"py312"
-          # are excluded from the PY_VER override applied to every other
-          # preset; that logic is also exercised on every PR by the
-          # always-on pyver-override-check job below, since this job itself
-          # only runs when the change detector flags docker/python/frontend
-          # changes and the PR build matrix never includes py311/py312.
-          EXTRA_FLAGS="$(scripts/docker-build-extra-flags.sh "$BUILD_PRESET" "$IMAGE_TAG")"
-
+          # supersetbot's "dev"/"lean" presets pin their own --build-arg
+          # PY_VER, which lands ahead of --extra-flags on the assembled
+          # buildx command line; docker/buildx keeps the last value for a
+          # repeated --build-arg key, so appending PY_VER here overrides
+          # supersetbot's pin and keeps the build on the Dockerfile's own
+          # supported Python version.
          for attempt in 1 2 3; do
            if supersetbot docker \
              $PUSH_OR_LOAD \
              --preset "$BUILD_PRESET" \
              --context "$EVENT" \
              --context-ref "$RELEASE" $FORCE_LATEST \
-              --extra-flags "$EXTRA_FLAGS" \
+              --extra-flags "--build-arg PY_VER=3.11.14-slim-trixie --build-arg INCLUDE_CHROMIUM=false --tag $IMAGE_TAG" \
              $PLATFORM_ARG; then
              break
            fi
@@ -213,29 +164,6 @@ jobs:
          docker images $IMAGE_TAG
          docker history $IMAGE_TAG

-      - name: WebSocket server smoke test
-        if: contains(fromJson('["lean", "dev"]'), matrix.build_preset)
-        shell: bash
-        run: |
-          # The realtime WebSocket server is bundled in the official image and
-          # launched via an alternate entrypoint; verify the bundled Node runtime
-          # starts it and it serves /health. (A JWT secret >= 32 bytes is required
-          # or the server refuses to start; no Redis is needed for /health.)
-          # Both presets are checked because docker-compose-non-dev.yml runs the
-          # websocket service from the dev target.
-          docker run -d --name superset-ws \
-            -e JWT_SECRET="ci-smoke-test-secret-ci-smoke-test-secret" \
-            -e PORT=8080 -p 8080:8080 \
-            "$IMAGE_TAG" /app/docker/entrypoints/run-websocket.sh
-          ok=""
-          for _ in $(seq 1 20); do
-            if curl -sf http://localhost:8080/health; then echo "ws /health OK"; ok=1; break; fi
-            sleep 2
-          done
-          docker logs superset-ws || true
-          docker rm -f superset-ws || true
-          [ "$ok" = "1" ] || { echo "::error::websocket /health did not come up"; exit 1; }
-
      - name: docker-compose sanity check
        if: matrix.build_preset == 'dev'
        shell: bash
@@ -289,7 +217,7 @@ jobs:
  actions-timeline:
    needs: [docker-build, docker-compose-image-tag]
    if: always()
-    runs-on: ubuntu-slim
+    runs-on: ubuntu-26.04
    permissions:
      actions: read
    steps:
@@ -33,9 +33,6 @@ concurrency:
  group: ${{ github.workflow }}-${{ github.event.pull_request.number || github.run_id }}
  cancel-in-progress: true

-permissions:
-  contents: read
-
 jobs:
  enforce-single-migration-head:
    runs-on: ubuntu-26.04
@@ -1,136 +0,0 @@
-name: Frontend bundle size (nightly baseline + analyzer)
-
-# Refreshes the bundle-size baseline that superset-frontend.yml's `bundle-size`
-# job compares PRs against, and publishes a browsable bundle-analyzer treemap
-# report of the same build. Deliberately NOT triggered on every push to
-# master: a day-old baseline/report is fine for catching relative
-# regressions on PRs and for browsing what's actually in the bundle, and
-# building the production bundle on every one of the many pushes master
-# gets per day would burn CI time for no benefit a nightly refresh doesn't
-# already cover.
-on:
-  schedule:
-    - cron: "0 6 * * *"
-  workflow_dispatch: {}
-
-concurrency:
-  group: ${{ github.workflow }}
-  cancel-in-progress: true
-
-env:
-  TAG: apache/superset:bundle-size-nightly-${{ github.run_id }}
-
-permissions:
-  contents: read
-
-jobs:
-  refresh-baseline:
-    runs-on: ubuntu-26.04
-    timeout-minutes: 30
-    env:
-      NETLIFY_SITE_ID: ${{ secrets.NETLIFY_BUNDLE_ANALYZER_SITE_ID }}
-    steps:
-      - name: "Checkout master"
-        uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
-        with:
-          persist-credentials: false
-          ref: master
-
-      - name: Build Docker Image
-        run: |
-          docker buildx build \
-            -t $TAG \
-            --cache-from=type=registry,ref=apache/superset-cache:3.11-slim-trixie \
-            --target superset-node-ci \
-            .
-
-      # Same cache the PR-time bundle-size job restores/writes -- webpack's
-      # persistent filesystem cache turns a warm production build into ~20s
-      # instead of several minutes. See superset-frontend.yml for the
-      # matching restore step and why it's keyed this way.
-      - name: Restore webpack build cache
-        uses: actions/cache@55cc8345863c7cc4c66a329aec7e433d2d1c52a9 # v6.1.0
-        with:
-          path: superset-frontend/.temp_cache
-          key: >-
-            webpack-prod-cache-${{ hashFiles('superset-frontend/package-lock.json',
-            'superset-frontend/babel.config.js', 'superset-frontend/tsconfig.json',
-            'superset-frontend/webpack.config.js') }}
-
-      # Only ever pull the last recorded data point off the cache, keyed by
-      # run ID -- `restore-keys` prefix-matches the most recently created
-      # entry. Absent on the very first run ever; benchmark-action starts a
-      # fresh history in that case.
-      - name: Restore bundle size history
-        uses: actions/cache/restore@55cc8345863c7cc4c66a329aec7e433d2d1c52a9 # v6.1.0
-        with:
-          path: bundle-size-history.json
-          key: bundle-size-history-${{ github.run_id }}
-          restore-keys: |
-            bundle-size-history-
-
-      # BUNDLE_ANALYZER rides along in the same build as BUNDLE_SIZE_STATS --
-      # they're independent env-gated additions in webpack.config.js (one
-      # sets `config.stats`, the other pushes plugins), so one production
-      # build produces both the numeric stats.json and the analyzer's
-      # report.html. Only report.html is mounted out, not
-      # BUNDLE_ANALYZER's sibling `statistics.html` sunburst -- that file is
-      # documented in webpack.config.js as routinely exceeding 100MB for
-      # this app (it's .gitignore'd for exactly that reason), too large to
-      # publish as a static site page.
-      - name: Build production bundle with stats and analyzer report
-        run: |
-          mkdir -p ${{ github.workspace }}/superset-frontend/bundle-stats
-          mkdir -p ${{ github.workspace }}/superset-frontend/.temp_cache
-          mkdir -p ${{ github.workspace }}/superset/static/assets
-          docker run \
-          -v ${{ github.workspace }}/superset-frontend/bundle-stats:/app/superset-frontend/bundle-stats \
-          -v ${{ github.workspace }}/superset-frontend/.temp_cache:/app/superset-frontend/.temp_cache \
-          -v ${{ github.workspace }}/superset/static/assets:/app/superset/static/assets \
-          --rm $TAG \
-          bash -c \
-          "npm i && BUNDLE_SIZE_STATS=true BUNDLE_ANALYZER=true npm run build -- --json=bundle-stats/stats.json"
-
-      - name: Summarize bundle size
-        run: |
-          node superset-frontend/scripts/bundle-size-summary.js \
-            superset-frontend/bundle-stats/stats.json > bundle-size-summary.json
-          rm -rf superset-frontend/bundle-stats
-
-      # No PR to comment on here, so comment-on-alert is off -- the job
-      # summary (summary-always) is the only surface for this run.
-      - name: Update bundle size baseline
-        uses: benchmark-action/github-action-benchmark@52576c92bccf6ac60c8223ec7eb2565637cae9ba # v1.22.1
-        with:
-          tool: customSmallerIsBetter
-          output-file-path: bundle-size-summary.json
-          external-data-json-path: bundle-size-history.json
-          github-token: ${{ secrets.GITHUB_TOKEN }}
-          fail-on-alert: false
-          summary-always: true
-
-      - name: Save bundle size history
-        uses: actions/cache/save@55cc8345863c7cc4c66a329aec7e433d2d1c52a9 # v6.1.0
-        with:
-          path: bundle-size-history.json
-          key: bundle-size-history-${{ github.run_id }}
-
-      # Publishes the treemap to Netlify (the same host already used for
-      # superset-storybook.netlify.app and docs previews, reusing the
-      # existing NETLIFY_AUTH_TOKEN). Skipped until
-      # NETLIFY_BUNDLE_ANALYZER_SITE_ID exists -- create a new (free)
-      # Netlify site named superset-bundle-analyzer and add its site ID as
-      # that secret to turn this on; nothing else in this workflow depends
-      # on it.
-      - name: Publish bundle analyzer report to Netlify
-        if: ${{ env.NETLIFY_SITE_ID != '' }}
-        env:
-          NETLIFY_AUTH_TOKEN: ${{ secrets.NETLIFY_AUTH_TOKEN }}
-        run: |
-          mkdir -p netlify-publish
-          cp superset/static/assets/report.html netlify-publish/index.html
-          # zizmor: ignore[adhoc-packages] - netlify-cli is a one-shot CI deploy
-          # tool, not an application dependency; a global/npx install has no
-          # lockfile context. Version pinned above the floor set by other
-          # ad-hoc installs in this repo (bump deliberately when upgrading).
-          npx --yes netlify-cli@27.0.1 deploy --prod --dir=netlify-publish
@@ -37,7 +37,7 @@ jobs:
          persist-credentials: false
          submodules: recursive
      - name: Setup Java
-        uses: actions/setup-java@dd06d9cba3e5552c54d9f8ea23572deb30010f7c # v6.0.0
+        uses: actions/setup-java@b6effb05e454b25005698d916606bdc6ffcbf961 # v5.7.0
        with:
          distribution: "temurin"
          java-version: "11"
@@ -19,7 +19,7 @@ concurrency:

 jobs:
  validate-all-ghas:
-    runs-on: ubuntu-26.04 # Don't switch to ubuntu-slim as zizmore-action requires Docker
+    runs-on: ubuntu-26.04
    permissions:
      contents: read
      # Required for the zizmor action to upload its SARIF results to
@@ -34,7 +34,7 @@ jobs:
      - name: Set up Node.js
        uses: actions/setup-node@820762786026740c76f36085b0efc47a31fe5020 # v7.0.0
        with:
-          node-version-file: "./superset-frontend/.nvmrc"
+          node-version: "20"

      - name: Install Dependencies
        # Versions are pinned to avoid ad-hoc, unpinned package installs.
@@ -45,8 +45,5 @@ jobs:
      - name: Run Script
        run: bash .github/workflows/github-action-validator.sh

-      - name: Test docs-deploy freshness gate
-        run: bash .github/workflows/scripts/check-docs-deploy-freshness.test.sh
-
      - name: Check for security issues on GHA workflows
        uses: zizmorcore/zizmor-action@3dc1ecc9bcb9e94e9b2c709687979e1298497054 # v0.6.2
@@ -26,7 +26,7 @@ jobs:
  cancel-on-hold:
    name: Cancel CI runs when hold label applied
    if: github.event.action == 'labeled' && startsWith(github.event.label.name, 'hold')
-    runs-on: ubuntu-slim
+    runs-on: ubuntu-26.04
    permissions:
      actions: write
      pull-requests: read
@@ -69,7 +69,7 @@ jobs:
  rerun-on-unhold:
    name: Re-run CI when hold label removed
    if: github.event.action == 'unlabeled' && startsWith(github.event.label.name, 'hold')
-    runs-on: ubuntu-slim
+    runs-on: ubuntu-24.04
    permissions:
      actions: write
      pull-requests: read
@@ -7,9 +7,6 @@ on:
  pull_request:
    types: [opened, edited]

-permissions:
-  contents: read
-
 jobs:
  superbot-orglabel:
    runs-on: ubuntu-slim
@@ -7,9 +7,6 @@ concurrency:
  group: ${{ github.workflow }}-${{ github.event.pull_request.number || github.run_id }}
  cancel-in-progress: true

-permissions:
-  contents: read
-
 jobs:
  labeler:
    permissions:
@@ -0,0 +1,39 @@
+name: Tags
+on:
+  release:
+    types: [published] # This makes it run only when a new released is published
+
+jobs:
+  latest-release:
+    name: Add/update tag to new release
+    runs-on: ubuntu-slim
+    permissions:
+      contents: write
+
+    steps:
+      - name: "Checkout ${{ github.ref }} ( ${{ github.sha }} )"
+        uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+        with:
+          persist-credentials: false
+          submodules: recursive
+
+      - name: Check for latest tag
+        id: latest-tag
+        env:
+          RELEASE_TAG_NAME: ${{ github.event.release.tag_name }}
+        run: |
+          source ./scripts/tag_latest_release.sh "$RELEASE_TAG_NAME" --dry-run
+
+      - name: Configure Git
+        run: |
+          git config user.name "$GITHUB_ACTOR"
+          git config user.email "$GITHUB_ACTOR@users.noreply.github.com"
+
+      - name: Run latest-tag
+        uses: ./.github/actions/latest-tag
+        if: steps.latest-tag.outputs.SKIP_TAG != 'true'
+        with:
+          description: Superset latest release
+          tag-name: latest
+        env:
+          GITHUB_TOKEN: ${{ github.token }}
@@ -23,7 +23,7 @@ jobs:
          persist-credentials: false
          submodules: recursive
      - name: Setup Java
-        uses: actions/setup-java@dd06d9cba3e5552c54d9f8ea23572deb30010f7c # v6.0.0
+        uses: actions/setup-java@b6effb05e454b25005698d916606bdc6ffcbf961 # v5.7.0
        with:
          distribution: "temurin"
          java-version: "11"
@@ -93,7 +93,7 @@ jobs:
          password: ${{ secrets.GITHUB_TOKEN }}

      - name: Set up Docker Buildx
-        uses: docker/setup-buildx-action@37fe631027851001ddb9b187196cc803df7f5f0e # v4.3.0
+        uses: docker/setup-buildx-action@bb05f3f5519dd87d3ba754cc423b652a5edd6d2c # v4.2.0

      - name: Copy image to GHCR
        env:
@@ -19,9 +19,6 @@ concurrency:
  group: ${{ github.workflow }}-${{ github.event.pull_request.number || github.run_id }}
  cancel-in-progress: false

-permissions:
-  contents: read
-
 jobs:
  lint-check:
    runs-on: ubuntu-slim
@@ -202,7 +202,7 @@ jobs:
  actions-timeline:
    needs: pre-commit
    if: always()
-    runs-on: ubuntu-slim
+    runs-on: ubuntu-26.04
    steps:
      - uses: Kesin11/actions-timeline@57fc93f20c6da7fbc14063c6d24a2a5627c799ad # v3.2.0
        with:
@@ -1,49 +0,0 @@
-#!/bin/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 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
-#
-#    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 specific language governing permissions and
-# limitations under the License.
-#
-# Shared freshness gate used by the Docs Deployment workflow
-# (superset-docs-deploy.yml) both up front (check-freshness) and again right
-# before the deploy step (recheck-freshness). Writes an output declaring
-# whether BUILD_SHA is still master's current tip, so a superseded run can
-# skip cleanly instead of racing (and clobbering, or being force-cancelled
-# by) a fresher run.
-#
-# Required env vars:
-#   BUILD_SHA     - the commit SHA this run is building
-#   REPO          - "owner/repo" to query, e.g. github.repository
-#   OUTPUT_NAME   - the GITHUB_OUTPUT key to write, e.g. "is-current"
-#   GITHUB_OUTPUT - path to append outputs to (set by the Actions runner)
-# Optional env vars:
-#   EVENT_NAME    - if "workflow_dispatch", bypasses the check and always
-#                   reports current, since a manual dispatch is a deliberate,
-#                   one-off action rather than something racing other triggers
-#   GH_TOKEN      - passed through to `gh`, needed to call the GitHub API
-
-set -euo pipefail
-
-if [ "${EVENT_NAME:-}" = "workflow_dispatch" ]; then
-  echo "${OUTPUT_NAME}=true" >>"$GITHUB_OUTPUT"
-  exit 0
-fi
-
-latest_sha="$(gh api "repos/${REPO}/commits/master" --jq .sha)"
-if [ "${latest_sha}" = "${BUILD_SHA}" ]; then
-  echo "${OUTPUT_NAME}=true" >>"$GITHUB_OUTPUT"
-else
-  echo "${OUTPUT_NAME}=false" >>"$GITHUB_OUTPUT"
-  echo "::notice::master has moved on to ${latest_sha} since ${BUILD_SHA} was triggered — skipping this stale run."
-fi
@@ -1,100 +0,0 @@
-#!/bin/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 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
-#
-#    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 specific language governing permissions and
-# limitations under the License.
-#
-# Exercises check-docs-deploy-freshness.sh against a stubbed `gh`, covering
-# the dispatch-bypass, current-tip and stale-tip branches so the output
-# contract (is-current / still-current) can't silently regress. Run
-# directly, no extra tooling required:
-#   bash .github/workflows/scripts/check-docs-deploy-freshness.test.sh
-
-set -euo pipefail
-
-script_dir="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
-script_under_test="${script_dir}/check-docs-deploy-freshness.sh"
-
-failures=0
-
-# Runs the script under test with a stubbed `gh` reporting $1 as master's
-# latest sha, asserting that GITHUB_OUTPUT ends up containing exactly $4.
-run_case() {
-  local case_name="$1"
-  local latest_sha="$2"
-  local build_sha="$3"
-  local event_name="$4"
-  local expected_line="$5"
-
-  local workdir
-  workdir="$(mktemp -d)"
-  trap 'rm -rf "${workdir}"' RETURN
-
-  # Fake `gh` that just echoes back the requested "latest" sha regardless of
-  # arguments, so the script under test never touches the network.
-  cat >"${workdir}/gh" <<EOF
-#!/bin/bash
-echo '${latest_sha}'
-EOF
-  chmod +x "${workdir}/gh"
-
-  local output_file="${workdir}/github_output"
-  : >"${output_file}"
-
-  if PATH="${workdir}:${PATH}" \
-    GITHUB_OUTPUT="${output_file}" \
-    OUTPUT_NAME="is-current" \
-    REPO="apache/superset" \
-    BUILD_SHA="${build_sha}" \
-    EVENT_NAME="${event_name}" \
-    GH_TOKEN="fake-token" \
-    bash "${script_under_test}"; then
-    :
-  else
-    echo "FAIL (${case_name}): script exited non-zero"
-    failures=$((failures + 1))
-    return
-  fi
-
-  local actual
-  actual="$(cat "${output_file}")"
-  if [ "${actual}" = "${expected_line}" ]; then
-    echo "PASS (${case_name})"
-  else
-    echo "FAIL (${case_name}): expected '${expected_line}', got '${actual}'"
-    failures=$((failures + 1))
-  fi
-}
-
-# `gh` prints "should-not-be-called" for the dispatch case above the trick:
-# it's never actually invoked since the bypass short-circuits before the
-# `gh api` call, but the fake still needs a body.
-run_case "workflow_dispatch bypasses the check" \
-  "unused" "abc123" "workflow_dispatch" \
-  "is-current=true"
-
-run_case "build sha matches master's tip" \
-  "abc123" "abc123" "push" \
-  "is-current=true"
-
-run_case "build sha is stale" \
-  "def456" "abc123" "push" \
-  "is-current=false"
-
-if [ "${failures}" -gt 0 ]; then
-  echo "${failures} case(s) failed"
-  exit 1
-fi
-
-echo "All cases passed"
@@ -17,9 +17,6 @@ env:
  GITHUB_ORG: ${{ github.repository_owner }}
  GITHUB_REPO: ${{ github.event.repository.name }}

-permissions:
-  contents: read
-
 jobs:
  cleanup-expired:
    name: Clean up expired showtime environments
@@ -26,9 +26,6 @@ env:
  GITHUB_REPO: ${{ github.event.repository.name }}
  GITHUB_ACTOR: ${{ github.actor }}

-permissions:
-  contents: read
-
 jobs:
  sync:
    name: 🎪 Sync PR to desired state
@@ -18,6 +18,16 @@ on:

  workflow_dispatch: {}

+# Serialize deploys: the action pushes to apache/superset-site without
+# rebasing, so concurrent runs race on the final push and the loser fails
+# with `! [rejected] asf-site -> asf-site (fetch first)`. Cancel any
+# in-progress run as soon as a newer one starts — the destination repo
+# isn't touched until the final push step, so canceling mid-build is safe,
+# and the freshest content always wins.
+concurrency:
+  group: docs-deploy-asf-site
+  cancel-in-progress: true
+
 permissions:
  contents: read
  actions: read
@@ -38,69 +48,17 @@ jobs:

        env:
          SUPERSET_SITE_BUILD: ${{ (secrets.SUPERSET_SITE_BUILD != '' && secrets.SUPERSET_SITE_BUILD != '') || '' }}
-
-  # Master gets frequent, sometimes bursty pushes, and each one can trigger a
-  # deploy attempt. Rather than let every superseded attempt get force-killed
-  # by the build-deploy concurrency group below (which shows up as a
-  # `cancelled` — i.e. red/failing-looking — check on that commit), have each
-  # run check up front whether it's still building master's current tip and,
-  # if not, skip cleanly. Deliberately outside the docs-deploy-asf-site
-  # concurrency group so it runs immediately for every trigger without
-  # blocking or being blocked by anything.
-  check-freshness:
-    runs-on: ubuntu-26.04
-    outputs:
-      is-current: ${{ steps.check.outputs.is-current }}
-    steps:
-      # Sparse checkout: this job's only job is to be fast, so it fetches
-      # nothing but the freshness-check script itself.
-      - name: Checkout freshness-check script
-        uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
-        with:
-          persist-credentials: false
-          sparse-checkout: |
-            .github/workflows/scripts
-          sparse-checkout-cone-mode: false
-      - name: "Check whether this is still master's current commit"
-        id: check
-        env:
-          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-          BUILD_SHA: ${{ github.event.workflow_run.head_sha || github.sha }}
-          EVENT_NAME: ${{ github.event_name }}
-          REPO: ${{ github.repository }}
-          OUTPUT_NAME: is-current
-        run: .github/workflows/scripts/check-docs-deploy-freshness.sh
-
  build-deploy:
-    needs: [config, check-freshness]
-    # Only the run for master's current tip proceeds; anything superseded
-    # already skipped at check-freshness above instead of landing here.
+    needs: config
    # For workflow_run triggers, only deploy when the triggering run originated
    # from this repository (not a fork), ensuring the checked-out code and any
    # local actions executed with deploy credentials are trusted.
    if: >-
      needs.config.outputs.has-secrets &&
-      needs.check-freshness.outputs.is-current == 'true' &&
      (github.event_name != 'workflow_run' ||
       github.event.workflow_run.head_repository.full_name == github.repository)
    name: Build & Deploy
    runs-on: ubuntu-26.04
-    # Serialize deploys: the action pushes to apache/superset-site without
-    # rebasing, so concurrent runs race on the final push and the loser fails
-    # with `! [rejected] asf-site -> asf-site (fetch first)`. Queue instead of
-    # canceling: a run that already passed check-freshness can still be
-    # sitting in the queue for a runner when a newer run starts and finishes
-    # first. cancel-in-progress would let that stale, queued run kill the
-    # newer run's in-progress deploy the moment it's finally scheduled, and
-    # then skip itself at the re-check below — losing the deploy entirely.
-    # Queuing means the stale run just waits its turn and then no-ops at the
-    # re-check, so the fresher content that already deployed is never
-    # clobbered or lost. The check-freshness gate above means it should be
-    # rare for more than one run to reach this point, so the queue stays
-    # short in practice.
-    concurrency:
-      group: docs-deploy-asf-site
-      cancel-in-progress: false
    steps:
      - uses: Kesin11/actions-timeline@57fc93f20c6da7fbc14063c6d24a2a5627c799ad # v3.2.0
        with:
@@ -118,7 +76,7 @@ jobs:
          node-version-file: "./docs/.nvmrc"
      - name: Setup Python
        uses: ./.github/actions/setup-backend/
-      - uses: actions/setup-java@dd06d9cba3e5552c54d9f8ea23572deb30010f7c # v6.0.0
+      - uses: actions/setup-java@b6effb05e454b25005698d916606bdc6ffcbf961 # v5.7.0
        with:
          distribution: "zulu"
          java-version: "21"
@@ -141,7 +99,7 @@ jobs:
          yarn install --check-cache
      - name: Download database diagnostics (if triggered by integration tests)
        if: github.event_name == 'workflow_run' && github.event.workflow_run.conclusion == 'success'
-        uses: dawidd6/action-download-artifact@d63b86af1b34672e53c440b1b83979861906bad7 # v24
+        uses: dawidd6/action-download-artifact@b6e2e70617bc3265edd6dab6c906732b2f1ae151 # v21
        continue-on-error: true
        with:
          workflow: superset-python-integrationtest.yml
@@ -150,7 +108,7 @@ jobs:
          path: docs/src/data/
      - name: Try to download latest diagnostics (for push/dispatch triggers)
        if: github.event_name != 'workflow_run'
-        uses: dawidd6/action-download-artifact@d63b86af1b34672e53c440b1b83979861906bad7 # v24
+        uses: dawidd6/action-download-artifact@b6e2e70617bc3265edd6dab6c906732b2f1ae151 # v21
        continue-on-error: true
        with:
          workflow: superset-python-integrationtest.yml
@@ -172,24 +130,7 @@ jobs:
        working-directory: docs
        run: |
          yarn build
-      # The check-freshness job above narrows the window but doesn't close it: an
-      # older run can observe is-current=true, then sit through this build while a
-      # newer run's own freshness check also passes and it deploys and finishes
-      # first. If this (stale) run then wins entry into the concurrency group, it
-      # would overwrite the newer content that already deployed. Re-check right
-      # before the one step that actually mutates superset-site, so a stale run
-      # skips deploying instead of clobbering a fresher one that already ran.
-      - name: "Re-check freshness immediately before deploying"
-        id: recheck-freshness
-        if: github.event_name != 'workflow_dispatch'
-        env:
-          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-          BUILD_SHA: ${{ github.event.workflow_run.head_sha || github.sha }}
-          REPO: ${{ github.repository }}
-          OUTPUT_NAME: still-current
-        run: .github/workflows/scripts/check-docs-deploy-freshness.sh
      - name: deploy docs
-        if: github.event_name == 'workflow_dispatch' || steps.recheck-freshness.outputs.still-current == 'true'
        uses: ./.github/actions/github-action-push-to-another-repository
        env:
          API_TOKEN_GITHUB: ${{ secrets.SUPERSET_SITE_BUILD }}
@@ -140,7 +140,7 @@ jobs:
        run: |
          yarn install --check-cache
      - name: Download database diagnostics from integration tests
-        uses: dawidd6/action-download-artifact@d63b86af1b34672e53c440b1b83979861906bad7 # v24
+        uses: dawidd6/action-download-artifact@b6e2e70617bc3265edd6dab6c906732b2f1ae151 # v21
        with:
          workflow: superset-python-integrationtest.yml
          run_id: ${{ github.event.workflow_run.id }}
@@ -26,9 +26,6 @@ concurrency:
  group: ${{ github.workflow }}-${{ github.event.pull_request.number || github.run_id }}
  cancel-in-progress: true

-permissions:
-  contents: read
-
 jobs:
  changes:
    runs-on: ubuntu-26.04
@@ -78,14 +75,14 @@ jobs:
      USE_DASHBOARD: ${{ github.event.inputs.use_dashboard == 'true' || 'false' }}
    services:
      postgres:
-        image: ghcr.io/apache/superset/ci/postgres:17-alpine
+        image: postgres:17-alpine
        env:
          POSTGRES_USER: superset
          POSTGRES_PASSWORD: superset
        ports:
          - 15432:5432
      redis:
-        image: ghcr.io/apache/superset/ci/redis:7-alpine
+        image: redis:7-alpine
        ports:
          - 16379:6379
    steps:
@@ -186,14 +183,14 @@ jobs:
      GITHUB_TOKEN: ${{ github.token }}
    services:
      postgres:
-        image: ghcr.io/apache/superset/ci/postgres:17-alpine
+        image: postgres:17-alpine
        env:
          POSTGRES_USER: superset
          POSTGRES_PASSWORD: superset
        ports:
          - 15432:5432
      redis:
-        image: ghcr.io/apache/superset/ci/redis:7-alpine
+        image: redis:7-alpine
        ports:
          - 16379:6379
    steps:
@@ -354,7 +351,7 @@ jobs:
  actions-timeline:
    needs: [cypress-matrix, playwright-tests, cypress-matrix-required, playwright-tests-required]
    if: always()
-    runs-on: ubuntu-slim
+    runs-on: ubuntu-26.04
    permissions:
      actions: read
    steps:
@@ -74,7 +74,7 @@ jobs:
  actions-timeline:
    needs: test-superset-extensions-cli-package
    if: always()
-    runs-on: ubuntu-slim
+    runs-on: ubuntu-26.04
    steps:
      - uses: Kesin11/actions-timeline@57fc93f20c6da7fbc14063c6d24a2a5627c799ad # v3.2.0
        with:
@@ -97,7 +97,6 @@ jobs:
          mkdir -p ${{ github.workspace }}/superset-frontend/coverage
          docker run \
          -v ${{ github.workspace }}/superset-frontend/coverage:/app/superset-frontend/coverage \
-          -e CI=true \
          --rm $TAG \
          bash -c \
          "npm run test -- --coverage --shard=${{ matrix.shard }}/8 --coverageReporters=json"
@@ -111,7 +110,7 @@ jobs:
  report-coverage:
    needs: [sharded-jest-tests]
    if: needs.frontend-build.outputs.should-run == 'true'
-    runs-on: ubuntu-slim
+    runs-on: ubuntu-26.04
    timeout-minutes: 15
    permissions:
      id-token: write
@@ -206,107 +205,10 @@ jobs:
  actions-timeline:
    needs: [report-coverage, lint-frontend, validate-frontend, test-storybook]
    if: always()
-    runs-on: ubuntu-slim
+    runs-on: ubuntu-26.04
    permissions:
      actions: read
    steps:
      - uses: Kesin11/actions-timeline@57fc93f20c6da7fbc14063c6d24a2a5627c799ad # v3.2.0
        with:
          expand-composite-actions: true
-
-  # Compares a PR's own bundle size against the last nightly-recorded
-  # baseline (see frontend-bundle-size-nightly.yml, which owns actually
-  # persisting new baselines). PR-only: a push to master doesn't need this
-  # check re-run against itself, and re-persisting the baseline on every
-  # push to master -- which happens many times a day -- would burn a full
-  # production build for no benefit nightly refresh doesn't already cover.
-  bundle-size:
-    needs: frontend-build
-    if: needs.frontend-build.outputs.should-run == 'true' && github.event_name == 'pull_request'
-    runs-on: ubuntu-26.04
-    timeout-minutes: 15
-    permissions:
-      contents: read
-      pull-requests: write
-    steps:
-      - name: Checkout Code
-        uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
-        with:
-          persist-credentials: false
-          ref: ${{ github.event_name == 'pull_request' && github.event.pull_request.head.sha || github.sha }}
-
-      - name: Download Docker Image Artifact
-        uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8
-        with:
-          name: docker-image
-
-      - name: Load Docker Image
-        run: |
-          zstd -d < docker-image.tar.zst | docker load
-
-      # webpack's persistent filesystem cache (superset-frontend/webpack.config.js)
-      # turns a warm production build into ~20s instead of several minutes,
-      # but GH-hosted runners are fresh VMs with nothing carried over between
-      # jobs -- without restoring it explicitly, every single PR would pay
-      # the full cold-build cost. Keyed on the same files webpack's own
-      # `buildDependencies` invalidates on, so a stale cache is never used.
-      - name: Restore webpack build cache
-        uses: actions/cache@55cc8345863c7cc4c66a329aec7e433d2d1c52a9 # v6.1.0
-        with:
-          path: superset-frontend/.temp_cache
-          key: >-
-            webpack-prod-cache-${{ hashFiles('superset-frontend/package-lock.json',
-            'superset-frontend/babel.config.js', 'superset-frontend/tsconfig.json',
-            'superset-frontend/webpack.config.js') }}
-
-      # Only ever pull the last recorded data point off the cache, keyed by
-      # run ID -- `restore-keys` prefix-matches the most recently created
-      # entry, which is always the latest nightly run. Absent before the
-      # first nightly run ever happens; benchmark-action starts a fresh
-      # history in that case.
-      - name: Restore bundle size history
-        uses: actions/cache/restore@55cc8345863c7cc4c66a329aec7e433d2d1c52a9 # v6.1.0
-        with:
-          path: bundle-size-history.json
-          key: bundle-size-history-${{ github.run_id }}
-          restore-keys: |
-            bundle-size-history-
-
-      - name: Build production bundle with stats
-        run: |
-          mkdir -p ${{ github.workspace }}/superset-frontend/bundle-stats
-          mkdir -p ${{ github.workspace }}/superset-frontend/.temp_cache
-          docker run \
-          -v ${{ github.workspace }}/superset-frontend/bundle-stats:/app/superset-frontend/bundle-stats \
-          -v ${{ github.workspace }}/superset-frontend/.temp_cache:/app/superset-frontend/.temp_cache \
-          --rm $TAG \
-          bash -c \
-          "npm i && BUNDLE_SIZE_STATS=true npm run build -- --json=bundle-stats/stats.json"
-
-      - name: Summarize bundle size
-        run: |
-          node superset-frontend/scripts/bundle-size-summary.js \
-            superset-frontend/bundle-stats/stats.json > bundle-size-summary.json
-          rm -rf superset-frontend/bundle-stats
-
-      # Comparison + alert only -- this job never persists. See
-      # frontend-bundle-size-nightly.yml for why.
-      #
-      # comment-on-alert is gated to same-repo PRs: on a fork PR,
-      # GITHUB_TOKEN is forced read-only regardless of the `permissions`
-      # block above, so once the alert threshold is crossed the action's
-      # `pulls.createReview` call 403s. That error isn't gated by
-      # fail-on-alert (which only governs the deliberate alert-threshold
-      # failure) -- it propagates and fails the job outright. Fork PRs
-      # still get the comparison via the job summary (summary-always).
-      - name: Compare bundle size against nightly baseline
-        uses: benchmark-action/github-action-benchmark@52576c92bccf6ac60c8223ec7eb2565637cae9ba # v1.22.1
-        with:
-          tool: customSmallerIsBetter
-          output-file-path: bundle-size-summary.json
-          external-data-json-path: bundle-size-history.json
-          github-token: ${{ secrets.GITHUB_TOKEN }}
-          comment-on-alert: ${{ github.event.pull_request.head.repo.full_name == github.repository }}
-          alert-threshold: "110%"
-          fail-on-alert: false
-          summary-always: true
@@ -27,9 +27,6 @@ concurrency:
  group: helm-release
  cancel-in-progress: false

-permissions:
-  contents: read
-
 jobs:
  release:
    runs-on: ubuntu-26.04
@@ -22,9 +22,6 @@ concurrency:
  group: ${{ github.workflow }}-${{ github.event.pull_request.number || github.run_id }}
  cancel-in-progress: true

-permissions:
-  contents: read
-
 jobs:
  changes:
    runs-on: ubuntu-26.04
@@ -188,7 +185,7 @@ jobs:
  actions-timeline:
    needs: playwright-tests-experimental
    if: always()
-    runs-on: ubuntu-slim
+    runs-on: ubuntu-26.04
    permissions:
      actions: read
    steps:
@@ -53,7 +53,9 @@ jobs:
        mysql+mysqldb://superset:superset@127.0.0.1:13306/superset?charset=utf8mb4&binary_prefix=true
    services:
      mysql:
-        image: ghcr.io/apache/superset/ci/mysql:8.0
+        image: mysql:8.0
+        # Authenticated pulls use our higher Docker Hub rate limit. Empty on
+        # fork PRs (secrets unavailable) -> runner falls back to anonymous.
        env:
          MYSQL_ROOT_PASSWORD: root
        ports:
@@ -64,7 +66,7 @@ jobs:
          --health-timeout=5s
          --health-retries=5
      redis:
-        image: ghcr.io/apache/superset/ci/redis:7-alpine
+        image: redis:7-alpine
        options: --entrypoint redis-server
        ports:
          - 16379:6379
@@ -141,7 +143,7 @@ jobs:
      SUPERSET__SQLALCHEMY_DATABASE_URI: postgresql+psycopg2://superset:superset@127.0.0.1:15432/superset
    services:
      postgres:
-        image: ghcr.io/apache/superset/ci/postgres:17-alpine
+        image: postgres:17-alpine
        env:
          POSTGRES_USER: superset
          POSTGRES_PASSWORD: superset
@@ -150,7 +152,7 @@ jobs:
          # GitHub action runner's default installations
          - 15432:5432
      redis:
-        image: ghcr.io/apache/superset/ci/redis:7-alpine
+        image: redis:7-alpine
        ports:
          - 16379:6379
    steps:
@@ -200,7 +202,7 @@ jobs:
        sqlite:///${{ github.workspace }}/.temp/examples.db?check_same_thread=true
    services:
      redis:
-        image: ghcr.io/apache/superset/ci/redis:7-alpine
+        image: redis:7-alpine
        ports:
          - 16379:6379
    steps:
@@ -257,7 +259,7 @@ jobs:
  actions-timeline:
    needs: [test-mysql, test-postgres, test-sqlite, test-postgres-required]
    if: always()
-    runs-on: ubuntu-slim
+    runs-on: ubuntu-26.04
    permissions:
      actions: read
    steps:
@@ -14,9 +14,6 @@ concurrency:
  group: ${{ github.workflow }}-${{ github.event.pull_request.number || github.run_id }}
  cancel-in-progress: true

-permissions:
-  contents: read
-
 jobs:
  changes:
    runs-on: ubuntu-26.04
@@ -52,7 +49,7 @@ jobs:
      SUPERSET__SQLALCHEMY_EXAMPLES_URI: presto://localhost:15433/memory/default
    services:
      postgres:
-        image: ghcr.io/apache/superset/ci/postgres:17-alpine
+        image: postgres:17-alpine
        env:
          POSTGRES_USER: superset
          POSTGRES_PASSWORD: superset
@@ -61,7 +58,7 @@ jobs:
          # GitHub action runner's default installations
          - 15432:5432
      presto:
-        image: ghcr.io/apache/superset/ci/presto:350-e.6
+        image: starburstdata/presto:350-e.6
        env:
          POSTGRES_USER: superset
          POSTGRES_PASSWORD: superset
@@ -70,7 +67,7 @@ jobs:
          # GitHub action runner's default installations
          - 15433:8080
      redis:
-        image: ghcr.io/apache/superset/ci/redis:7-alpine
+        image: redis:7-alpine
        ports:
          - 16379:6379
    steps:
@@ -116,7 +113,7 @@ jobs:
      UPLOAD_FOLDER: /tmp/.superset/uploads/
    services:
      postgres:
-        image: ghcr.io/apache/superset/ci/postgres:17-alpine
+        image: postgres:17-alpine
        env:
          POSTGRES_USER: superset
          POSTGRES_PASSWORD: superset
@@ -125,7 +122,7 @@ jobs:
          # GitHub action runner's default installations
          - 15432:5432
      redis:
-        image: ghcr.io/apache/superset/ci/redis:7-alpine
+        image: redis:7-alpine
        ports:
          - 16379:6379
    steps:
@@ -165,7 +162,7 @@ jobs:
  actions-timeline:
    needs: [test-postgres-presto, test-postgres-hive]
    if: always()
-    runs-on: ubuntu-slim
+    runs-on: ubuntu-26.04
    permissions:
      actions: read
    steps:
@@ -53,6 +53,12 @@ jobs:
        python-version: ${{ github.event_name == 'pull_request' && fromJSON('["current"]') || fromJSON('["current", "next"]') }}
    env:
      PYTHONPATH: ${{ github.workspace }}
+      # Promotes the SQLAlchemy 2.0 deprecation warnings already locked in as
+      # errors via pytest.ini's `filterwarnings` to actually run in CI, so a
+      # regression on those fails the build instead of relying on a
+      # contributor remembering to set this locally. See the migration
+      # battleplan: https://github.com/apache/superset/discussions/40273
+      SQLALCHEMY_WARN_20: "1"
    steps:
      - name: "Checkout ${{ github.ref }} ( ${{ github.sha }} )"
        uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
@@ -69,18 +75,13 @@ jobs:
          SUPERSET_SECRET_KEY: not-a-secret
        run: |
          pytest --durations-min=0.5 --cov-report= --cov=superset ./tests/common ./tests/unit_tests --cache-clear --maxfail=50 --junit-xml=test-results/junit-unit.xml
-      # COVERAGE_FILE keeps these scoped gates off the default .coverage that
-      # the step above wrote. pytest-cov starts a fresh data file per run, so
-      # without it the last gate replaces the full-suite data and the report
-      # uploaded below contains only that gate's subtree -- every other file
-      # then reads as uncovered, and patch coverage on an unrelated PR is 0%.
      - name: Python 100% coverage unit tests
        env:
          SUPERSET_TESTENV: true
          SUPERSET_SECRET_KEY: not-a-secret
        run: |
-          COVERAGE_FILE="${RUNNER_TEMP}/.coverage.sql" pytest --durations-min=0.5 --cov=superset/sql/ ./tests/unit_tests/sql/ --cache-clear --cov-fail-under=100 --junit-xml=test-results/junit-sql-coverage.xml
-          COVERAGE_FILE="${RUNNER_TEMP}/.coverage.semantic_layers" pytest --durations-min=0.5 --cov=superset/semantic_layers/ ./tests/unit_tests/semantic_layers/ --cache-clear --cov-fail-under=100 --junit-xml=test-results/junit-semantic-layers-coverage.xml
+          pytest --durations-min=0.5 --cov=superset/sql/ ./tests/unit_tests/sql/ --cache-clear --cov-fail-under=100 --junit-xml=test-results/junit-sql-coverage.xml
+          pytest --durations-min=0.5 --cov=superset/semantic_layers/ ./tests/unit_tests/semantic_layers/ --cache-clear --cov-fail-under=100 --junit-xml=test-results/junit-semantic-layers-coverage.xml
      - name: Upload code coverage
        uses: codecov/codecov-action@fb8b3582c8e4def4969c97caa2f19720cb33a72f # v7.0.0
        with:
@@ -125,7 +126,7 @@ jobs:
  unit-tests-required:
    needs: [changes, unit-tests]
    if: always()
-    runs-on: ubuntu-slim
+    runs-on: ubuntu-26.04
    timeout-minutes: 5
    permissions:
      contents: read
@@ -20,7 +20,7 @@ permissions:

 jobs:
  post-comment:
-    runs-on: ubuntu-slim
+    runs-on: ubuntu-26.04
    # Only act when the Translations workflow failed (which means a regression
    # was detected — the workflow exits 1 on regression).
    if: github.event.workflow_run.conclusion == 'failure'
@@ -160,7 +160,7 @@ jobs:
  actions-timeline:
    needs: [frontend-check-translations, babel-extract]
    if: always()
-    runs-on: ubuntu-slim
+    runs-on: ubuntu-26.04
    permissions:
      actions: read
    steps:
@@ -35,10 +35,10 @@ jobs:
      - name: Install dependencies
        working-directory: ./superset-websocket
        run: npm ci
-      - name: lint
+      - name: eslint
        working-directory: ./superset-websocket
-        run: npm run lint-check
-      - name: typescript check
+        run: npm run eslint -- . --quiet
+      - name: typescript checks
        working-directory: ./superset-websocket
        run: npm run type
      - name: code format check
@@ -13,9 +13,6 @@ on:
        required: true
        type: string

-permissions:
-  contents: read
-
 jobs:
  supersetbot:
    runs-on: ubuntu-26.04
@@ -5,9 +5,6 @@ on:
  pull_request_target:
    types: [opened]

-permissions:
-  contents: read
-
 jobs:
  welcome:
    runs-on: ubuntu-slim
@@ -15,12 +15,18 @@
 # limitations under the License.
 #

+[submodule ".github/actions/latest-tag"]
+	path = .github/actions/latest-tag
+	url = https://github.com/EndBug/latest-tag
 [submodule ".github/actions/pr-lint-action"]
 	path = .github/actions/pr-lint-action
 	url = https://github.com/morrisoncole/pr-lint-action
 [submodule ".github/actions/cached-dependencies"]
 	path = .github/actions/cached-dependencies
 	url = https://github.com/apache-superset/cached-dependencies
+[submodule ".github/actions/comment-on-pr"]
+	path = .github/actions/comment-on-pr
+	url = https://github.com/unsplash/comment-on-pr
 [submodule ".github/actions/chart-testing-action"]
 	path = .github/actions/chart-testing-action
 	url = https://github.com/helm/chart-testing-action
@@ -64,19 +64,10 @@ repos:
    hooks:
      - id: oxfmt-frontend
        name: oxfmt (frontend)
-        entry: ./scripts/oxfmt.sh superset-frontend
+        entry: bash -c 'cd superset-frontend && files=(); for f in "$@"; do files+=("${f#superset-frontend/}"); done; npx oxfmt --write --no-error-on-unmatched-pattern -- "${files[@]}"' --
        language: system
        pass_filenames: true
        files: ^superset-frontend/.*\.(js|jsx|ts|tsx|css|scss|sass|json)$
-      - id: oxfmt-websocket
-        name: oxfmt (websocket)
-        entry: ./scripts/oxfmt.sh superset-websocket
-        language: system
-        pass_filenames: true
-        # JSON is excluded: superset-websocket/.oxfmtrc.json ignores *.json, so
-        # passing them here would only ever be a no-op (notably for the tracked
-        # package-lock.json).
-        files: ^superset-websocket/.*\.(js|ts)$
  - repo: local
    hooks:
      - id: oxlint-frontend
@@ -97,9 +88,9 @@ repos:
        language: system
        pass_filenames: true
        files: ^superset-frontend/.*\.(js|jsx|ts|tsx)$
-      - id: oxlint-docs
-        name: oxlint (docs)
-        entry: bash -c 'cd docs && FILES=$(printf "%s\n" "$@" | sed "s|^docs/||" | tr "\n" " ") && yarn lint --fix --quiet $FILES'
+      - id: eslint-docs
+        name: eslint (docs)
+        entry: bash -c 'cd docs && FILES=$(printf "%s\n" "$@" | sed "s|^docs/||" | tr "\n" " ") && yarn eslint --fix --quiet $FILES'
        language: system
        pass_filenames: true
        files: ^docs/.*\.(js|jsx|ts|tsx)$
@@ -10,7 +10,6 @@
 .stylelintignore
 .flake8
 .nvmrc
-.npmrc
 .rat-excludes
 .swcrc
 .*log
@@ -167,7 +167,7 @@ The Developer Portal auto-generates MDX documentation from Storybook stories. **
 ### Generator Location
 - Script: `docs/scripts/generate-superset-components.mjs`
 - Wrapper: `docs/src/components/StorybookWrapper.jsx`
- Output: `docs/developer_docs/components/`
+- Output: `docs/developer_portal/components/`

 ## Architecture Patterns

@@ -35,4 +35,4 @@ The Developer Portal includes comprehensive guides for:
 - [Code Review Process](https://superset.apache.org/developer_portal/contributing/code-review)
 - [Development How-tos](https://superset.apache.org/developer_portal/contributing/howtos)

-Source for the Developer Portal documentation is [located here](https://github.com/apache/superset/tree/master/docs/developer_docs).
+Source for the Developer Portal documentation is [located here](https://github.com/apache/superset/tree/master/docs/developer_portal).
@@ -104,30 +104,6 @@ RUN if [ "${BUILD_TRANSLATIONS}" = "true" ]; then \
    rm -rf /app/superset/translations/*/*/*.[po,mo];


-######################################################################
-# superset-websocket builds the realtime WebSocket (Node) server that
-# ships in the official image, launched via docker/entrypoints/run-websocket.sh
-######################################################################
-FROM node:24-trixie-slim AS superset-websocket
-
-# Harden `npm ci` against transient npm-registry network blips (e.g. ECONNRESET).
-ENV npm_config_fetch_retries=5 \
-    npm_config_fetch_retry_mintimeout=20000 \
-    npm_config_fetch_retry_maxtimeout=120000 \
-    npm_config_fetch_timeout=600000
-
-WORKDIR /app/superset-websocket
-
-# Install against the lockfile first (cached until it changes), then bundle the
-# TypeScript server into a single self-contained CJS file (esbuild inlines every
-# dependency), so the runtime image needs only the Node binary and dist/ — no
-# node_modules to ship.
-COPY superset-websocket/package.json superset-websocket/package-lock.json ./
-RUN --mount=type=cache,target=/root/.npm npm ci
-COPY superset-websocket/ ./
-RUN npm run build
-
-
 ######################################################################
 # Base python layer
 ######################################################################
@@ -245,19 +221,6 @@ RUN rm superset/translations/*/*/*.po
 COPY --from=superset-node /app/superset/translations superset/translations
 COPY --from=python-translation-compiler /app/translations_mo superset/translations

-# --- Realtime WebSocket server (part of the official image) ---------------
-# The realtime transport (superset-websocket) is a Node service, bundled by
-# esbuild into a single self-contained file. Copy the Node runtime plus that
-# bundle so every image built from this stage can launch it via an alternate
-# entrypoint (docker/entrypoints/run-websocket.sh) rather than needing a separate
-# image. This lives here rather than in a single downstream stage so the lean and
-# dev images both ship it — docker-compose-non-dev.yml runs the websocket service
-# from the dev target.
-RUN /app/docker/apt-install.sh libstdc++6
-COPY --from=superset-websocket /usr/local/bin/node /usr/local/bin/node
-COPY --from=superset-websocket --chown=superset:superset \
-    /app/superset-websocket/dist /app/superset-websocket/dist
-
 HEALTHCHECK CMD /app/docker/docker-healthcheck.sh
 CMD ["/app/docker/entrypoints/run-server.sh"]
 EXPOSE ${SUPERSET_PORT}
@@ -31,8 +31,6 @@ under the License.
 [![Open PRs](https://img.shields.io/github/issues-pr/apache/superset)](https://github.com/apache/superset/pulls)
 [![Get on Slack](https://img.shields.io/badge/slack-join-orange.svg)](https://bit.ly/join-superset-slack)
 [![Documentation](https://img.shields.io/badge/docs-apache.org-blue.svg)](https://superset.apache.org)
-[![Storybook](https://img.shields.io/badge/storybook-live-ff4785.svg)](https://superset-storybook.netlify.app)
-[![Bundle Analyzer](https://img.shields.io/badge/bundle%20analyzer-nightly-8dd6f9.svg)](https://superset-bundle-analyzer.netlify.app)

 <picture width="500">
  <source
@@ -441,11 +441,6 @@ categories:
      url: https://bestpair.info/
      contributors: ["@stevensuting"]

-    - name: Veremes
-      url: https://www.veremes.com/
-      logo: veremes.svg
-      contributors: ["@verdier"]
-
    - name: Virtuoso QA
      url: https://www.virtuosoqa.com

@@ -84,16 +84,6 @@ The `sql_lab` role is *additive*: it grants the SQL Lab permission set on top of

 Deployments may grant or revoke individual view-menu permissions, which shifts the boundary for that deployment but does not redefine the model. Any custom role created by an operator inherits the same principle: its capabilities are whatever the operator has explicitly granted it. The Public principal follows the same rule: operators may grant the Public role read access to specific datasets or dashboards (typically for anonymous reporting use cases), which shifts the boundary for that deployment without redefining the model.

-### Async Execution and Realtime Notifications
-
-Asynchronous execution paths do not create a separate data-access capability. A background task is a continuation of an already-authorized action, such as reading chart data or executing SQL through SQL Lab. The initiating route, command, or scheduler must enforce the same route-level and object-level checks the synchronous path would enforce before it creates the task, and the worker must execute under the initiating principal's effective identity when row-level security, impersonation, embedded guest-token scope, or similar controls affect the result.
-
-Task metadata is itself a request-scoped resource. Non-admin users and embedded guests may read or cancel only tasks they are subscribed to or that otherwise represent work they are entitled to observe; Admin may observe and manage tasks as part of the trusted operational boundary. A bug that lets a principal create, read, join, cancel, or receive task state for work outside the role and capability matrix is in scope.
-
-Realtime transports, including WebSocket delivery backed by Redis or Valkey Pub/Sub, are notification mechanisms rather than authorization sources. WebSocket notification access is controlled by `can_read` on the `Realtime` resource. The broadcast scope is authenticated-global, not public: it reaches every authenticated realtime socket, and an anonymous request receives no realtime principal, no JWT cookie, and therefore no socket, so it never receives these messages (true anonymous/Public-role realtime is not offered and would require a separate, restricted model). Broadcast Pub/Sub messages, such as list-view entity-change events, must be context-free nudges; sensitive or authoritative state must not be published on the broadcast scope. Targeted Pub/Sub messages may carry task state only when the producer names routing keys derived from an authorized identity, such as a task subscriber's principal channel (or a per-tab channel derived from it); the producer validates every routing key against the task's own subscriber principals before publishing, and the websocket server forwards the payload only to sockets bound to those keys. Full data and result payloads must still be fetched through the normal protected REST API or cache-read path. Redis Streams used for task completion, dependency, and lock-release signalling are likewise coordination signals; the metastore or cache entry they wake a consumer to read remains the source of truth.
-
-The realtime notification permission is distinct from the permission to read the underlying object. It controls whether a principal receives push notifications, not whether they may read the object once they call the protected REST API. Existing websocket connections are authorized by the JWT accepted at upgrade time; permission revocation after token minting is bounded by `WEBSOCKET_JWT_EXPIRATION_SECONDS` plus the websocket server's socket-check interval. Redis Streams are internal server-to-server coordination primitives and should not be directly exposed as an end-user subscription surface.
-
 ### Vulnerability Scope

 The test for whether a finding is in scope is a single question:
@@ -24,214 +24,6 @@ assists people when migrating to a new version.

 ## Next

-### Global Async Queries re-platformed onto the Global Task Framework (breaking)
-
-Global Async Queries (GAQ) no longer runs on its own bespoke async-events
-plumbing. Async chart data is now executed as Global Task Framework (GTF) tasks
-(one task per `QueryObject`), the browser learns of completion by polling
-`GET /api/v1/task/status_changes` (optionally accelerated by the WebSocket
-transport below) and re-issuing the original `/chart/data` request against the
-now-warm per-query cache, and the realtime WebSocket server is a generic,
-feature-agnostic task push transport rather than a GAQ-specific event tail.
-
-Breaking removals (no deprecation window):
-
- The `/api/v1/async_event/` REST API, `AsyncQueryManager`, and the
-  `qc-<hash>` query-context descriptor replay endpoint
-  (`GET /api/v1/chart/data/<cache_key>`) are removed. Any client that consumed a
-  `result_url` from a `202` response must move to the re-request model (the
-  built-in frontend already does).
- The following config keys are removed: `GLOBAL_ASYNC_QUERIES_CACHE_BACKEND`,
-  `GLOBAL_ASYNC_QUERIES_TRANSPORT`, `GLOBAL_ASYNC_QUERIES_WEBSOCKET_URL`,
-  `GLOBAL_ASYNC_QUERIES_REDIS_STREAM_PREFIX`,
-  `GLOBAL_ASYNC_QUERIES_REDIS_STREAM_LIMIT`,
-  `GLOBAL_ASYNC_QUERIES_REDIS_STREAM_LIMIT_FIREHOSE`,
-  `GLOBAL_ASYNC_QUERIES_REGISTER_REQUEST_HANDLERS`,
-  `GLOBAL_ASYNC_QUERIES_JWT_*`, and
-  `GLOBAL_ASYNC_QUERY_MANAGER_CLASS`. The coordinator (locks, GTF, and now GAQ)
-  uses `DISTRIBUTED_COORDINATION_CONFIG` exclusively.
-
-Enabling async chart data in the new flow:
-
-```python
-# feature flag: makes async chart data available (auto-enables GLOBAL_TASK_FRAMEWORK)
-FEATURE_FLAGS = {"GLOBAL_ASYNC_QUERIES": True}
-
-# a Redis connection for distributed coordination (locks, GTF signalling,
-# and the realtime pub/sub); required for async execution in production
-DISTRIBUTED_COORDINATION_CONFIG = {
-    "CACHE_TYPE": "RedisCache",
-    "CACHE_REDIS_HOST": "localhost",
-    "CACHE_REDIS_PORT": 6379,
-    "CACHE_REDIS_DB": 0,
-}
-```
-
-Async is now **opt-in per request**: `GLOBAL_ASYNC_QUERIES` only makes async
-*available*; whether a given `/chart/data` request runs async is decided by an
-`async_mode` request flag (endpoint default `false`, so programmatic API clients
-keep the synchronous `200` flow unless they opt in). The built-in frontend
-resolves the `async_mode` it sends from a policy chain — per-dashboard override →
-deployment default `GLOBAL_ASYNC_QUERIES_DEFAULT` (default `true`) → the feature
-flag — so the UI keeps its existing async behavior by default.
-
-**Embedded (guest token) async requires explicit role grants.** Async chart-data
-completion is observed through `GET /api/v1/task/status_changes` (gated by
-`can_read Task`) and, when the WebSocket transport is enabled, over the socket
-(gated by `can_read Realtime`). An authenticated Gamma user has `can_read Task` by
-default; the default guest role (`Public`) does **not**. So an embedded guest only
-runs async when the operator grants its role `can_read Task` (and `can_read
-Realtime` for the socket) — otherwise the request transparently falls back to the
-synchronous `200` flow rather than returning a `202` the guest could never resolve.
-
-Enabling the realtime WebSocket transport (optional; when enabled it becomes the
-completion transport for async chart-data — see the note on the interval poll):
-
-> **Note:** the realtime WebSocket transport is opt-in (`WEBSOCKET_ENABLE`
-> defaults to `False`). When it is **disabled**, async chart-data completion is
-> driven entirely by the `status_changes` interval poll (the source of truth).
-> When it is **enabled**, completion is delivered over the socket and the
-> recurring interval poll does not run; a one-shot `status_changes` catch-up on
-> waiter registration and on socket reconnect reconciles anything missed while
-> disconnected. The socket accelerates delivery over the authoritative
-> `status_changes` API rather than replacing it: Redis Pub/Sub is best-effort
-> (at-most-once, no replay), so a disconnect is reconciled by the catch-up on
-> reconnect/registration. In the rare case a `task.status` is missed while the
-> socket stays open, the request's give-up runs one final `status_changes` read
-> before timing out — so a chart whose query actually finished still resolves; only
-> if that read can't confirm completion does the request end in a bounded error (a
-> page reload re-establishes state).
-
-```python
-WEBSOCKET_ENABLE = True
-WEBSOCKET_URL = "ws://<same-host>:8080/"
-WEBSOCKET_JWT_SECRET = "<output of: openssl rand -base64 42>"
-```
-
-The built-in Gamma role receives `can_read Realtime`; grant that permission to
-custom roles that should receive websocket notifications.
-
-Run the `superset-websocket` Node server on the **same browser-visible host**
-(so its JWT channel cookie is shared) and point its `redis` config at the same
-instance as `DISTRIBUTED_COORDINATION_CONFIG`, plus `jwtSecret` /
-`jwtCookieName` matching the Flask config (`WEBSOCKET_JWT_SECRET` /
-`WEBSOCKET_JWT_COOKIE_NAME`, default `superset-ws-token`). During websocket JWT
-secret rotation, set the websocket server's `previousJwtSecret` /
-`PREVIOUS_JWT_SECRET` to the old key while Flask continues minting cookies with
-`WEBSOCKET_JWT_SECRET`. The server is bundled in the official Superset image
-and launched via an alternate entrypoint — no separate image is required:
-`docker run <superset-image> /app/docker/entrypoints/run-websocket.sh` (or the
-opt-in `websocket` profile in `docker compose`). It **subscribes** to a single
-Redis Pub/Sub channel, `realtime`, which carries a self-describing
-`{topic, scope, routes, payload}` envelope (both the broadcast `entity.changed`
-nudges and the targeted `task.status` messages), and forwards `{topic, payload}`
-to browsers after routing — so a Redis ACL for the websocket server must allow
-subscribing to `realtime` (this replaces the earlier `entity-changes:*` /
-`task-status` channels); see `superset-websocket/README.md`.
-
-Orphaned GTF tasks (a worker killed mid-execution) are now detected and cleaned
-up server-side. While a worker holds a task it writes a liveness heartbeat
-(`tasks.last_heartbeat`, every `GTF_TASK_HEARTBEAT_INTERVAL` seconds, default
-`15`); a dedicated `reap_orphaned_tasks` Celery beat job reaps any active task
-whose heartbeat is older than `GTF_ORPHAN_TASK_TIMEOUT` (default `60`) — revoking
-its Celery job, marking it `FAILURE` so waiters unblock, and (on engines that
-support query cancellation) cancelling the abandoned warehouse query out-of-band.
-Enable the `reap_orphaned_tasks` beat schedule on a short interval (e.g. every
-minute); it is separate from `prune_tasks` (a heavier retention delete run
-infrequently). The heartbeat write is issued out-of-band and deliberately does
-not advance `changed_on`.
-
-Async chart-data query tasks are now cancellable: a per-query timeout
-(`GLOBAL_ASYNC_QUERIES_QUERY_TIMEOUT`, default `None` = unbounded) or a user
-cancel aborts the task, and on database engines that support query cancellation
-(e.g. PostgreSQL, MySQL, Snowflake, Redshift) the abort also cancels the running
-warehouse query over a fresh connection — including when the worker died (the
-reaper cancels it). Engines without cancel support are unaffected — the task is
-still freed, but the query runs to completion.
-
- Calculated (expression) dataset columns are now wrapped in parentheses when
-  compiled to SQL (`(<expression>)`), in `SELECT`, `GROUP BY`, `ORDER BY`,
-  `COUNT(DISTINCT ...)`, and the series-limit (top-N) prequery/JOIN paths. This
-  fixes a correctness bug where a bare boolean operator (e.g. `OR`) inside a
-  calculated column used as a series dimension leaked into the surrounding
-  operator precedence (`state = 'CA' OR state = 'NY' = 1` mis-parsing as
-  `state = 'CA' OR (state = 'NY' = 1)`). Query results are otherwise unchanged,
-  but the generated SQL text for calculated-column queries differs; deployments
-  that key on the exact compiled SQL (custom result-cache keys, logging, or SQL
-  diffing) may observe the added parentheses. Physical columns are unaffected,
-  as are calculated columns used as a temporal (time/x-axis) dimension, which
-  resolve through a separate time-grain path (`get_timestamp_expression`).
-
- **[BREAKING] `SemanticLayer` and `SemanticView` are now classified in the
-  Flask-AppBuilder role sets**, so `sync_role_definitions` (run on
-  `superset init` and on startup) stops granting the built-in **Gamma** role
-  write access to them. `SemanticLayer` is treated like `Database`
-  (`READ_ONLY_MODEL_VIEWS`): create/edit/delete become **admin-only**, while
-  read stays broadly available (its configuration is returned masked).
-  `SemanticView` is treated like `Dataset` (`GAMMA_READ_ONLY_MODEL_VIEWS`):
-  writes are Alpha-tier, reads Gamma-tier. Its custom read endpoints
-  (`views`, `connections`) are mapped to `can_read` so they remain
-  accessible under the read-only classification. A deployment relying on
-  Gamma users creating or editing semantic layers/views must grant those
-  permissions through a custom role. A migration retires the now-unused
-  `can_views` / `can_connections` permissions left on the `SemanticLayer`
-  view menu by earlier builds. Two upgrade-time notes on that migration:
-  it seeds the `SemanticLayer` view menu and its `can_read` PVM if absent, so
-  even a fresh or flag-off install gains that permission (harmless — the
-  endpoints 404 while `SEMANTIC_LAYERS` is off); and retiring the stale
-  permissions remaps any role that held them onto `can_read`, a small
-  widening — a custom role granted only `can_views` or `can_connections` gains
-  `can_read` (the semantic-layer list and its masked-configuration detail),
-  which it could not previously reach. Operators who hand-rolled semantic-layer
-  roles should re-audit them after upgrading. The feature remains gated behind
-  the default-off `SEMANTIC_LAYERS` flag.
-
-### Archived dataset purge requires impact confirmation
-
-`GET /api/v1/dataset/<uuid>/purge-impact` returns the charts and distinct
-dashboards affected by permanently deleting an archived dataset, together with
-an opaque `impact_token`. The dataset purge endpoint now requires that token in
-the JSON body as `confirmed_impact_token`. API clients that call
-`POST /api/v1/dataset/<uuid>/purge` must fetch and display the impact first;
-requests with a missing or malformed token are rejected with 400.
-
-The server rechecks the dependency identities immediately before mutation. If
-they changed, purge performs no deletion and returns 409 with a refreshed impact
-payload. Clients must display the new impact and obtain renewed confirmation
-before retrying. Preview or recheck failures fail closed rather than treating
-unknown impact as zero. Chart and dashboard purge endpoints are unchanged.
-
- The dashboard datasource-based visibility fallback now fails closed: a dashboard whose member charts’ datasources cannot be resolved (deleted datasource rows, missing `datasource_id`, or unsupported datasource types) is no longer accessible to users without explicit editor/viewer rights, and a dashboard composed of semantic-view charts now requires `datasource_access` on (at least one of) its semantic views or their parent semantic layer — previously any authenticated user could open such a dashboard’s shell. Because the fallback now considers every member chart rather than only table-backed ones, a user holding `datasource_access` on any single member datasource — including a semantic view or its parent layer — can open a mixed dashboard that previously denied them. Dashboards with no charts remain accessible, and dashboards with explicit viewers are unaffected. Conversely, holders of `all_datasource_access` now see every published no-viewer dashboard in the dashboard list — including chart-less ones previously hidden by the inner joins — matching what the object-level gate already allowed them to open.
- `SAMPLES_ROW_LIMIT` is now the default for `/datasource/samples` requests without a valid explicit `per_page`, rather than a hard per-request ceiling; explicit limits are honored up to the existing global row-limit ceiling, matching `/chart/data` SAMPLES requests.
- The `cockroachdb` extra (`pip install apache-superset[cockroachdb]`) now installs `sqlalchemy-cockroachdb` instead of the abandoned `cockroachdb` package, whose SQLAlchemy dialect could not be imported under SQLAlchemy 2.0. Existing environments with the old package installed should `pip uninstall cockroachdb && pip install sqlalchemy-cockroachdb` (or simply reinstall the extra) to restore CockroachDB connectivity.
-
-### Native Value filter "Select all" always targets the whole column
-
-The native "Value" filter's bulk "Select all" / "Clear" controls now operate on the entire loaded set of column values regardless of any text typed into the filter's search box. Previously the "Select all (N)" count briefly flickered to the search-scoped count before settling on the full-column count, and clicking "Select all" while searching could select only the currently matching subset. Search-scoped bulk selection was never a supported feature; the count is now stable and always matches what "Select all" selects (the full column). No configuration change is required.
-
-### MCP tool results preserve stored string values
-
-Structured MCP tool results no longer add `<UNTRUSTED-CONTENT>` wrappers or
-rewrite delimiter-looking text inside string fields. Tool-result content remains
-user-controlled data, but clients must convey that trust boundary outside domain
-values instead of recognizing or removing marker strings.
-
-Clients that handled the former delimiter convention should stop stripping marker
-text: the same text can be legitimate stored content. Response models and content
-types are unchanged, and no metadata-database migration is required. Automated
-read-modify-write workflows should be paused or pinned away from older instances
-until every serving instance is upgraded; a mixed-version response has no reliable
-signal that tells a client whether its text is decorated. Redis-backed MCP response
-caches use a new internal namespace after the upgrade, so upgraded instances do not
-reuse older cached results.
-
-Values that a client already wrote back with presentation wrappers cannot be
-distinguished safely from intentional content. Operators should review possible
-`<UNTRUSTED-CONTENT>` / `</UNTRUSTED-CONTENT>` wrappers and
-`[ESCAPED-UNTRUSTED-CONTENT-OPEN]` /
-`[ESCAPED-UNTRUSTED-CONTENT-CLOSE]` substitutions rather than applying an automatic
-marker-removal migration.
-
 ### OAuth2 database callback metrics include their outcome

 The unqualified `DatabaseRestApi.oauth2` StatsD counter has been replaced with
@@ -239,10 +31,7 @@ The unqualified `DatabaseRestApi.oauth2` StatsD counter has been replaced with
 `DatabaseRestApi.oauth2.error`. Update monitoring rules and dashboards that consume
 the old counter to use the outcome-specific replacements.

- [42930](https://github.com/apache/superset/pull/42930): Dataset import data-URI fetches no longer honor an HTTP(S) proxy when `DATASET_IMPORT_ALLOW_INTERNAL_DATA_URLS` is `False` (the default): the connection is now made directly to the destination so the peer-address check validates the real target instead of a proxy's. Deployments that require an egress proxy to reach legitimate external data URLs for dataset import should set `DATASET_IMPORT_ALLOW_INTERNAL_DATA_URLS = True` or otherwise ensure those URLs resolve without one.
 - [42935](https://github.com/apache/superset/pull/42935): The MCP service now refuses to start (`MCPAuthConfigError`) when `MCP_JWT_ISSUER` trusts more than one issuer and no `MCP_USER_RESOLVER` is configured, instead of only logging a warning. This was already a documented misconfiguration (the default resolver isn't issuer-scoped, so distinct trusted issuers minting the same username/email would resolve to the same Superset user); deployments trusting multiple issuers must configure an `MCP_USER_RESOLVER` that derives its identity from the token's `iss` claim before upgrading. Single-issuer deployments are unaffected.
- [42429](https://github.com/apache/superset/pull/42429): The Country Map chart's Iran GeoJSON now gives Alborz province its own ISO 3166-2 code, `IR-32`, instead of `IR-30`. `ISO` is the join key used to color/filter provinces on this chart, so any existing dataset keyed on `IR-30` for Alborz will silently stop matching after upgrading; re-key that data to `IR-32`.
- [43388](https://github.com/apache/superset/pull/43388): The MCP service now refuses to start (`MCPAuthConfigError`) if `MCP_DEV_USERNAME` and `MCP_AUTH_ENABLED = True` are both set, and separately if `MCP_AUTH_ENABLED = True` but no usable JWT key material is configured (RSA key/JWKS, or an explicit `MCP_JWT_SECRET` for HMAC) — both previously started with authentication silently weaker than configured. Deployments combining a dev-mode username with JWT auth enabled, or enabling JWT auth without key material, must pick one before upgrading: unset `MCP_DEV_USERNAME` for a real auth deployment, or unset `MCP_AUTH_ENABLED` (or configure the key material) for a dev-mode one. Response caching (`MCP_CACHE_CONFIG["enabled"] = True`) now also excludes every tool with a side effect by default, not only a partial list, so a previously-cached mutating tool call is no longer served from cache; no config change is needed to pick this up.
 - [42393](https://github.com/apache/superset/pull/42393): Exported dataset YAML now carries a `uuid` for each metric and column so that custom folder assignments (which reference metrics/columns by UUID) survive an import into another workspace. This affects any export bundle that contains datasets, not just a dataset export: chart, dashboard, database and full-asset exports all embed the same dataset YAML, so a dashboard exported from this release also fails to import into an older one even though no dataset was exported directly. As with `folders` and `currency_code_column`, the affected `datasets/` files fail schema validation (`Unknown field: uuid`) when imported into Superset releases that predate this change; regenerate or hand-edit exports for older targets in mixed-version fleets.
 - [42300](https://github.com/apache/superset/pull/42300): Timeseries charts (line/area/bar) with a Y-axis bound in effect — either an explicit `yAxisBounds` or one derived from `truncateYAxis` — now clamp out-of-range data points to that bound instead of letting ECharts drop the point (and the line segments around it) entirely. Any existing chart with a configured Y-axis bound and data outside it will look different after upgrading: a gap becomes a point pinned to the boundary. The clamp also rewrites the value ECharts reads for that point's tooltip and data label, so the displayed value is the bound rather than the true observation.
 - [42087](https://github.com/apache/superset/pull/42087): Stored calculated-column and metric expressions are validated when a query is built, under the same sub-query policy already applied to adhoc expressions. Previously only the dataset update path checked them on save, so expressions written by v1 import, by dataset duplication, or before that check existed were never validated. Since `ALLOW_ADHOC_SUBQUERY` defaults to `False` (see [19242](https://github.com/apache/superset/pull/19242)), a dataset whose stored expression contains a sub-query works before upgrading and afterwards fails at chart render with `Custom SQL fields cannot contain sub-queries.` There is no migration step, and the error does not name the offending dataset column, so audit stored expressions before upgrading: either rewrite them without the sub-query, or set `ALLOW_ADHOC_SUBQUERY = True` to keep the previous behaviour for both stored and adhoc expressions.
@@ -310,23 +99,6 @@ dialect; each package's constraint in `pyproject.toml` documents why.
 No application-level configuration changes are required for deployments
 that don't touch SQLAlchemy directly.

-### New metric aggregates: MEDIAN, Sample Standard Deviation, Sample Variance
-
-`MEDIAN`, `STDDEV_SAMP`, and `VAR_SAMP` are now available anywhere a metric
-aggregate is chosen (every chart type, SQL Lab, MCP), not only in Pivot
-Table's controls. Support is opt-in per database engine *spec class*,
-verified against a live instance before being enabled: Postgres, MySQL
-(`STDDEV_SAMP`/`VAR_SAMP` only, no `MEDIAN`), DuckDB, and Redshift (inherits
-Postgres's support, not yet separately verified) ship enabled in this
-release. Engine specs that subclass one of those (e.g. MariaDB, Aurora
-MySQL/Postgres, TimescaleDB) inherit the same support, on the same
-not-yet-independently-verified basis. Picking one of these aggregates on a
-database that has not opted in returns a clear "not supported on this
-database" error rather than a failed query. See
-`docs/sip/median-stddev-variance-aggregates.md` for the full design
-rationale, including why this is safe to add without reintroducing the
-totals/subtotals correctness bug fixed by #41184 (SIP-216).
-
 ### Soft delete is on by default, and purging is live

 `SOFT_DELETE` now ships **on** (`DEFAULT_FEATURE_FLAGS`), so deleting a
@@ -368,12 +140,10 @@ misrepresents the entity as unchanged.
 - **Storage growth.** Capture writes shadow rows per save, so the metadata
  database grows with edit volume. The `version_history.prune_old_versions`
  beat task removes rows whose transaction is older than
-  `SUPERSET_VERSION_HISTORY_RETENTION_DAYS` (default 30).
- **Check a replaced `CELERY_CONFIG`.** Carry both the
-  `superset.tasks.version_history_retention` import and the
-  `version_history.prune_old_versions` beat entry; see
-  [Version-history retention (pruning)](#version-history-retention-pruning) for
-  the startup-warning behavior.
+  `SUPERSET_VERSION_HISTORY_RETENTION_DAYS` (default 30). A deployment that
+  replaces `CELERY_CONFIG` rather than inheriting it must carry both the
+  `superset.tasks.version_history_retention` import and the beat entry; a
+  startup warning names whichever is absent.
 - **`PUT` responses change shape.** Entity updates now return populated
  `old_version_uuid` / `new_version_uuid` fields and an `ETag` header, which
  were null or absent while capture was off.
@@ -382,10 +152,7 @@ misrepresents the entity as unchanged.
 kill-switch — not removed with the rollout toggles. Setting it to a falsy value
 stops capture within a restart, without a revert-and-redeploy. Unlike the
 soft-delete toggle, turning it off is a clean stop: existing version rows remain
-readable and no entity state is altered. Restore is unavailable (404) while
-capture is off. A full rollback also sets
-`FEATURE_FLAGS = {"VERSION_HISTORY": False}` to hide the panel — capture off
-with the panel left on shows an empty or stale history.
+readable and no entity state is altered.

 ### Scheduled report execution now enforces one application deadline

@@ -412,10 +179,8 @@ Behavior changes to be aware of:
  fail fast at the first phase check rather than erroring at setup.
 - Dashboard reports whose charts have not mounted are no longer captured
  blank: readiness is polled until the deadline, and the report fails loudly
-  if charts never mount. Large tiled reports also retry Chromium screenshot
-  stalls and suspicious uniform tiles, while persistent screenshot timeouts
-  fail loudly. Large tiled thumbnails use the same bounded retries, but retain
-  their previous failure contract after a persistent timeout.
+  if charts never mount. Thumbnails and non-report screenshots keep their
+  previous behavior.

 ### Embedded (guest token) API responses no longer echo database errors

@@ -849,9 +614,9 @@ ALTER TABLE tagged_object DROP CONSTRAINT <constraint_name>;
 ALTER TABLE tagged_object DROP FOREIGN KEY <constraint_name>;
 ```

-### Entity version-history infrastructure
+### Entity version-history infrastructure (gated off by default)

-Introduces the schema and SQLAlchemy-Continuum wiring that captures version history for charts, dashboards, and datasets, plus read-only `GET /api/v1/{chart,dashboard,dataset}/<uuid>/versions/` endpoints. Capture is governed by the `ENABLE_VERSIONING_CAPTURE` config value — an operational kill-switch (a release toggle that became a permanent ops switch), not a feature flag; see "Version history is on by default" above for the shipped default. With capture off, no save writes version rows; the endpoints continue to serve already-captured rows read-only. The migration is additive; existing entity `PUT` responses gain `old_version_uuid` / `new_version_uuid` body fields and an `ETag` header (both null/absent when capture is off).
+Introduces the schema and SQLAlchemy-Continuum wiring that captures version history for charts, dashboards, and datasets, plus read-only `GET /api/v1/{chart,dashboard,dataset}/<uuid>/versions/` endpoints. This ships **inert**: a new config flag `ENABLE_VERSIONING_CAPTURE` defaults to `False`, so no save writes any version rows and the endpoints return empty. It is an operational kill-switch (a release toggle that becomes a permanent ops switch), not a feature flag — set it to `True` to enable capture once validated. The migration is additive; existing entity `PUT` responses gain `old_version_uuid` / `new_version_uuid` body fields and an `ETag` header (both null/absent when capture is off).

 A few save- and import-path internals change **unconditionally** (independent of the flag), because the versioned mappers must behave correctly whether or not capture is enabled:

@@ -872,7 +637,7 @@ A read-only companion to the version-history endpoints: each entity type gains a
 | `q`                  | string                       | —          | Case-insensitive search over the full history, applied before pagination (so `count` reflects matches) |
 | `page` / `page_size` | integer                      | `0` / `25` | Pagination (`page_size` clamped to 200)                                                                |

-Authorization reuses the resource's `can_read` permission and per-object `raise_for_access`; related-entity rows are visibility-filtered to what the caller may see. The stream reflects captured history; with capture off it remains readable but stops accruing new entries.
+Authorization reuses the resource's `can_read` permission and per-object `raise_for_access`; related-entity rows are visibility-filtered to what the caller may see. The stream is empty unless version capture is on (`ENABLE_VERSIONING_CAPTURE`).

 ### Version-history retention (pruning)

@@ -892,7 +657,7 @@ Purging is **live by default** (`SOFT_DELETE_PURGE_DRY_RUN=False`), so the reten

 Deployments that replace the default `CELERY_CONFIG` must ensure workers register `superset.tasks.deletion_retention` and schedule the `deletion_retention.purge_soft_deleted` task themselves. The shipped Docker development config uses `imports` and includes both entries. While `SOFT_DELETE` is statically enabled, a missing beat entry logs a startup warning; when the override explicitly defines `imports`, a missing purge module is also reported.

-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 scheduled evaluation writes a provisional, content-free record to the new `purge_audit_log` table before the cascade starts. Meaningful retained outcomes survive the entity they name. Blocked audit records carry a stable machine-readable `reason` code (`report_schedule`, `user_attribute`, or `cascade_integrity_failure` for an unexpected cascade failure caused by a database integrity constraint) so the audit table alone answers why an entity was not purged; records finalized before the column existed keep a NULL reason. Apply the migration before rolling out the new code: the audit model declares the column, so a worker on the new code with an un-migrated table fails its write-ahead write and the scheduled purge fails closed until the migration lands. During a rolling deploy, workers still on the old code write reason-less blocked rows and suppress on status alone; both effects are self-healing, since a NULL-reason record never matches a reason code and the next all-new-code run re-anchors the entity. Consecutive scheduled evaluations blocked with the same status **and reason** suppress only the redundant current provisional record — a reason change writes one new blocked record carrying the new code; completed outcomes, outcome transitions, and every force-purge attempt remain independent and immutable. Retained transition records are not automatically expired, so entities whose block reason changes repeatedly can accumulate multiple audit rows. The **scheduled** purge fails closed when its provisional record cannot be written, while **force-purge** proceeds even if the audit write fails — the operator is present and deletion outranks audit for a compliance erasure. Operators can monitor `deletion_retention.blocked_audit_suppressed` and `deletion_retention.blocked_audit_dedupe_fallback` to verify suppression and fail-safe fallback behavior without changing the existing blocked-workload gauge.
+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 scheduled evaluation writes a provisional, content-free record to the new `purge_audit_log` table before the cascade starts. Meaningful retained outcomes survive the entity they name. Consecutive scheduled evaluations with the same blocked outcome suppress only the redundant current provisional record; completed outcomes, outcome transitions, and every force-purge attempt remain independent and immutable. The **scheduled** purge fails closed when its provisional record cannot be written, while **force-purge** proceeds even if the audit write fails — the operator is present and deletion outranks audit for a compliance erasure. Operators can monitor `deletion_retention.blocked_audit_suppressed` and `deletion_retention.blocked_audit_dedupe_fallback` to verify suppression and fail-safe fallback behavior without changing the existing blocked-workload gauge.

 ### Recently Archived view and permanent delete (purge) endpoints

@@ -1088,7 +853,7 @@ The migration is transactional (all-or-nothing) and idempotent — it can be saf

 ### Soft delete and restore for datasets

-**The soft-delete behavior in this section applies only when the `SOFT_DELETE` feature flag is enabled. The flag defaults to `True`** (`@lifecycle: testing`), so on a default deployment `DELETE /api/v1/dataset/<id>` uses the recoverable soft-delete behavior described below. Setting `SOFT_DELETE` to `False` restores legacy permanent hard-delete behavior for subsequent deletes.
+**The soft-delete behavior in this section applies only when the `SOFT_DELETE` feature flag is enabled. The flag defaults to `False`** (`@lifecycle: development`), so on a default deployment `DELETE /api/v1/dataset/<id>` continues to **hard-delete permanently** — nothing is recoverable. Enable `SOFT_DELETE` to get the behavior described below.

 **Flag-toggle caveat:** the soft-delete visibility filter is evaluated per query while the flag is on. If datasets are soft-deleted during a flag-on window and the flag is later turned **off**, those rows reappear as live datasets in all lists, lookups, and relationship loads (including charts that reference them). The `POST /<uuid>/restore` endpoint and the `dataset_deleted_state` list filter remain functional regardless of the flag, deliberately, so rows soft-deleted during a flag-on window stay discoverable and restorable after a rollback of the flag.

@@ -1118,7 +883,7 @@ With the flag enabled: `DELETE /api/v1/dataset/<id>` no longer hard-deletes the

 ### Soft delete and restore for charts

-**Everything in this section applies only when the `SOFT_DELETE` feature flag is enabled. The flag defaults to `True`** (`@lifecycle: testing`), so on a default deployment `DELETE /api/v1/chart/<id>` uses the recoverable soft-delete behavior described below. Setting `SOFT_DELETE` to `False` restores legacy permanent hard-delete behavior for subsequent deletes.
+**Everything in this section applies only when the `SOFT_DELETE` feature flag is enabled. The flag defaults to `False`** (`@lifecycle: development`), so on a default deployment `DELETE /api/v1/chart/<id>` continues to **hard-delete permanently** — nothing is recoverable. Enable `SOFT_DELETE` to get the behavior described below.

 **Flag-toggle caveat:** the soft-delete visibility filter is evaluated per query while the flag is on. If charts are soft-deleted during a flag-on window and the flag is later turned **off**, those rows reappear as live charts in all lists, lookups, and relationship loads (including dashboards that contained them). The `POST /<uuid>/restore` endpoint and the `chart_deleted_state` list filter remain functional regardless of the flag, deliberately, so rows soft-deleted during a flag-on window stay discoverable and restorable after a rollback of the flag.

@@ -1142,7 +907,7 @@ With the flag enabled: `DELETE /api/v1/chart/<id>` no longer hard-deletes the ch

 ### Soft delete and restore for dashboards

-**Everything in this section applies only when the `SOFT_DELETE` feature flag is enabled. The flag defaults to `True`** (`@lifecycle: testing`), so on a default deployment `DELETE /api/v1/dashboard/<id>` uses the recoverable soft-delete behavior described below. Setting `SOFT_DELETE` to `False` restores legacy permanent hard-delete behavior for subsequent deletes.
+**Everything in this section applies only when the `SOFT_DELETE` feature flag is enabled. The flag defaults to `False`** (`@lifecycle: development`), so on a default deployment `DELETE /api/v1/dashboard/<id>` continues to **hard-delete permanently** — nothing is recoverable. Enable `SOFT_DELETE` to get the behavior described below.

 **Flag-toggle caveat:** the soft-delete visibility filter is evaluated per query while the flag is on. If dashboards are soft-deleted during a flag-on window and the flag is later turned **off**, those rows reappear as live dashboards in all lists and lookups (including slug lookups — if a soft-deleted dashboard's slug was reused while the flag was on, both rows become visible with the same slug). The `POST /<uuid>/restore` endpoint and the `dashboard_deleted_state` list filter remain functional regardless of the flag, deliberately, so rows soft-deleted during a flag-on window stay discoverable and restorable after a rollback of the flag.

@@ -137,41 +137,6 @@ services:
    healthcheck:
      disable: true

-  # Realtime WebSocket transport, launched from the official image via its
-  # alternate entrypoint (no separate image needed). Opt-in — start it with
-  # `docker compose --profile websocket up`. To actually use it, the Superset
-  # app must also set WEBSOCKET_ENABLE=true, WEBSOCKET_URL, and a matching
-  # WEBSOCKET_JWT_SECRET (== the JWT_SECRET below) in docker/.env-local.
-  superset-websocket:
-    build:
-      <<: *common-build
-    container_name: superset_websocket
-    profiles:
-      - websocket
-    # Neither a volume mount nor the root user is needed: the entrypoint and the
-    # Node bundle it runs are both baked into the image, and the server is
-    # configured entirely through the environment below.
-    command: ["/app/docker/entrypoints/run-websocket.sh"]
-    environment:
-      REDIS_HOST: redis
-      REDIS_PORT: 6379
-      PORT: 8080
-      JWT_COOKIE_NAME: superset-ws-token
-      # Dev-only default; must match the app's WEBSOCKET_JWT_SECRET and be
-      # replaced with a strong secret (>= 32 bytes) outside local development.
-      JWT_SECRET: ${WEBSOCKET_JWT_SECRET:-dev-only-websocket-secret-change-me!}
-      # Optional verify-only old key for websocket JWT secret rotation.
-      PREVIOUS_JWT_SECRET: ${WEBSOCKET_PREVIOUS_JWT_SECRET:-}
-    restart: unless-stopped
-    ports:
-      - 8080:8080
-    depends_on:
-      redis:
-        condition: service_started
-    # Overrides the image-level HEALTHCHECK, which probes the Superset app.
-    healthcheck:
-      test: ["CMD-SHELL", "curl -f http://localhost:8080/health"]
-
 volumes:
  superset_home:
    external: false
@@ -19,14 +19,6 @@
 #
 HYPHEN_SYMBOL='-'

-STATSD_ARGS=()
-STATSD_HOST="${SERVER_STATSD_HOST//[[:space:]]/}"
-if [ -n "${STATSD_HOST}" ]; then
-    STATSD_PORT="${SERVER_STATSD_PORT//[[:space:]]/}"
-    STATSD_PORT="${STATSD_PORT:-8125}"
-    STATSD_ARGS=(--statsd-host "${STATSD_HOST}:${STATSD_PORT}" --statsd-prefix "${SERVER_STATSD_PREFIX:-superset}")
-fi
-
 exec gunicorn \
    --bind "${SUPERSET_BIND_ADDRESS:-0.0.0.0}:${SUPERSET_PORT:-8088}" \
    --access-logfile "${ACCESS_LOG_FILE:-$HYPHEN_SYMBOL}" \
@@ -41,5 +33,4 @@ exec gunicorn \
    --max-requests-jitter ${WORKER_MAX_REQUESTS_JITTER:-0} \
    --limit-request-line ${SERVER_LIMIT_REQUEST_LINE:-0} \
    --limit-request-field_size ${SERVER_LIMIT_REQUEST_FIELD_SIZE:-0} \
-    "${STATSD_ARGS[@]}" \
    "${FLASK_APP}"
@@ -1,44 +0,0 @@
-#!/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
-# 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
-#
-# 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
-# specific language governing permissions and limitations
-# under the License.
-#
-# Launch the realtime WebSocket server (superset-websocket) bundled in the
-# official image. Run it with:
-#
-#   docker run <superset-image> /app/docker/entrypoints/run-websocket.sh
-#
-# Configure via environment variables — see superset-websocket/src/config.ts for
-# the authoritative, complete set (Redis connection, logging, connection limits,
-# StatsD, etc.). The values that MUST match the Flask app's config are:
-#   JWT_SECRET      == WEBSOCKET_JWT_SECRET
-#   JWT_COOKIE_NAME == WEBSOCKET_JWT_COOKIE_NAME (default superset-ws-token)
-#   REALTIME_CHANNEL_PREFIX == Flask REALTIME_CHANNEL_PREFIX (default empty; set a
-#     per-deployment value on both sides to isolate a shared Redis/Valkey)
-# Optional rotation setting:
-#   PREVIOUS_JWT_SECRET == old WEBSOCKET_JWT_SECRET accepted for verification
-# and the Redis connection (REDIS_HOST/REDIS_PORT/...) must point at the same
-# instance as the app's DISTRIBUTED_COORDINATION_CONFIG.
-set -e
-
-# Run from a writable directory so that opting into file logging with the
-# default relative LOG_FILENAME (LOG_TO_FILE=true) writes somewhere the
-# unprivileged `superset` user can create files, rather than the read-only /app.
-# The config.json lookup is unaffected (it resolves relative to the bundle).
-cd "${SUPERSET_HOME:-/app/superset_home}"
-
-exec node /app/superset-websocket/dist/index.cjs start
@@ -15,8 +15,8 @@
    "db": 0,
    "ssl": false
  },
+  "redisStreamPrefix": "async-events-",
  "jwtAlgorithms": ["HS256"],
  "jwtSecret": "CHANGE-ME-IN-PRODUCTION-GOTTA-BE-LONG-AND-SECRET",
-  "previousJwtSecret": "",
-  "jwtCookieName": "superset-ws-token"
+  "jwtCookieName": "async-token"
 }
@@ -62,8 +62,8 @@ yarn version:remove:developer_docs <version> # Remove developer docs version
 yarn version:remove:components <version>     # Remove components version

 # Quality Checks
-yarn typecheck   # TypeScript validation
-yarn lint        # Lint TypeScript/JavaScript files
+yarn typecheck            # TypeScript validation
+yarn eslint              # Lint TypeScript/JavaScript files
 ```

 ## 📁 Documentation Structure
@@ -431,7 +431,7 @@ yarn build
 yarn typecheck

 # Linting issues
-yarn lint
+yarn eslint
 ```

 ### Version Issues
@@ -14,20 +14,6 @@ Users can configure automated alerts and reports to send dashboards or charts to

 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.

-## Content Format Options
-
-When scheduling an alert or report, you can choose the format used to deliver the dashboard or chart:
-
- **PDF** – a full-page screenshot rendered as a PDF attachment. Available for both dashboards and charts.
- **PNG** – a screenshot delivered as an attachment. Emails embed the image inline in the message body; Slack and webhook recipients receive it as an uploaded file. Available for both dashboards and charts.
- **CSV** – chart data attached as a `.csv` file. Available for charts only.
- **XLSX (Excel)** – chart data attached as a `.xlsx` file. Available for charts only. If the chart's data spans multiple server-paginated files, email delivery detects the bundle and renames the attachment to `.zip`; Slack and webhook deliveries always name the file with an `.xlsx` extension even when the contents are a multi-file ZIP archive.
- **Text** – chart data embedded directly in the email or Slack message body. Available only for charts using a text-based visualization type (e.g. Table, Pivot Table, Paired t-test).
-
-Dashboard reports and alerts are limited to the PDF and PNG formats; the CSV, XLSX, and Text options are only available when scheduling a report or alert for an individual chart.
-
-For alerts (not scheduled reports), PNG/PDF screenshots and chart CSV/XLSX data are only generated when the `ALERTS_ATTACH_REPORTS` [feature flag](/admin-docs/configuration/configuring-superset#feature-flags) is enabled (the default); with it disabled, an alert notification is still sent, but without the attachment.
-
 ## Requirements

 ### Commons
@@ -76,58 +76,6 @@ value defined in `DATA_CACHE_CONFIG`.
 Note, that by setting the cache timeout to `-1`, caching for charting data can be disabled, either
 per chart, dataset or database, or by default if set in `DATA_CACHE_CONFIG`.

-Native filter option queries (the dropdown values for native filters) go through this same
-chart-data cache, but their freshness needs often differ from regular chart queries, especially for
-datasets whose visible values change frequently, including RLS-constrained datasets. Set
-`NATIVE_FILTER_OPTIONS_CACHE_TIMEOUT` in `superset_config.py` to give these queries a dedicated
-timeout, checked before the chart/dataset/database chain and the `DATA_CACHE_CONFIG` default above:
-
-```python
-NATIVE_FILTER_OPTIONS_CACHE_TIMEOUT = 60  # seconds
-```
-
- `None` (default): native filter option queries fall through to the normal
-  chart/dataset/database/`DATA_CACHE_CONFIG` resolution chain.
- `-1`: disables caching for native filter option queries entirely.
- `0`: passed directly to the cache backend; behavior is backend-specific, so use `-1` if the intent
-  is to disable caching.
- A positive integer: cache native filter option queries for that many seconds.
-
-This setting only applies to requests detected as native filter option queries. It takes precedence
-over the per-chart/dataset/database timeouts, but not over an explicit per-request
-`custom_cache_timeout` override (e.g. "Force refresh").
-
-## Async Query Result Cache TTL
-
-When [Global Async Queries](/admin-docs/configuration/configuring-superset#feature-flags) is
-enabled, a chart-data request that runs asynchronously does not return the result inline. Instead the
-query executes on a background task that **writes the result to the data cache**, and the browser
-then re-issues the same request to read that result back out of the cache once the task succeeds.
-
-This read-back is what makes the result-cache TTL matter for correctness, not just performance: if
-the effective TTL is shorter than the full async round trip (task execution + the client's poll
-interval + the re-fetch), the entry can be **evicted before the client reads it**, leaving the chart
-stuck re-running instead of loading. To prevent this, async requests floor their result-cache TTL to
-`GLOBAL_ASYNC_QUERIES_MIN_CACHE_TTL` (seconds, default `300` — five minutes):
-
-```python
-GLOBAL_ASYNC_QUERIES_MIN_CACHE_TTL = 300  # seconds
-```
-
-How the floor interacts with the timeouts above:
-
- It applies **only to async execution**. Synchronous `/chart/data` requests keep their normal
-  chart/dataset/database/`DATA_CACHE_CONFIG` timeout even when Global Async Queries is enabled.
- A **longer** effective TTL from that chain is kept as-is — the floor only raises TTLs that are
-  shorter than it.
- A TTL of `0` ("cache forever") is left untouched.
-
-Tuning guidance: raise this value if your workload's async round trip can exceed five minutes (very
-long-running queries or slow warehouses), otherwise those charts may intermittently fail to load. Be
-aware of the trade-off — because the floor can raise an async result's TTL above a shorter cache
-retention policy, it keeps async results in the cache longer and modestly increases cache
-(Redis/Valkey) usage. Do not lower it below your worst-case async round trip.
-
 ## Limiting Cached Result Size

 Very large chart or SQL query results can flood the cache backend (Redis/Memcached), evicting many
@@ -347,25 +295,14 @@ high-performance distributed operations. This configuration enables:

 - **Distributed locking**: Moves lock operations from the metadata database to Redis, improving
  performance and reducing metastore load
- **Event-driven notifications**: Task completion and abort signals are delivered over Redis
-  **Streams**, so waiters (sync join-and-wait, task-dependency DAGs, abort listeners) wake when a
-  signal lands instead of polling the metadata database. Because stream entries are persisted, a
-  waiter that reads slightly late, reconnects, or fails over still receives the signal. Without this
-  backend, these operations poll the metadata database instead.
+- **Real-time event notifications**: Enables instant pub/sub messaging for task abort signals and
+  completion notifications instead of polling-based approaches

 :::note
-This requires Redis or Valkey specifically—it uses Redis-specific features (Streams, pub/sub,
-`SET NX EX`) that are not available in general Flask-Caching backends.
+This requires Redis or Valkey specifically—it uses Redis-specific features (pub/sub, `SET NX EX`)
+that are not available in general Flask-Caching backends.
 :::

-Each signal stream keeps only its latest entry and is given a TTL, so signal streams for tasks that
-are never awaited do not accumulate in Redis/Valkey. Set the retention window with
-`DISTRIBUTED_COORDINATION_SIGNAL_TTL` (seconds, default 24 hours):
-
-```python
-DISTRIBUTED_COORDINATION_SIGNAL_TTL = 24 * 60 * 60
-```
-
 ### Configuration

 The distributed coordination uses Flask-Caching style configuration for consistency with other cache
@@ -408,8 +345,9 @@ DISTRIBUTED_COORDINATION_CONFIG = {
 }
 ```

-By default, connections opened for `DISTRIBUTED_COORDINATION_CONFIG` have no socket
-timeout. This can be overridden with `CACHE_REDIS_SOCKET_TIMEOUT` and
+By default, connections opened for `DISTRIBUTED_COORDINATION_CONFIG` (as well as
+`GLOBAL_ASYNC_QUERIES_CACHE_BACKEND`, which uses the same `RedisCache`/`RedisSentinelCache`
+backend) have no socket timeout. This can be overridden with `CACHE_REDIS_SOCKET_TIMEOUT` and
 `CACHE_REDIS_SOCKET_CONNECT_TIMEOUT`, both in seconds:

 ```python
@@ -97,54 +97,6 @@ for more information on how to configure it.

 At the very least, you'll want to change `SECRET_KEY` and `SQLALCHEMY_DATABASE_URI`. Continue reading for more about each of these.

-## Localizing D3 date and time labels
-
-`BABEL_DEFAULT_LOCALE` controls Superset's application translations, while
-`D3_TIME_FORMAT` provides localized date and time names to visualizations that
-use the D3 formatter registry, including Calendar Heatmap. Configure both when
-you want the application and chart labels to use the same locale.
-
-`D3_TIME_FORMAT` accepts partial overrides. For example, Russian month names
-can be configured in `superset_config.py` as follows:
-
-```python
-BABEL_DEFAULT_LOCALE = "ru"
-
-D3_TIME_FORMAT = {
-    "months": [
-        "Январь",
-        "Февраль",
-        "Март",
-        "Апрель",
-        "Май",
-        "Июнь",
-        "Июль",
-        "Август",
-        "Сентябрь",
-        "Октябрь",
-        "Ноябрь",
-        "Декабрь",
-    ],
-    "shortMonths": [
-        "Янв",
-        "Фев",
-        "Мар",
-        "Апр",
-        "Май",
-        "Июн",
-        "Июл",
-        "Авг",
-        "Сен",
-        "Окт",
-        "Ноя",
-        "Дек",
-    ],
-}
-```
-
-Restart Superset after changing `superset_config.py` so the frontend receives
-the updated formatter configuration.
-
 ## Chart-data query timing

 Set `CHART_DATA_INCLUDE_TIMING = True` to add an optional versioned timing object
@@ -566,55 +518,6 @@ def FLASK_APP_MUTATOR(app: Flask) -> None:
    app.before_request_funcs.setdefault(None, []).append(make_session_permanent)
 ```

-## Carrying extra data through chart and dashboard exports
-
-Deployments often attach their own metadata to charts and dashboards — an owning
-team, a catalogue entry, a cost centre — and need it to survive an export/import
-round trip between environments. `EXTRA_ASSET_EXPORT_FIELDS` and
-`EXTRA_ASSET_IMPORT_HANDLER` let you do that without forking the export commands.
-
-The export hook receives the model and the asset type (`"chart"` or `"dashboard"`)
-and returns a mapping, which is serialised under the `extra` key of the asset's
-YAML. The import hook receives the model, the asset type and that same mapping,
-once the asset exists and has an id:
-
-```python
-# superset_config.py
-def _export_fields(model, asset_type):
-    return {"owning_team": lookup_team(model)}
-
-
-def _import_handler(model, asset_type, extra):
-    if team := extra.get("owning_team"):
-        assign_team(model, team)
-
-
-EXTRA_ASSET_EXPORT_FIELDS = _export_fields
-EXTRA_ASSET_IMPORT_HANDLER = _import_handler
-```
-
-The exported YAML then carries:
-
-```yaml
-slice_name: Revenue by region
-...
-extra:
-  owning_team: analytics-platform
-```
-
-A few things worth knowing:
-
- **Both hooks are optional and default to `None`.** With neither configured,
-exported files are byte-for-byte what they were before, and imports behave
-identically.
- **Everything lives under the single `extra` key.** The import schemas reject
-unknown top-level fields, so namespacing under `extra` keeps that strictness
-while leaving you free to change the shape of your own payload later.
- **An export hook returning `None` or an empty mapping writes nothing**, so
-assets without your metadata do not gain an empty `extra` block.
- **The import handler runs after the asset is created or updated**, which means
-you can rely on `model.id`. Raising from it will fail the import.
-
 ## Customizing the landing page (index view)

 The page served at `/` is rendered by an index view. By default Superset registers
@@ -1,184 +0,0 @@
---
-title: Dashboard Performance
-hide_title: true
-sidebar_position: 5
-version: 1
---
-
-<!--
-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
-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
-
-  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
-specific language governing permissions and limitations
-under the License.
-->
-
-# Dashboard Performance
-
-A dashboard's perceived speed is determined by three independent things: how
-many charts have to render, how many queries the backend can execute
-concurrently, and how quickly the underlying data warehouse can return
-results. Superset gives you levers for the first two; the third belongs to
-your warehouse. This page covers the dashboard-side levers and the practical
-guidance around them.
-
-## Is there a maximum chart count per dashboard?
-
-**No hard limit is enforced** — Superset has no configuration key that
-caps the number of charts on a dashboard. In practice, dashboards behave
-well up to a few dozen charts. Beyond that, you'll typically feel friction
-on the initial load and during cross-filter / time-range updates, even with
-the lazy-loading optimizations described below.
-
-Rough thresholds to keep in mind:
-
- **Under ~25 charts**: usually no perceptible problem.
- **25–50 charts**: still fine, but you start to want tabs to break the
-  page into chunks the user actually looks at.
- **Over ~50 charts**: split into multiple dashboards or use tabs
-  aggressively. The bottleneck is rarely Superset itself — it's the
-  warehouse executing dozens of queries in parallel and the browser
-  rendering dozens of chart frames.
-
-These are guidelines, not guarantees. A dashboard of 100 sparkline-style
-charts hitting a fast cache behaves very differently from a dashboard of
-20 heavy aggregations against a cold warehouse.
-
-## Lazy rendering — `DASHBOARD_VIRTUALIZATION`
-
-Superset's dashboard layout is virtualized at the row level. Charts that
-are far below the user's current scroll position render a placeholder
-instead of their visualization until the user scrolls them into view, and
-go back to a placeholder if scrolled well past. The chart component itself
-stays mounted throughout — only the visualization is swapped for a
-placeholder — so this alone does **not** reduce backend query load; see
-[Deferred data fetch](#deferred-data-fetch--dashboard_virtualization_defer_data)
-below for that. This is on by default.
-
-**Feature flag**: `DASHBOARD_VIRTUALIZATION` (default: `True`)
-
-The flag is `stable` and marked for path-to-deprecation — meaning the
-behavior will eventually be non-optional, but the flag still exists so
-operators can disable it if a specific layout misbehaves.
-
-**Behavior** (from `superset-frontend/src/dashboard/components/gridComponents/Row/Row.tsx`):
-
- A chart's visualization is rendered when its row scrolls within **1
-  viewport height** of the visible area.
- A chart's visualization is swapped back for a placeholder when its row
-  scrolls more than **4 viewport heights** away from the visible area.
- Tabs that aren't currently selected don't render their content at all
-  (see below).
- The placeholder-swap-back is skipped in **embedded** mode (so an
-  embedded dashboard keeps its charts rendered once they've been seen,
-  which avoids re-rendering on scroll-up). Both halves are skipped for
-  **headless / bot** rendering (so screenshot / report jobs load every
-  chart).
-
-## Deferred data fetch — `DASHBOARD_VIRTUALIZATION_DEFER_DATA`
-
-By default, `DASHBOARD_VIRTUALIZATION` only controls whether a chart's
-*visualization* is rendered — the chart component still mounts and issues
-its data request immediately, regardless of scroll position.
-`DASHBOARD_VIRTUALIZATION_DEFER_DATA` is a supplementary flag that skips
-the data request itself for charts that aren't currently in view, useful
-for backends where opening a connection or compiling a query is expensive
-even if the result would be thrown away. It only has an effect when
-`DASHBOARD_VIRTUALIZATION` is also enabled — with virtualization off,
-every chart is treated as in view, so there's nothing left to defer.
-
-**Feature flag**: `DASHBOARD_VIRTUALIZATION_DEFER_DATA` (default: `False`)
-
-Enable this if you see warehouse load spike on dashboard *open* even
-though most charts are off-screen.
-
-## Per-tab lazy loading
-
-**This is on by default and has no flag.** A tab's content is not rendered
-until the user activates that tab, so charts inside an unselected tab do
-not fetch data on dashboard open. When the user clicks the tab, that
-tab's charts mount and fetch in the normal way.
-
-Practically: tabs are the single most effective tool for a large
-dashboard. Splitting 60 charts across 4 tabs effectively turns dashboard
-open into "load ~15 charts," and the remaining ones lazy-load only if the
-user goes looking.
-
-## Is there a switch to cap concurrent chart queries?
-
-**No.** Superset does not implement a frontend-side concurrent-request
-limiter. Each chart issues its own data request when it mounts, and the
-browser handles parallelism — typically ~6 in-flight requests per origin
-under HTTP/1.1, though HTTP/2 or HTTP/3 (if your deployment terminates
-TLS that way) can multiplex considerably more over a single connection.
-Backend throughput is bounded by your
-Gunicorn worker count for synchronous query execution, or by your Celery
-worker pool when [async queries](./async-queries-celery.mdx) are enabled.
-
-If you need to throttle warehouse load, the right place is:
-
-1. The warehouse itself (connection pool / concurrency limits).
-2. Superset's Celery configuration (smaller worker pool when async
-   queries are on).
-3. Splitting heavy charts across tabs or separate dashboards (each
-   dashboard load only fetches what's visible).
-
-## Splitting strategies
-
-When a dashboard outgrows comfortable performance, the options in order
-of effort:
-
-**1. Move sections into tabs.** Same dashboard, but only the active tab's
-charts fetch. This is the cheapest change and often the only one needed.
-
-**2. Cache aggressively.** A Redis cache backend (see
-[Caching](./cache.mdx)) means repeat dashboard loads serve from cache
-rather than re-hitting the warehouse. This is especially impactful for
-dashboards opened by many users in close succession.
-
-**3. Enable async queries.** [Async query execution](./async-queries-celery.mdx)
-via Celery decouples query duration from request lifetime, so a slow
-chart doesn't block the page. The user sees other charts come in as
-their queries complete.
-
-**4. Split into multiple dashboards.** Group related charts into purpose-
-specific dashboards rather than one mega-dashboard. Link them from a
-landing dashboard or a navigation menu.
-
-**5. Pre-aggregate at the warehouse level.** If the same expensive
-aggregation appears across many charts, materialize it as a view or
-scheduled table in the warehouse so each chart query is a cheap lookup.
-
-## Operational notes
-
- The feature flags above are set in `superset_config.py`, e.g.:
-
-  ```python
-  FEATURE_FLAGS = {
-      "DASHBOARD_VIRTUALIZATION": True,
-      "DASHBOARD_VIRTUALIZATION_DEFER_DATA": True,
-  }
-  ```
-
- See [Feature Flags](./feature-flags.mdx) for the full list of supported
-  flags and their lifecycle stages.
- Server-side screenshot jobs (alerts, scheduled reports, thumbnails)
-  render the dashboard in a headless, webdriver-controlled browser, which
-  intentionally bypasses row virtualization so the rendered artifact
-  includes every chart, not just the ones above the fold. User-triggered
-  "download as image/PDF" is different: it captures whatever's currently
-  rendered in the user's own browser, so it's still subject to
-  virtualization like any other page view. Metadata/YAML dashboard export
-  doesn't render the frontend at all, so virtualization doesn't apply to
-  it either.
@@ -50,34 +50,13 @@ Superset can be configured to log events to [StatsD](https://github.com/statsd/s
 if desired. Most endpoints hit are logged as
 well as key events like query start and end in SQL Lab.

-Superset can also collect gunicorn [metrics](https://gunicorn.org/instrumentation/).
-To enable these, the following environment variables should be set:
-
-```bash
-SERVER_STATSD_HOST=localhost
-SERVER_STATSD_PORT=8125
-SERVER_STATSD_PREFIX=superset
-```
-
-To setup StatsD logging for Superset, it’s a matter of configuring the logger in your `superset_config.py`.
+To setup StatsD logging, it’s a matter of configuring the logger in your `superset_config.py`.
+If not already present, you need to ensure that the `statsd`-package is installed in Superset's python environment.

 ```python
-import os
 from superset.stats_logger import StatsdStatsLogger
-
-try:
-    STATSD_PORT = int(os.environ.get("SERVER_STATSD_PORT", "8125"))
-except ValueError:
-    STATSD_PORT = 8125
-
-STATS_LOGGER = StatsdStatsLogger(
-    host=os.environ.get("SERVER_STATSD_HOST", "localhost"),
-    port=STATSD_PORT,
-    prefix=os.environ.get("SERVER_STATSD_PREFIX", "superset"),
-)
+STATS_LOGGER = StatsdStatsLogger(host='localhost', port=8125, prefix='superset')
 ```

-[statsd](https://pypi.org/project/statsd/) in version ~3.3.0 must be installed.
-
 Note that it’s also possible to implement your own logger by deriving
 `superset.stats_logger.BaseStatsLogger`.
@@ -83,26 +83,6 @@ The optional username flag **-u** sets the user used for the datasource import.
 superset import_datasources -p <path / filename> -u 'admin'
 ```

-## Importing a Directory of Assets
-
-The `import_directory` command imports a directory of exported assets (databases, datasets,
-dashboards, charts) in the same layout produced by the ZIP-based export. Saved queries and tags
-included in a full export are not imported by this command:
-
-```bash
-superset import_directory <path / directory>
-```
-
-As with `import_datasources`, the optional username flag **-u** sets the user assigned as the
-owner of the imported assets. The default is 'admin'. Example:
-
-```bash
-superset import_directory <path / directory> -u 'admin'
-```
-
-If the specified user does not exist, the command fails immediately with an error rather than
-importing the assets without an owner.
-
 ## Dashboard Import Overwrite Behavior

 When importing a dashboard ZIP with the **overwrite** option enabled, any existing charts that are part of the dashboard are **replaced** rather than duplicated. This applies to:
@@ -253,58 +253,6 @@ def my_custom_auth_factory(app):
 MCP_AUTH_FACTORY = my_custom_auth_factory
 ```

-### Embedded Guest Authentication
-
-Superset's [embedded dashboards](/user-docs/using-superset/embedding) feature mints short-lived **guest tokens** for anonymous/embedded viewers. The MCP server can accept these same guest tokens, so an embedded guest (e.g. an in-app chatbot next to an embedded dashboard) can call MCP tools scoped to the dashboards/resources named in its token.
-
-This is opt-in and reuses the existing core guest-token configuration -- there is no MCP-specific guest secret or audience.
-
-```python
-# superset_config.py
-FEATURE_FLAGS = {"EMBEDDED_SUPERSET": True}   # required -- guest tokens only exist when this is on
-MCP_EMBEDDED_GUEST_AUTH_ENABLED = True        # opt-in for the MCP transport (default False)
-```
-
-Present the guest token the same way as any other bearer token:
-
-```bash
-curl -X POST http://localhost:5008/mcp \
-  -H 'Content-Type: application/json' \
-  -H 'Authorization: Bearer YOUR_GUEST_TOKEN' \
-  -d '{"jsonrpc": "2.0", "method": "tools/list", "id": 1}'
-```
-
-**How it works**
-
- A dedicated guest-token verifier validates the token against the same `GUEST_TOKEN_JWT_SECRET` / `GUEST_TOKEN_JWT_ALGO` / `GUEST_TOKEN_JWT_AUDIENCE` config used by embedded dashboards, replays the embedded structural checks, and enforces revocation (global version bumps and per-dashboard `guest_token_revoked_before` cutoffs). It runs *before* the JWT verifier described above, since guest tokens are signed with a different key/algorithm and would otherwise be rejected at the transport.
- A verified guest resolves to a Superset guest user as the highest-priority identity, so it's never downgraded to API-key / `MCP_DEV_USERNAME` / dev-mode resolution. Data access is scoped by the same checks (dataset allowlist, dashboard access, row-level security) that apply to embedded dashboard views.
- Guests are restricted to a default-deny allow-list, `MCP_GUEST_ALLOWED_TOOLS`, regardless of `MCP_RBAC_ENABLED`. Sensitive enumeration tools like `find_users` and `get_instance_info` are denied simply by being absent from the default list.
- Setting `MCP_AUTH_FACTORY` bypasses this whole path: a configured factory is tried first, and the default factory that wires up the guest-token verifier is never reached. If you rely on a custom auth factory (e.g. your own OIDC provider) alongside guest auth, that factory must verify guest tokens itself -- otherwise they're rejected regardless of `MCP_EMBEDDED_GUEST_AUTH_ENABLED`.
-
-```python
-# superset_config.py
-MCP_GUEST_ALLOWED_TOOLS = {
-    "get_dashboard_info",
-    "get_dashboard_layout",
-    "list_dashboards",
-    "list_charts",
-    "get_chart_info",
-    "get_chart_data",
-    "get_chart_preview",
-}  # default
-```
-
-**Deployment requirements**
-
- The MCP server and the service that mints guest tokens (the Superset web app) must share `GUEST_TOKEN_JWT_SECRET` and `GUEST_TOKEN_JWT_AUDIENCE`. Set `GUEST_TOKEN_JWT_AUDIENCE` explicitly -- if it's unset, audience validation falls back to the URL host, which can differ between the two services and cause every guest token to fail validation.
- The `GUEST_ROLE_NAME` role (default `Public`) must exist -- a guest token is rejected if it does not.
- Don't set `MCP_DEV_USERNAME` on a deployment that also serves embedded guests.
- Restart the MCP process after toggling `EMBEDDED_SUPERSET` or `MCP_EMBEDDED_GUEST_AUTH_ENABLED` -- guest auth is wired up once at startup.
-
-:::warning
-`GUEST_TOKEN_JWT_SECRET` guards both the web embedding and MCP guest-auth surfaces. With `MCP_EMBEDDED_GUEST_AUTH_ENABLED` on, leaving it at its insecure default isn't just a forgery risk -- the MCP server refuses to start (`MCPAuthConfigError`) until you set a real secret shared with the guest-token minting service.
-:::
-
 ---

 ## Connecting AI Clients
@@ -557,8 +505,6 @@ All MCP settings go in `superset_config.py`. Defaults are defined in `superset/m
 | `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). |
-| `MCP_DISABLED_CHART_PLUGINS` | `frozenset()` | Set of chart type plugin names (e.g. `"handlebars"`) to hide from `generate_chart`. Does not affect `get_chart_type_schema`. See [Disabling chart type plugins](#disabling-chart-type-plugins). |
-| `MCP_CHART_PLUGIN_ENABLED_FUNC` | `None`        | Callable `(chart_type: str) -> bool` evaluated per registry lookup for dynamic enable/disable decisions. Takes precedence over `MCP_DISABLED_CHART_PLUGINS` when set. See [Disabling chart type plugins](#disabling-chart-type-plugins). |

 ### Authentication

@@ -575,8 +521,6 @@ All MCP settings go in `superset_config.py`. Defaults are defined in `superset/m
 | `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. |
-| `MCP_EMBEDDED_GUEST_AUTH_ENABLED` | `False` | Accept embedded [guest tokens](#embedded-guest-authentication) as Bearer auth. Also requires the `EMBEDDED_SUPERSET` feature flag. |
-| `MCP_GUEST_ALLOWED_TOOLS` | see [default list](#embedded-guest-authentication) | The only tool names callable by embedded guests (default-deny), regardless of `MCP_RBAC_ENABLED`. |

 ### Response Size Guard

@@ -632,7 +576,7 @@ MCP_CACHE_CONFIG = {
 | Key                  | Default   | Description                                                 |
 | -------------------- | --------- | ----------------------------------------------------------- |
 | `enabled`            | `False`   | Enable response caching                                     |
-| `CACHE_KEY_PREFIX`   | `None`    | Base prefix for shared Redis; Superset appends an internal response-contract namespace |
+| `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`                                |
@@ -774,34 +718,6 @@ Every MCP request passes through a middleware stack before reaching the tool fun

 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.

-### Tool Result Value Contract
-
-Structured tool results preserve Superset domain values exactly. In particular,
-string fields are not wrapped in trust delimiters, and text that resembles a
-delimiter is returned as literal application data. This lets clients safely use a
-read result as the basis for an update without persisting presentation markup.
-
-All tool-result content should still be treated as user-controlled data with no
-instruction authority. MCP clients should communicate that trust boundary through
-their model instructions or presentation layer, outside the returned field values;
-fixed or generated marker strings inside a value are ambiguous and must not be used
-as a trust signal.
-
-For compatibility, clients that supported the former
-`<UNTRUSTED-CONTENT>` convention should stop recognizing or stripping those strings.
-The response schemas and content types have not changed. Because marker-looking text
-can be legitimate application data, a client cannot reliably distinguish a legacy
-decorated response from a clean one. Pause automated read-modify-write workflows, or
-route them only to upgraded instances, until every serving instance is upgraded.
-
-Redis-backed MCP response caches include an internal response-contract namespace, so
-an upgraded instance does not reuse responses cached by an older release. Older
-instances can still return legacy values while they remain in service. After the
-upgrade, review previously written values for wrapper text and both
-`[ESCAPED-UNTRUSTED-CONTENT-OPEN]` and
-`[ESCAPED-UNTRUSTED-CONTENT-CLOSE]`; do not remove these strings automatically,
-because they may be intentional content.
-
 ### Error Sanitization

 The `GlobalErrorHandlerMiddleware` automatically redacts sensitive information from all error messages before they reach the LLM client. The following are replaced with generic messages:
@@ -836,20 +752,11 @@ For a 3-pod Kubernetes deployment with the defaults above, expect up to 3 × (5
 Enable response caching for read-heavy workloads (dashboards/datasets that don't change frequently). With the in-memory backend (default when `MCP_STORE_CONFIG` is disabled), caching is per-process. Use Redis-backed caching for consistent cache hits across multiple pods:

 ```python
-MCP_CACHE_CONFIG = {
-    "enabled": True,
-    # Cache keys don't include the requesting principal and hits are served
-    # ahead of auth/RBAC, so a shared cache can return one caller's response
-    # to another. Required for caching to actually start -- only appropriate
-    # when every request is guaranteed to come from the same principal.
-    "dangerously_share_cache_across_principals": True,
-    "CACHE_KEY_PREFIX": "mcp_cache_",
-    "call_tool_ttl": 3600,
-}
+MCP_CACHE_CONFIG = {"enabled": True, "call_tool_ttl": 3600}
 MCP_STORE_CONFIG = {"enabled": True, "CACHE_REDIS_URL": "redis://redis:6379/0"}
 ```

-Every tool with a side effect (create/update/delete/execute) is always excluded from caching regardless of this setting -- see the `excluded_tools` default in `superset/mcp_service/mcp_config.py` for the current list.
+Mutating tools (`generate_chart`, `update_chart`, `execute_sql`, `generate_dashboard`) are always excluded from caching regardless of this setting.

 ---

@@ -949,39 +856,6 @@ MCP_DISABLED_TOOLS = {"extensions.myorg.myextension.some_tool"}
 Specifying a tool name that does not exist logs a warning at startup and is otherwise ignored — it will not prevent the server from starting.
 :::

-## Disabling chart type plugins
-
-The `generate_chart` tool dispatches per chart type (`xy`, `table`, `pie`, `pivot_table`, `mixed_timeseries`, `handlebars`, `big_number`, `histogram`, `box_plot`, `waterfall`) to a registered chart type plugin. Two settings let operators enable or disable individual chart type plugins at runtime, without a code deploy.
-
-### Static deny-list
-
-Set `MCP_DISABLED_CHART_PLUGINS` in your `superset_config.py` to a set of chart type names:
-
-```python
-# superset_config.py
-
-# Emergency kill switch: hide "handlebars" from all callers
-MCP_DISABLED_CHART_PLUGINS = {"handlebars"}
-```
-
-Disabled chart types stay registered but are filtered out at lookup time: they're never listed in `generate_chart`'s supported chart types, and `generate_chart` calls for them are rejected. `get_chart_type_schema` consults its own static schema/example map rather than the registry filter, so a disabled chart type's schema remains queryable through that tool even though `generate_chart` will reject it.
-
-### Dynamic predicate
-
-For per-request control (A/B tests, gradual rollout, entitlement checks), set `MCP_CHART_PLUGIN_ENABLED_FUNC` to a callable. It's evaluated as `enabled_func(chart_type: str) -> bool` on every registry lookup, and it takes precedence over `MCP_DISABLED_CHART_PLUGINS` when set:
-
-```python
-# superset_config.py
-from flask import g
-
-
-def MCP_CHART_PLUGIN_ENABLED_FUNC(chart_type: str) -> bool:
-    flags = getattr(g, "feature_flags", {})
-    return flags.get(f"mcp_chart_{chart_type}", True)
-```
-
-The callable must be cheap and in-process (consult already-loaded feature flags or request-local context) -- do not perform network I/O per call. If it raises, the registry fails closed (the plugin is hidden) and logs a warning.
-
 ## Security Best Practices

 - **Use TLS** for all production MCP endpoints -- place the server behind a reverse proxy with HTTPS
@@ -88,27 +88,6 @@ THEME_DARK = {
 # - OS preference detection is automatically enabled
 ```

-### Default Theme Mode
-
-By default, Superset mimics the visitor's OS/browser preference (light or dark) for
-sessions that don't have a saved user preference. Use `THEME_DEFAULT_MODE` to override
-that starting point instance-wide for the standard application:
-
-```python
-# Default theme mode for sessions without a saved user preference.
-# One of "default" (always light), "dark" (always dark), or "system" (mimic OS preference).
-THEME_DEFAULT_MODE = "dark"
-```
-
- `"system"` (the default) preserves the existing behavior of following the OS/browser
-  preference, provided a dark theme is configured (`THEME_DARK` is not `None`). If no dark
-  theme is available, Superset always starts in light mode regardless of this setting.
- `"default"` or `"dark"` forces that starting mode for first-time visitors; users can still switch themes manually afterward if both `THEME_DEFAULT` and `THEME_DARK` are available.
- A user's own saved preference, once they toggle the theme switcher, always takes precedence over `THEME_DEFAULT_MODE`.
- `THEME_DEFAULT_MODE` has no effect on embedded dashboards: the embed SDK sets the
-  starting mode via its own `themeMode` URL parameter, which takes precedence and falls
-  back to light mode when the parameter is absent.
-
 ### App Branding

 The application name shown in the browser title bar and navigation can be
@@ -240,39 +219,6 @@ Font URLs are validated against a configurable allowlist. By default, fonts from

 This feature works with the stock Docker image - no custom build required!

-## Results Grid Configuration Overrides
-
-Superset exposes a handful of opt-in tokens that customize the appearance of
-the results grid in SQL Lab. These tokens have no effect unless explicitly
-set, since the results grid otherwise falls back to its built-in defaults.
-
-```python
-THEME_DEFAULT = {
-    "token": {
-        "colorPrimary": "#2893B3",
-        # ... other Ant Design tokens
-
-        # Results grid overrides
-        "resultsGridRowHeight": 32,
-        "resultsGridHeaderFontSize": 13,
-        "resultsGridHeaderFontWeight": 600,
-        "resultsGridBorderRadius": 4,
-        "resultsGridNoStriping": True,
-    }
-}
-```
-
-| Token | Type | Description |
-| --- | --- | --- |
-| `resultsGridRowHeight` | `number` | Row and header height, in pixels. |
-| `resultsGridHeaderFontSize` | `number` | Header cell font size, in pixels. |
-| `resultsGridHeaderFontWeight` | `number` | Header cell font weight. |
-| `resultsGridBorderRadius` | `number` | Border radius applied to the grid and its wrapper, in pixels. |
-| `resultsGridNoStriping` | `boolean` | When `true`, disables alternating row background striping. |
-
-These tokens can also be set through the theme CRUD interface's JSON editor,
-alongside any other Superset-specific tokens.
-
 ## ECharts Configuration Overrides

 :::note
@@ -183,14 +183,13 @@ https://superset.apache.org/admin-docs/configuration/configuring-superset/#rotat
 | --------------------------------- | ------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------- | ----------------------------------------- |
 | `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                 |
-| `WEBSOCKET_JWT_SECRET`            | Signs the realtime websocket channel JWT cookie                                       | Forged websocket tokens → unauthorized realtime notifications                                       | 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:

- Rotating `GUEST_TOKEN_JWT_SECRET` or `WEBSOCKET_JWT_SECRET` invalidates outstanding tokens of that type; schedule rotations accordingly.
- `WEBSOCKET_JWT_SECRET` can be rotated without disconnecting live sockets: set the outgoing value as `PREVIOUS_JWT_SECRET` on the websocket server so it keeps verifying old cookies, then remove it once they have aged out.
+- Rotating `GUEST_TOKEN_JWT_SECRET` or `GLOBAL_ASYNC_QUERIES_JWT_SECRET` invalidates outstanding tokens of that type; schedule rotations accordingly.
 - After a suspected compromise, rotate **all** of the above, not only `SUPERSET_SECRET_KEY`.
 - Keep the register under change control so new secrets introduced by future features are added to the rotation schedule.

@@ -243,42 +243,6 @@ Each subject in the response includes flat scalar ids (`user_id`, `role_id`, `gr
 than a nested object, so callers can match directly on whichever id they already have — only the
 id field matching the subject's `type` is populated; the others are `null`.

-#### Extending Editorship with EXTRA_EDITORS_RESOLVER
-
-Deployments that grant edit access to a dashboard or chart through a mechanism outside
-Superset's own Subject-based `editors` list — for example, a folder-permission system or an
-internal directory service — can plug that logic in with `EXTRA_EDITORS_RESOLVER`:
-
-```python
-def extra_editors_resolver(resource):
-    # `resource` is the Dashboard or Slice instance being checked.
-    # Return Subject instances, raw subject ids, or dicts with an `id` key.
-    return [...]
-
-
-EXTRA_EDITORS_RESOLVER = extra_editors_resolver
-```
-
-The resolver's result is unioned with the resource's own `editors` for editorship checks: it
-feeds `is_editor`, `raise_for_editorship`, save-as, and soft-delete restore. When
-`EXTRA_EDITORS_RESOLVER` is configured, the usual lockout-prevention behavior — automatically
-re-adding a non-admin who removes themselves from a resource's editors — is skipped, since the
-deployment has its own way of keeping the resource editable. This skip is global to the setting,
-not per-resource: it still applies on a resource where the resolver currently returns no
-subjects, so a resolver that can't guarantee an alternate editor for every resource can let the
-last editor remove themselves and leave it uneditable by non-admins.
-
-Resolved subject ids are also surfaced as `extra_editors` in the chart and dashboard `GET`
-responses, so API clients can distinguish resolver-granted editorship from the resource's own
-`editors` list. This field is attached after serialization and isn't part of the OpenAPI response
-schema, so generated API clients won't see it as a typed field.
-
-Because the resolver is arbitrary per-deployment Python rather than a SQL-expressible condition,
-editorship it grants cannot be reflected in list-view filtering (for example, the soft-deleted
-archive is scoped to editors via a SQL query). It does still run once per row on chart and
-dashboard list responses to populate `extra_editors`, so a slow or unavailable external resolver
-affects ordinary list requests, not just direct per-object checks.
-
 ### Dashboard Access Control

 Access to dashboards is managed via editors (subjects that have edit permissions to the dashboard).
@@ -436,7 +400,7 @@ Once enabled, each user manages their own keys from their profile page:
 1. Open the user menu (top-right) and click **Info** to navigate to the User Info page
 2. Expand the **API Keys** section
 3. Click **+ API Key**
-4. Enter a name and optionally select resource scopes
+4. Enter a name and (optionally) an expiration date
 5. Copy the generated token — it is shown only once

 Only users with the `can_read` and `can_write` permissions on `ApiKey` (granted by default to Admins) can manage API keys.
@@ -451,18 +415,6 @@ Authorization: Bearer <your-api-key>

 This works for all REST API endpoints and the MCP server. The request is executed with the permissions of the user who created the key.

-#### API Key Scopes
-
-The creation dialog can restrict an API key to MCP resource actions such as
-`superset:dashboard:read` or `superset:chart:write`. A scope is an additional
-restriction: it never grants a permission that the creating user does not
-already have through Superset RBAC. Write scopes also cover update and delete
-operations for that resource; `superset:sqllab:write` covers SQL execution.
-
-Keys created without scopes retain legacy RBAC-only behavior. The scoped-key
-restrictions described here are enforced by the MCP server; regular REST API
-routes continue to apply their existing Superset RBAC checks.
-
 #### Use Cases

 - **CI/CD pipelines** — automated chart/dashboard exports and imports
@@ -619,28 +571,6 @@ SELECT * FROM (
  queries run against tables that have associated datasets with RLS filters will then have
  the appropriate predicates injected automatically.

-#### RLS Indicator in the Dataset List and Explore
-
-When a dataset has one or more RLS filters that apply to it, Superset shows a lock
-icon badge next to the dataset name in the **Datasets** list and next to the dataset
-selector in **Explore**. Hovering over the badge shows a tooltip listing each
-applicable filter's name, filter type (Regular or Base), group key (if any), assigned
-subjects (labeled "Roles" in the tooltip, but may include users and groups too), and
-clause.
-
-This badge also surfaces filters that are inherited from the physical tables
-referenced by a virtual (SQL-based) dataset, as described above. Inherited filters
-are marked "from underlying table" in the tooltip, and a summary note is shown
-whenever any of the listed filters are inherited rather than assigned directly to
-the dataset. Inherited-filter detection depends on Superset's SQL parser being able
-to identify the referenced tables and match them to a physical dataset by name,
-schema, and database, so it's best-effort: unparseable or unmatched references won't
-surface a filter on the badge even if one would apply at query time.
-
-The badge is a visibility aid only — it does not change which filters are applied to
-a query. Use the RLS REST API described below if you need to confirm exactly which
-filters affect a dataset.
-
 #### Checking RLS Filters via the API

 You can use the RLS REST API to audit which filters are configured and which datasets
@@ -86,7 +86,6 @@
    "Israel",
    "Italy",
    "Italy (regions)",
-    "Italy (regions and autonomous provinces)",
    "Ivory Coast",
    "Japan",
    "Jordan",
@@ -570,6 +570,15 @@ curl -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \

 </details>

+<details>
+<summary><strong>AsyncEventsRestApi</strong> (1 endpoints) — Real-time event streaming via Server-Sent Events (SSE).</summary>
+
+| Method | Endpoint | Description |
+|--------|----------|-------------|
+| `GET` | [Read off of the Redis events stream](/developer-docs/api/read-off-of-the-redis-events-stream) | `/api/v1/async_event/` |
+
+</details>
+
 <details>
 <summary><strong>OpenApi</strong> (1 endpoints) — Access the OpenAPI specification.</summary>

@@ -493,8 +493,8 @@ Frontend assets (TypeScript, JavaScript, CSS, and images) must be compiled in or

 First, be sure you are using the following versions of Node.js and npm:

- `Node.js`: Version 24 (see `superset-frontend/.nvmrc` for the exact version)
- `npm`: Version 11
+- `Node.js`: Version 22 (LTS)
+- `npm`: Version 10

 We recommend using [nvm](https://github.com/nvm-sh/nvm) to manage your node environment:

@@ -507,8 +507,8 @@ export NVM_DIR="$HOME/.nvm"
 [ -s "$NVM_DIR/bash_completion" ] && \. "$NVM_DIR/bash_completion"  # This loads nvm bash_completion

 cd superset-frontend
-nvm install
-nvm use
+nvm install --lts
+nvm use --lts
 ```

 Or if you use the default macOS starting with Catalina shell `zsh`, try:
@@ -519,30 +519,6 @@ sh -c "$(curl -fsSL https://raw.githubusercontent.com/nvm-sh/nvm/v0.37.0/install

 For those interested, you may also try out [avn](https://github.com/nvm-sh/nvm#deeper-shell-integration) to automatically switch to the node version that is required to run Superset frontend.

-##### zstd
-
-`npm run dev-server` proxies requests to your local Superset server and rewrites the HTML it returns, so it has to decompress responses sent with `Content-Encoding: zstd`. It does that with [`simple-zstd`](https://www.npmjs.com/package/simple-zstd), which wraps the system `zstd` binary instead of bundling one. That binary has to be on your `PATH`:
-
-```bash
-# macOS
-brew install zstd
-
-# Ubuntu/Debian
-sudo apt install zstd
-
-# Windows
-choco install zstd
-```
-
-`simple-zstd` looks for the binary when it is first imported, not when a response is decompressed, so a missing `zstd` stops the dev server at startup with:
-
-```
-Error: Can not access zstd! Is it installed?
-    at Object.<anonymous> (.../node_modules/simple-zstd/dist/src/index.js:102:11)
-```
-
-The message names the dependency, but it surfaces from inside `webpack.proxy-config.js` while the webpack config is loading, which reads like a build-tooling failure rather than a missing system package.
-
 #### Install dependencies

 Install third-party dependencies listed in `package.json` via:
@@ -114,8 +114,8 @@ function MyExtension() {

 ## Source Links

- [Story file](https://github.com/apache/superset/blob/master/superset-frontend/packages/superset-core/src/components/Alert/Alert.stories.tsx)
- [Component source](https://github.com/apache/superset/blob/master/superset-frontend/packages/superset-core/src/components/Alert/index.tsx)
+- [Story file](https://github.com/apache/superset/blob/master/superset-frontend/packages/superset-core/src/ui/components/Alert/Alert.stories.tsx)
+- [Component source](https://github.com/apache/superset/blob/master/superset-frontend/packages/superset-core/src/ui/components/Alert/index.tsx)

 ---

@@ -47,8 +47,8 @@ export function MyExtensionPanel() {

 Components in `@apache-superset/core/components` are automatically documented here. To add a new extension component:

-1. Add the component to `superset-frontend/packages/superset-core/src/components/`
-2. Export it from `superset-frontend/packages/superset-core/src/components/index.ts`
+1. Add the component to `superset-frontend/packages/superset-core/src/ui/components/`
+2. Export it from `superset-frontend/packages/superset-core/src/ui/components/index.ts`
 3. Create a Storybook story with an `Interactive` export:

 ```tsx
@@ -107,7 +107,7 @@ PENDING ──→ IN_PROGRESS ────→ SUCCESS
 | `IN_PROGRESS` | Executing                                            |
 | `ABORTING`    | Abort/timeout triggered, abort handlers running      |
 | `SUCCESS`     | Completed successfully                               |
-| `FAILURE`     | Failed with error, abort/cleanup handler exception, orphan reaping, or worker self-fence |
+| `FAILURE`     | Failed with error or abort/cleanup handler exception |
 | `ABORTED`     | Cancelled by user/admin                              |
 | `TIMED_OUT`   | Exceeded configured timeout                          |

@@ -152,57 +152,10 @@ Use the tuple format `(current, total)` whenever possible. It provides the riche

 #### Payload

-The `payload` parameter stores custom metadata that can help users understand what the task is doing. Each call to `update_task()` merges into the existing payload (top-level keys are added or overwritten; keys you don't pass are preserved), so a task can build up its payload incrementally across calls.
+The `payload` parameter stores custom metadata that can help users understand what the task is doing. Each call to `update_task()` replaces the previous payload completely.

 In the Task List UI, when a payload is defined, an info icon appears in the **Details** column. Users can hover over it to see the JSON content.

-#### Forcing an Immediate Write
-
-By default `update_task()` throttles database writes (batching frequent updates to limit metastore load, at most one write per `TASK_PROGRESS_UPDATE_THROTTLE_INTERVAL` seconds, default 2). Pass `immediate=True` to bypass throttling and write synchronously:
-
-```python
-ctx.update_task(payload={"result_cache_key": key}, immediate=True)
-```
-
-Use this only when another consumer must observe the update as soon as the task finishes — for example, a dependent task that reads a prerequisite's payload the moment the dependency gate releases. For ordinary progress reporting, prefer the default throttled behavior.
-
-#### Task state: public properties, private state, and results
-
-A task's state lives in three tiers:
-
-1. **Public `properties`** — named runtime state and execution config
-   (`is_abortable`, `progress_*`, `dedupe_count`, `execution_mode`, `timeout`,
-   `error_message`). Returned by the Task REST API and shown in the Task List UI.
-2. **Private properties** — internal state that is surfaced to API consumers
-   **only in debug mode** (otherwise the whole `private` key is stripped). It has
-   two structurally isolated namespaces so a task type's freeform key can never
-   collide with a framework key:
-   - `private.framework` — framework-owned named keys common to every task: the
-     Celery job id the orphan reaper revokes (`celery_task_id`) plus error debug
-     (`exception_type`, `stack_trace`). Written only by the framework via
-     `task.update_framework_private({...})`.
-   - `private.task` — freeform, task-type-specific internal handles (e.g. the
-     chart-data query task's engine cancel handle,
-     `cancel_query_id`/`cancel_database_id`). Written by task/execution code via
-     `task.update_task_private({...})`.
-   - `private.subscription` — a
-     [subscription policy](#per-client-subscriptions-subscription-policies)'s
-     per-client bookkeeping (e.g. chart-data's per-tab consumer list). Written
-     only from the policy hooks via `TaskDAO.merge_subscription_state(task, {...})`;
-     the executor never writes it, and its whole-blob property writes carry the
-     row's current value through instead of overwriting it.
-   All namespaces merge independently (a write to one never clobbers another).
-3. **Results (`payload`)** — end-user-facing task output (intermediate/final):
-   e.g. a `cache_key` or an engine tracking URL. Set via
-   `ctx.update_task(payload=...)` and rendered in the Task List info bubble. In
-   debug mode the bubble shows the `private` state in a separate section below.
-
-Rule of thumb: user-facing status → top-level `properties`; user-facing output →
-`payload`; framework plumbing → `private.framework`; task-specific internal
-handles → `private.task`; subscription-policy bookkeeping →
-`private.subscription`.
-
-
 ### Handlers

 Register handlers to run cleanup logic or respond to abort requests:
@@ -291,64 +244,6 @@ The framework automatically skips execution if a task was aborted while pending:
 Always implement an abort handler for long-running tasks. This allows users to cancel unneeded tasks and free up worker capacity for other operations.
 :::

-### Per-client subscriptions (subscription policies)
-
-The framework subscribes tasks at **principal grain**: one subscriber row per
-authenticated user (or embedded guest). The abort-vs-unsubscribe decision above
-counts principals. For most task types that is exactly right.
-
-Some task types need a finer grain than the principal. The canonical case is
-async chart-data: a single `SHARED` task is deduplicated across every request
-for the same query, so one user viewing the same chart in **two browser tabs** is
-a single principal with a single subscriber row. If either tab's cancel (an
-explicit cancel, or the navigate-away teardown) were treated as *the* principal
-leaving, it would abort the shared task and kill the other tab's still-pending
-query.
-
-A **subscription policy** lets a task type refine this without the framework
-knowing anything about tabs (or any other per-client grain). Register one on the
-`@task` decorator:
-
-```python
-from superset_core.tasks.subscription import TaskSubscriptionPolicy
-
-class MyConsumerPolicy(TaskSubscriptionPolicy):
-    def on_subscribe(self, task, *, principal, client_ref):
-        # Record this client (e.g. append f"{principal}:{client_ref}" to a list
-        # via TaskDAO.merge_subscription_state(task, {...})). Called after the
-        # framework has ensured the principal's subscriber row.
-        ...
-
-    def on_unsubscribe(self, task, *, principal, client_ref) -> bool:
-        # Drop this client. Return True if the principal now has no client left
-        # (the framework then proceeds with its normal principal-grain rule:
-        # unsubscribe the principal, and abort if it was the last subscriber);
-        # return False to keep the principal subscribed because another of its
-        # clients is still watching.
-        ...
-
-@task(name="my_task", scope=TaskScope.SHARED, subscription_policy=MyConsumerPolicy())
-def my_task() -> None:
-    ...
-```
-
-Both hooks run in the web request process, inside the lock that serializes
-concurrent submit/cancel for the task, so an implementation can safely
-read-modify-write its bookkeeping without extra locking against other
-submits/cancels. Keep that bookkeeping under `private.subscription` and write it
-with `TaskDAO.merge_subscription_state(task, {...})`: the executor does not hold
-the submit/cancel lock and keeps writing the task's properties while it runs, so
-the helper merges under a row lock and the executor's own writes preserve that
-namespace, where a plain `task.update_task_private({...})` would be overwritten
-by the executor's next write and silently drop a client that joined
-mid-execution. `client_ref` is the caller's
-opaque per-client id (for chart-data, the browser tab id sent as `tab_id` on the
-request); it is **not** an authorization token — the framework authorizes the
-calling principal before the policy runs, and the policy only ever records or
-removes entries scoped to that principal. A task type with no policy, or a
-request with no `client_ref`, keeps plain principal-grain behavior. An admin
-**Force abort** always aborts, bypassing the policy.
-
 ## Timeouts

 Set a timeout to automatically abort tasks that run too long:
@@ -438,48 +333,6 @@ assert task.uuid == task2.uuid  # True
 print(task2.status)  # "success" (terminal status)
 ```

-## Task Dependencies
-
-Tasks can declare prerequisite tasks, forming a directed acyclic graph (DAG). Pass the prerequisite `Task` objects (returned by `.schedule()`) via `depends_on`:
-
-```python
-from superset_core.tasks.types import TaskOptions
-
-totals = totals_task.schedule(options=TaskOptions(task_key="totals_123"))
-
-# `dependent` only runs once `totals` has finished successfully.
-dependent = dependent_task.schedule(
-    options=TaskOptions(depends_on=[totals])
-)
-```
-
-Passing the `Task` object is the canonical pattern. For convenience, a prerequisite's `UUID` (or UUID string) is also accepted where you don't hold the `Task` itself.
-
-**Semantics (`all_success`).** A task runs only once **every** direct prerequisite has reached a terminal `SUCCESS`. If **any** prerequisite ends in a non-`SUCCESS` terminal state (`FAILURE`, `ABORTED`, or `TIMED_OUT`), the dependent does **not** run and is transitioned to `FAILURE`. This propagates transitively: because a failed dependent is itself non-`SUCCESS`, its own dependents fail in turn, so a failure anywhere short-circuits everything downstream.
-
-**Scheduling model (non-blocking defer).** All tasks in a DAG are enqueued immediately. When a dependent is dequeued before its prerequisites are terminal, it does **not** hold its worker slot: it is re-enqueued via a Celery retry with a short, growing backoff (roughly 1s, 3s, 5s… capped) and the worker moves on to other work. While waiting, the task remains `PENDING` (shown as "waiting on N prerequisites" in the Task List). Each defer emits the `gtf.task.dag_deferred` metric.
-
-:::note
-A deferred dependent carries no heartbeat and no Celery job id until it is actually claimed (its prerequisites met), so the orphan reaper never mistakes a waiting task for abandoned work.
-:::
-
-Cycles (including self-dependencies) are rejected at schedule time. Dependency edges are removed automatically when either endpoint task is pruned.
-
-**Reading a prerequisite's output.** A dependent reads the payloads its prerequisites published via `ctx.get_dependency_payloads()`, which returns the prerequisites' payloads in dependency-edge order. Pair it with the prerequisite writing its result with `ctx.update_task(payload=..., immediate=True)` so the value is flushed (not held in the write-throttle buffer) by the time the dependency gate releases the dependent:
-
-```python
-@task
-def totals_task() -> None:
-    ctx = get_context()
-    # immediate=True so the dependent observes this the moment the gate releases.
-    ctx.update_task(payload={"result_cache_key": key}, immediate=True)
-
-@task
-def dependent_task() -> None:
-    ctx = get_context()
-    upstream = ctx.get_dependency_payloads()  # [{"result_cache_key": ...}, ...]
-```
-
 ## Task Scopes

 ```python
@@ -502,10 +355,6 @@ def system_task(): ...
 | `SHARED`  | All subscribers | Last subscriber cancels; others unsubscribe |
 | `SYSTEM`  | Admins only     | Admin cancels                               |

-For `SHARED` tasks, "last subscriber" is at principal grain by default; a task
-type can refine cancel to a finer per-client (e.g. per browser tab) grain with a
-[subscription policy](#per-client-subscriptions-subscription-policies).
-
 ## Task Cleanup

 Completed tasks accumulate in the database over time. Configure a scheduled prune job to automatically remove old tasks:
@@ -526,32 +375,8 @@ The prune job only removes tasks in terminal states (`SUCCESS`, `FAILURE`, `ABOR

 See `superset/config.py` for a complete example configuration.

-### Orphan Reaping
-
-A task whose worker dies mid-execution (OOM kill, crash, lost broker message) would otherwise stay `IN_PROGRESS` forever. To prevent this, a worker writes a liveness heartbeat while it holds a task, and a dedicated `reap_orphaned_tasks` beat job reaps orphans:
-
- **Heartbeat** — every `GTF_TASK_HEARTBEAT_INTERVAL` seconds (default 15) the executing worker refreshes `tasks.last_heartbeat`. This write is deliberately out-of-band and does not update `changed_on`.
- **Reaping** — `reap_orphaned_tasks` marks any active task whose heartbeat is older than `GTF_ORPHAN_TASK_TIMEOUT` (default 60) as `FAILURE` so waiters and dependents unblock, revokes its Celery job so a redelivered copy (with `task_acks_late`) will not run, and — on engines that support query cancellation, when the dead worker had captured a cancel handle — cancels the abandoned warehouse query out-of-band. A task still being worked on keeps a fresh heartbeat and is never reaped, so this never interferes with a live worker's cooperative abort/cleanup.
- **Self-fencing** — the reaper handles a *dead* worker, but a worker that is alive yet cut off from the metastore (network partition, metastore outage) would keep running a query the reaper has already marked `FAILURE`. To avoid that wasted work, if a worker's heartbeat writes keep failing for longer than `GTF_ORPHAN_TASK_TIMEOUT` — the same window the reaper uses — the worker fails the task from the inside, cancelling any in-flight query. A single failed write is tolerated; only a sustained outage spanning the orphan window fences, so a transient blip never kills a healthy task. There is no handover to another worker: the task simply fails.
-
-Enable the `reap_orphaned_tasks` beat schedule on a short interval (e.g. every minute) so orphaned tasks — and their warehouse queries — do not linger; it is separate from `prune_tasks` (a heavier retention delete that runs infrequently). Keep `GTF_ORPHAN_TASK_TIMEOUT` comfortably larger than the heartbeat interval (≥ ~3×) so a brief pause or CPU-bound stretch is not mistaken for a dead worker.
-
-```python
-# In your superset_config.py, add to your Celery beat schedule:
-CELERY_CONFIG.beat_schedule["reap_orphaned_tasks"] = {
-    "task": "reap_orphaned_tasks",
-    "schedule": crontab(minute="*", hour="*"),  # Run every minute
-}
-```
-
-Unlike `prune_tasks`, the reaper takes no kwargs — it reads `GTF_ORPHAN_TASK_TIMEOUT` from config.
-
-:::note Cancelling the underlying query
-For long-running work backed by an external query, register an `on_abort` handler that cancels it (this is how async chart-data query tasks cancel the warehouse query on engines that support cancellation). Without such a handler an abort/timeout frees the task but cannot stop the external work.
-:::
-
 :::tip Distributed Coordination for Faster Notifications
-By default, abort detection and sync join-and-wait poll the task row in the metadata database (every `TASK_ABORT_POLLING_DEFAULT_INTERVAL` seconds, default 10). Configure `DISTRIBUTED_COORDINATION_CONFIG` (Redis/Valkey) and these become event-driven: completion and abort are signalled over Redis **Streams**, so a waiter wakes when the signal lands instead of polling the database. Because stream entries are persisted, a waiter that reads slightly late, reconnects, or fails over still receives the signal. Each signal stream keeps only its latest entry and is given a TTL, so streams for tasks that are never awaited do not accumulate; set the retention window with `DISTRIBUTED_COORDINATION_SIGNAL_TTL` (default 24h). See [Distributed Coordination Backend](/admin-docs/configuration/cache#signal-cache-backend) for configuration details.
+By default, abort detection and sync join-and-wait use database polling. Configure `DISTRIBUTED_COORDINATION_CONFIG` to enable Redis pub/sub for real-time notifications. See [Distributed Coordination Backend](/admin-docs/configuration/cache#signal-cache-backend) for configuration details.
 :::

 ## API Reference
@@ -562,24 +387,19 @@ By default, abort detection and sync join-and-wait poll the task row in the meta
@task(
    name: str | None = None,
    scope: TaskScope = TaskScope.PRIVATE,
-    timeout: int | None = None,
-    subscription_policy: TaskSubscriptionPolicy | None = None,
+    timeout: int | None = None
 )
 ```

 - `name`: Task identifier (defaults to function name)
 - `scope`: `PRIVATE`, `SHARED`, or `SYSTEM`
 - `timeout`: Default timeout in seconds (can be overridden via `TaskOptions`)
- `subscription_policy`: Optional per-client subscription policy that refines the
-  principal-grain cancel decision (see
-  [Per-client subscriptions](#per-client-subscriptions-subscription-policies))

 ### TaskContext Methods

 | Method                           | Description                                   |
 | -------------------------------- | --------------------------------------------- |
-| `update_task(progress, payload, immediate=False)` | Update progress and/or custom payload (`immediate=True` bypasses write throttling) |
-| `get_dependency_payloads()`      | Return prerequisite tasks' payloads, in dependency-edge order |
+| `update_task(progress, payload)` | Update progress and/or custom payload         |
 | `on_cleanup(handler)`            | Register cleanup handler                      |
 | `on_abort(handler)`              | Register abort handler (makes task abortable) |

@@ -589,15 +409,13 @@ By default, abort detection and sync join-and-wait poll the task row in the meta
 TaskOptions(
    task_key: str | None = None,
    task_name: str | None = None,
-    timeout: int | None = None,
-    depends_on: list[Task | UUID | str] | None = None
+    timeout: int | None = None
 )
 ```

 - `task_key`: Deduplication key (also used as display name if `task_name` is not set)
 - `task_name`: Human-readable display name for the Task List UI
 - `timeout`: Timeout in seconds (overrides decorator default)
- `depends_on`: Prerequisite tasks to wait for before running. Pass the scheduled `Task` objects (canonical); a `UUID` or UUID string is also accepted (see [Task Dependencies](#task-dependencies))

 :::tip
 Provide a descriptive `task_name` for better readability in the Task List UI. While `task_key` is used for deduplication and may be technical (e.g., `chart_export_123`), `task_name` can be user-friendly (e.g., `"Export Sales Chart 123"`).
@@ -198,7 +198,7 @@ Each component should come with its dedicated storybook file.

 **One component per story:** Each storybook file should only contain one component unless substantially different variants are required

-**Component variants:** If the component behavior is substantially different when certain props are used, it is best to separate the story into different types. See the `superset-frontend/packages/superset-ui-core/src/components/Select/Select.stories.tsx` as an example.
+**Component variants:** If the component behavior is substantially different when certain props are used, it is best to separate the story into different types. See the `superset-frontend/src/components/Select/Select.stories.tsx` as an example.

 **Isolated state:** The storybook should show how the component works in an isolated state and with as few dependencies as possible

@@ -49,10 +49,10 @@ curl -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \

 | Method | Endpoint                                                               | Description                     |
 | ------ | ---------------------------------------------------------------------- | ------------------------------- |
-| `GET`  | [Get the CSRF token](/developer-docs/6.1.0/api/get-the-csrf-token)           | `/api/v1/security/csrf_token/`  |
-| `POST` | [Get a guest token](/developer-docs/6.1.0/api/get-a-guest-token)             | `/api/v1/security/guest_token/` |
-| `POST` | [Create security login](/developer-docs/6.1.0/api/create-security-login)     | `/api/v1/security/login`        |
-| `POST` | [Create security refresh](/developer-docs/6.1.0/api/create-security-refresh) | `/api/v1/security/refresh`      |
+| `GET`  | [Get the CSRF token](/developer-docs/api/get-the-csrf-token)           | `/api/v1/security/csrf_token/`  |
+| `POST` | [Get a guest token](/developer-docs/api/get-a-guest-token)             | `/api/v1/security/guest_token/` |
+| `POST` | [Create security login](/developer-docs/api/create-security-login)     | `/api/v1/security/login`        |
+| `POST` | [Create security refresh](/developer-docs/api/create-security-refresh) | `/api/v1/security/refresh`      |

 ---

@@ -65,34 +65,34 @@ curl -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \

 | Method   | Endpoint                                                                                                                                                               | Description                                          |
 | -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------- |
-| `DELETE` | [Bulk delete dashboards](/developer-docs/6.1.0/api/bulk-delete-dashboards)                                                                                                   | `/api/v1/dashboard/`                                 |
-| `GET`    | [Get a list of dashboards](/developer-docs/6.1.0/api/get-a-list-of-dashboards)                                                                                               | `/api/v1/dashboard/`                                 |
-| `POST`   | [Create a new dashboard](/developer-docs/6.1.0/api/create-a-new-dashboard)                                                                                                   | `/api/v1/dashboard/`                                 |
-| `GET`    | [Get metadata information about this API resource (dashboard--info)](/developer-docs/6.1.0/api/get-metadata-information-about-this-api-resource-dashboard-info)              | `/api/v1/dashboard/_info`                            |
-| `GET`    | [Get a dashboard detail information](/developer-docs/6.1.0/api/get-a-dashboard-detail-information)                                                                           | `/api/v1/dashboard/{id_or_slug}`                     |
-| `GET`    | [Get a dashboard's chart definitions.](/developer-docs/6.1.0/api/get-a-dashboards-chart-definitions)                                                                         | `/api/v1/dashboard/{id_or_slug}/charts`              |
-| `POST`   | [Create a copy of an existing dashboard](/developer-docs/6.1.0/api/create-a-copy-of-an-existing-dashboard)                                                                   | `/api/v1/dashboard/{id_or_slug}/copy/`               |
-| `GET`    | [Get dashboard's datasets](/developer-docs/6.1.0/api/get-dashboards-datasets)                                                                                                | `/api/v1/dashboard/{id_or_slug}/datasets`            |
-| `DELETE` | [Delete a dashboard's embedded configuration](/developer-docs/6.1.0/api/delete-a-dashboards-embedded-configuration)                                                          | `/api/v1/dashboard/{id_or_slug}/embedded`            |
-| `GET`    | [Get the dashboard's embedded configuration](/developer-docs/6.1.0/api/get-the-dashboards-embedded-configuration)                                                            | `/api/v1/dashboard/{id_or_slug}/embedded`            |
-| `POST`   | [Set a dashboard's embedded configuration](/developer-docs/6.1.0/api/set-a-dashboards-embedded-configuration)                                                                | `/api/v1/dashboard/{id_or_slug}/embedded`            |
-| `PUT`    | [Update dashboard by id_or_slug embedded](/developer-docs/6.1.0/api/update-dashboard-by-id-or-slug-embedded)                                                                 | `/api/v1/dashboard/{id_or_slug}/embedded`            |
-| `GET`    | [Get dashboard's tabs](/developer-docs/6.1.0/api/get-dashboards-tabs)                                                                                                        | `/api/v1/dashboard/{id_or_slug}/tabs`                |
-| `DELETE` | [Delete a dashboard](/developer-docs/6.1.0/api/delete-a-dashboard)                                                                                                           | `/api/v1/dashboard/{pk}`                             |
-| `PUT`    | [Update a dashboard](/developer-docs/6.1.0/api/update-a-dashboard)                                                                                                           | `/api/v1/dashboard/{pk}`                             |
-| `POST`   | [Compute and cache a screenshot (dashboard-pk-cache-dashboard-screenshot)](/developer-docs/6.1.0/api/compute-and-cache-a-screenshot-dashboard-pk-cache-dashboard-screenshot) | `/api/v1/dashboard/{pk}/cache_dashboard_screenshot/` |
-| `PUT`    | [Update chart customizations configuration for a dashboard.](/developer-docs/6.1.0/api/update-chart-customizations-configuration-for-a-dashboard)                            | `/api/v1/dashboard/{pk}/chart_customizations`        |
-| `PUT`    | [Update colors configuration for a dashboard.](/developer-docs/6.1.0/api/update-colors-configuration-for-a-dashboard)                                                        | `/api/v1/dashboard/{pk}/colors`                      |
-| `GET`    | [Export dashboard as example bundle](/developer-docs/6.1.0/api/export-dashboard-as-example-bundle)                                                                           | `/api/v1/dashboard/{pk}/export_as_example/`          |
-| `DELETE` | [Remove the dashboard from the user favorite list](/developer-docs/6.1.0/api/remove-the-dashboard-from-the-user-favorite-list)                                               | `/api/v1/dashboard/{pk}/favorites/`                  |
-| `POST`   | [Mark the dashboard as favorite for the current user](/developer-docs/6.1.0/api/mark-the-dashboard-as-favorite-for-the-current-user)                                         | `/api/v1/dashboard/{pk}/favorites/`                  |
-| `PUT`    | [Update native filters configuration for a dashboard.](/developer-docs/6.1.0/api/update-native-filters-configuration-for-a-dashboard)                                        | `/api/v1/dashboard/{pk}/filters`                     |
-| `GET`    | [Get a computed screenshot from cache (dashboard-pk-screenshot-digest)](/developer-docs/6.1.0/api/get-a-computed-screenshot-from-cache-dashboard-pk-screenshot-digest)       | `/api/v1/dashboard/{pk}/screenshot/{digest}/`        |
-| `GET`    | [Get dashboard's thumbnail](/developer-docs/6.1.0/api/get-dashboards-thumbnail)                                                                                              | `/api/v1/dashboard/{pk}/thumbnail/{digest}/`         |
-| `GET`    | [Download multiple dashboards as YAML files](/developer-docs/6.1.0/api/download-multiple-dashboards-as-yaml-files)                                                           | `/api/v1/dashboard/export/`                          |
-| `GET`    | [Check favorited dashboards for current user](/developer-docs/6.1.0/api/check-favorited-dashboards-for-current-user)                                                         | `/api/v1/dashboard/favorite_status/`                 |
-| `POST`   | [Import dashboard(s) with associated charts/datasets/databases](/developer-docs/6.1.0/api/import-dashboard-s-with-associated-charts-datasets-databases)                      | `/api/v1/dashboard/import/`                          |
-| `GET`    | [Get related fields data (dashboard-related-column-name)](/developer-docs/6.1.0/api/get-related-fields-data-dashboard-related-column-name)                                   | `/api/v1/dashboard/related/{column_name}`            |
+| `DELETE` | [Bulk delete dashboards](/developer-docs/api/bulk-delete-dashboards)                                                                                                   | `/api/v1/dashboard/`                                 |
+| `GET`    | [Get a list of dashboards](/developer-docs/api/get-a-list-of-dashboards)                                                                                               | `/api/v1/dashboard/`                                 |
+| `POST`   | [Create a new dashboard](/developer-docs/api/create-a-new-dashboard)                                                                                                   | `/api/v1/dashboard/`                                 |
+| `GET`    | [Get metadata information about this API resource (dashboard--info)](/developer-docs/api/get-metadata-information-about-this-api-resource-dashboard-info)              | `/api/v1/dashboard/_info`                            |
+| `GET`    | [Get a dashboard detail information](/developer-docs/api/get-a-dashboard-detail-information)                                                                           | `/api/v1/dashboard/{id_or_slug}`                     |
+| `GET`    | [Get a dashboard's chart definitions.](/developer-docs/api/get-a-dashboards-chart-definitions)                                                                         | `/api/v1/dashboard/{id_or_slug}/charts`              |
+| `POST`   | [Create a copy of an existing dashboard](/developer-docs/api/create-a-copy-of-an-existing-dashboard)                                                                   | `/api/v1/dashboard/{id_or_slug}/copy/`               |
+| `GET`    | [Get dashboard's datasets](/developer-docs/api/get-dashboards-datasets)                                                                                                | `/api/v1/dashboard/{id_or_slug}/datasets`            |
+| `DELETE` | [Delete a dashboard's embedded configuration](/developer-docs/api/delete-a-dashboards-embedded-configuration)                                                          | `/api/v1/dashboard/{id_or_slug}/embedded`            |
+| `GET`    | [Get the dashboard's embedded configuration](/developer-docs/api/get-the-dashboards-embedded-configuration)                                                            | `/api/v1/dashboard/{id_or_slug}/embedded`            |
+| `POST`   | [Set a dashboard's embedded configuration](/developer-docs/api/set-a-dashboards-embedded-configuration)                                                                | `/api/v1/dashboard/{id_or_slug}/embedded`            |
+| `PUT`    | [Update dashboard by id_or_slug embedded](/developer-docs/api/update-dashboard-by-id-or-slug-embedded)                                                                 | `/api/v1/dashboard/{id_or_slug}/embedded`            |
+| `GET`    | [Get dashboard's tabs](/developer-docs/api/get-dashboards-tabs)                                                                                                        | `/api/v1/dashboard/{id_or_slug}/tabs`                |
+| `DELETE` | [Delete a dashboard](/developer-docs/api/delete-a-dashboard)                                                                                                           | `/api/v1/dashboard/{pk}`                             |
+| `PUT`    | [Update a dashboard](/developer-docs/api/update-a-dashboard)                                                                                                           | `/api/v1/dashboard/{pk}`                             |
+| `POST`   | [Compute and cache a screenshot (dashboard-pk-cache-dashboard-screenshot)](/developer-docs/api/compute-and-cache-a-screenshot-dashboard-pk-cache-dashboard-screenshot) | `/api/v1/dashboard/{pk}/cache_dashboard_screenshot/` |
+| `PUT`    | [Update chart customizations configuration for a dashboard.](/developer-docs/api/update-chart-customizations-configuration-for-a-dashboard)                            | `/api/v1/dashboard/{pk}/chart_customizations`        |
+| `PUT`    | [Update colors configuration for a dashboard.](/developer-docs/api/update-colors-configuration-for-a-dashboard)                                                        | `/api/v1/dashboard/{pk}/colors`                      |
+| `GET`    | [Export dashboard as example bundle](/developer-docs/api/export-dashboard-as-example-bundle)                                                                           | `/api/v1/dashboard/{pk}/export_as_example/`          |
+| `DELETE` | [Remove the dashboard from the user favorite list](/developer-docs/api/remove-the-dashboard-from-the-user-favorite-list)                                               | `/api/v1/dashboard/{pk}/favorites/`                  |
+| `POST`   | [Mark the dashboard as favorite for the current user](/developer-docs/api/mark-the-dashboard-as-favorite-for-the-current-user)                                         | `/api/v1/dashboard/{pk}/favorites/`                  |
+| `PUT`    | [Update native filters configuration for a dashboard.](/developer-docs/api/update-native-filters-configuration-for-a-dashboard)                                        | `/api/v1/dashboard/{pk}/filters`                     |
+| `GET`    | [Get a computed screenshot from cache (dashboard-pk-screenshot-digest)](/developer-docs/api/get-a-computed-screenshot-from-cache-dashboard-pk-screenshot-digest)       | `/api/v1/dashboard/{pk}/screenshot/{digest}/`        |
+| `GET`    | [Get dashboard's thumbnail](/developer-docs/api/get-dashboards-thumbnail)                                                                                              | `/api/v1/dashboard/{pk}/thumbnail/{digest}/`         |
+| `GET`    | [Download multiple dashboards as YAML files](/developer-docs/api/download-multiple-dashboards-as-yaml-files)                                                           | `/api/v1/dashboard/export/`                          |
+| `GET`    | [Check favorited dashboards for current user](/developer-docs/api/check-favorited-dashboards-for-current-user)                                                         | `/api/v1/dashboard/favorite_status/`                 |
+| `POST`   | [Import dashboard(s) with associated charts/datasets/databases](/developer-docs/api/import-dashboard-s-with-associated-charts-datasets-databases)                      | `/api/v1/dashboard/import/`                          |
+| `GET`    | [Get related fields data (dashboard-related-column-name)](/developer-docs/api/get-related-fields-data-dashboard-related-column-name)                                   | `/api/v1/dashboard/related/{column_name}`            |

 </details>

@@ -101,26 +101,26 @@ curl -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \

 | Method   | Endpoint                                                                                                                                                             | Description                               |
 | -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------- |
-| `DELETE` | [Bulk delete charts](/developer-docs/6.1.0/api/bulk-delete-charts)                                                                                                         | `/api/v1/chart/`                          |
-| `GET`    | [Get a list of charts](/developer-docs/6.1.0/api/get-a-list-of-charts)                                                                                                     | `/api/v1/chart/`                          |
-| `POST`   | [Create a new chart](/developer-docs/6.1.0/api/create-a-new-chart)                                                                                                         | `/api/v1/chart/`                          |
-| `GET`    | [Get metadata information about this API resource (chart--info)](/developer-docs/6.1.0/api/get-metadata-information-about-this-api-resource-chart-info)                    | `/api/v1/chart/_info`                     |
-| `GET`    | [Get a chart detail information](/developer-docs/6.1.0/api/get-a-chart-detail-information)                                                                                 | `/api/v1/chart/{id_or_uuid}`              |
-| `DELETE` | [Delete a chart](/developer-docs/6.1.0/api/delete-a-chart)                                                                                                                 | `/api/v1/chart/{pk}`                      |
-| `PUT`    | [Update a chart](/developer-docs/6.1.0/api/update-a-chart)                                                                                                                 | `/api/v1/chart/{pk}`                      |
-| `GET`    | [Compute and cache a screenshot (chart-pk-cache-screenshot)](/developer-docs/6.1.0/api/compute-and-cache-a-screenshot-chart-pk-cache-screenshot)                           | `/api/v1/chart/{pk}/cache_screenshot/`    |
-| `GET`    | [Return payload data response for a chart](/developer-docs/6.1.0/api/return-payload-data-response-for-a-chart)                                                             | `/api/v1/chart/{pk}/data/`                |
-| `DELETE` | [Remove the chart from the user favorite list](/developer-docs/6.1.0/api/remove-the-chart-from-the-user-favorite-list)                                                     | `/api/v1/chart/{pk}/favorites/`           |
-| `POST`   | [Mark the chart as favorite for the current user](/developer-docs/6.1.0/api/mark-the-chart-as-favorite-for-the-current-user)                                               | `/api/v1/chart/{pk}/favorites/`           |
-| `GET`    | [Get a computed screenshot from cache (chart-pk-screenshot-digest)](/developer-docs/6.1.0/api/get-a-computed-screenshot-from-cache-chart-pk-screenshot-digest)             | `/api/v1/chart/{pk}/screenshot/{digest}/` |
-| `GET`    | [Get chart thumbnail](/developer-docs/6.1.0/api/get-chart-thumbnail)                                                                                                       | `/api/v1/chart/{pk}/thumbnail/{digest}/`  |
-| `POST`   | [Return payload data response for the given query (chart-data)](/developer-docs/6.1.0/api/return-payload-data-response-for-the-given-query-chart-data)                     | `/api/v1/chart/data`                      |
-| `GET`    | [Return payload data response for the given query (chart-data-cache-key)](/developer-docs/6.1.0/api/return-payload-data-response-for-the-given-query-chart-data-cache-key) | `/api/v1/chart/data/{cache_key}`          |
-| `GET`    | [Download multiple charts as YAML files](/developer-docs/6.1.0/api/download-multiple-charts-as-yaml-files)                                                                 | `/api/v1/chart/export/`                   |
-| `GET`    | [Check favorited charts for current user](/developer-docs/6.1.0/api/check-favorited-charts-for-current-user)                                                               | `/api/v1/chart/favorite_status/`          |
-| `POST`   | [Import chart(s) with associated datasets and databases](/developer-docs/6.1.0/api/import-chart-s-with-associated-datasets-and-databases)                                  | `/api/v1/chart/import/`                   |
-| `GET`    | [Get related fields data (chart-related-column-name)](/developer-docs/6.1.0/api/get-related-fields-data-chart-related-column-name)                                         | `/api/v1/chart/related/{column_name}`     |
-| `PUT`    | [Warm up the cache for the chart](/developer-docs/6.1.0/api/warm-up-the-cache-for-the-chart)                                                                               | `/api/v1/chart/warm_up_cache`             |
+| `DELETE` | [Bulk delete charts](/developer-docs/api/bulk-delete-charts)                                                                                                         | `/api/v1/chart/`                          |
+| `GET`    | [Get a list of charts](/developer-docs/api/get-a-list-of-charts)                                                                                                     | `/api/v1/chart/`                          |
+| `POST`   | [Create a new chart](/developer-docs/api/create-a-new-chart)                                                                                                         | `/api/v1/chart/`                          |
+| `GET`    | [Get metadata information about this API resource (chart--info)](/developer-docs/api/get-metadata-information-about-this-api-resource-chart-info)                    | `/api/v1/chart/_info`                     |
+| `GET`    | [Get a chart detail information](/developer-docs/api/get-a-chart-detail-information)                                                                                 | `/api/v1/chart/{id_or_uuid}`              |
+| `DELETE` | [Delete a chart](/developer-docs/api/delete-a-chart)                                                                                                                 | `/api/v1/chart/{pk}`                      |
+| `PUT`    | [Update a chart](/developer-docs/api/update-a-chart)                                                                                                                 | `/api/v1/chart/{pk}`                      |
+| `GET`    | [Compute and cache a screenshot (chart-pk-cache-screenshot)](/developer-docs/api/compute-and-cache-a-screenshot-chart-pk-cache-screenshot)                           | `/api/v1/chart/{pk}/cache_screenshot/`    |
+| `GET`    | [Return payload data response for a chart](/developer-docs/api/return-payload-data-response-for-a-chart)                                                             | `/api/v1/chart/{pk}/data/`                |
+| `DELETE` | [Remove the chart from the user favorite list](/developer-docs/api/remove-the-chart-from-the-user-favorite-list)                                                     | `/api/v1/chart/{pk}/favorites/`           |
+| `POST`   | [Mark the chart as favorite for the current user](/developer-docs/api/mark-the-chart-as-favorite-for-the-current-user)                                               | `/api/v1/chart/{pk}/favorites/`           |
+| `GET`    | [Get a computed screenshot from cache (chart-pk-screenshot-digest)](/developer-docs/api/get-a-computed-screenshot-from-cache-chart-pk-screenshot-digest)             | `/api/v1/chart/{pk}/screenshot/{digest}/` |
+| `GET`    | [Get chart thumbnail](/developer-docs/api/get-chart-thumbnail)                                                                                                       | `/api/v1/chart/{pk}/thumbnail/{digest}/`  |
+| `POST`   | [Return payload data response for the given query (chart-data)](/developer-docs/api/return-payload-data-response-for-the-given-query-chart-data)                     | `/api/v1/chart/data`                      |
+| `GET`    | [Return payload data response for the given query (chart-data-cache-key)](/developer-docs/api/return-payload-data-response-for-the-given-query-chart-data-cache-key) | `/api/v1/chart/data/{cache_key}`          |
+| `GET`    | [Download multiple charts as YAML files](/developer-docs/api/download-multiple-charts-as-yaml-files)                                                                 | `/api/v1/chart/export/`                   |
+| `GET`    | [Check favorited charts for current user](/developer-docs/api/check-favorited-charts-for-current-user)                                                               | `/api/v1/chart/favorite_status/`          |
+| `POST`   | [Import chart(s) with associated datasets and databases](/developer-docs/api/import-chart-s-with-associated-datasets-and-databases)                                  | `/api/v1/chart/import/`                   |
+| `GET`    | [Get related fields data (chart-related-column-name)](/developer-docs/api/get-related-fields-data-chart-related-column-name)                                         | `/api/v1/chart/related/{column_name}`     |
+| `PUT`    | [Warm up the cache for the chart](/developer-docs/api/warm-up-the-cache-for-the-chart)                                                                               | `/api/v1/chart/warm_up_cache`             |

 </details>

@@ -129,25 +129,25 @@ curl -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \

 | Method   | Endpoint                                                                                                                                                   | Description                                    |
 | -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- |
-| `DELETE` | [Bulk delete datasets](/developer-docs/6.1.0/api/bulk-delete-datasets)                                                                                           | `/api/v1/dataset/`                             |
-| `GET`    | [Get a list of datasets](/developer-docs/6.1.0/api/get-a-list-of-datasets)                                                                                       | `/api/v1/dataset/`                             |
-| `POST`   | [Create a new dataset](/developer-docs/6.1.0/api/create-a-new-dataset)                                                                                           | `/api/v1/dataset/`                             |
-| `GET`    | [Get metadata information about this API resource (dataset--info)](/developer-docs/6.1.0/api/get-metadata-information-about-this-api-resource-dataset-info)      | `/api/v1/dataset/_info`                        |
-| `GET`    | [Get a dataset](/developer-docs/6.1.0/api/get-a-dataset)                                                                                                         | `/api/v1/dataset/{id_or_uuid}`                 |
-| `GET`    | [Get charts and dashboards count associated to a dataset](/developer-docs/6.1.0/api/get-charts-and-dashboards-count-associated-to-a-dataset)                     | `/api/v1/dataset/{id_or_uuid}/related_objects` |
-| `DELETE` | [Delete a dataset](/developer-docs/6.1.0/api/delete-a-dataset)                                                                                                   | `/api/v1/dataset/{pk}`                         |
-| `PUT`    | [Update a dataset](/developer-docs/6.1.0/api/update-a-dataset)                                                                                                   | `/api/v1/dataset/{pk}`                         |
-| `DELETE` | [Delete a dataset column](/developer-docs/6.1.0/api/delete-a-dataset-column)                                                                                     | `/api/v1/dataset/{pk}/column/{column_id}`      |
-| `GET`    | [Get dataset drill info](/developer-docs/6.1.0/api/get-dataset-drill-info)                                                                                       | `/api/v1/dataset/{pk}/drill_info/`             |
-| `DELETE` | [Delete a dataset metric](/developer-docs/6.1.0/api/delete-a-dataset-metric)                                                                                     | `/api/v1/dataset/{pk}/metric/{metric_id}`      |
-| `PUT`    | [Refresh and update columns of a dataset](/developer-docs/6.1.0/api/refresh-and-update-columns-of-a-dataset)                                                     | `/api/v1/dataset/{pk}/refresh`                 |
-| `GET`    | [Get distinct values from field data (dataset-distinct-column-name)](/developer-docs/6.1.0/api/get-distinct-values-from-field-data-dataset-distinct-column-name) | `/api/v1/dataset/distinct/{column_name}`       |
-| `POST`   | [Duplicate a dataset](/developer-docs/6.1.0/api/duplicate-a-dataset)                                                                                             | `/api/v1/dataset/duplicate`                    |
-| `GET`    | [Download multiple datasets as YAML files](/developer-docs/6.1.0/api/download-multiple-datasets-as-yaml-files)                                                   | `/api/v1/dataset/export/`                      |
-| `POST`   | [Retrieve a table by name, or create it if it does not exist](/developer-docs/6.1.0/api/retrieve-a-table-by-name-or-create-it-if-it-does-not-exist)              | `/api/v1/dataset/get_or_create/`               |
-| `POST`   | [Import dataset(s) with associated databases](/developer-docs/6.1.0/api/import-dataset-s-with-associated-databases)                                              | `/api/v1/dataset/import/`                      |
-| `GET`    | [Get related fields data (dataset-related-column-name)](/developer-docs/6.1.0/api/get-related-fields-data-dataset-related-column-name)                           | `/api/v1/dataset/related/{column_name}`        |
-| `PUT`    | [Warm up the cache for each chart powered by the given table](/developer-docs/6.1.0/api/warm-up-the-cache-for-each-chart-powered-by-the-given-table)             | `/api/v1/dataset/warm_up_cache`                |
+| `DELETE` | [Bulk delete datasets](/developer-docs/api/bulk-delete-datasets)                                                                                           | `/api/v1/dataset/`                             |
+| `GET`    | [Get a list of datasets](/developer-docs/api/get-a-list-of-datasets)                                                                                       | `/api/v1/dataset/`                             |
+| `POST`   | [Create a new dataset](/developer-docs/api/create-a-new-dataset)                                                                                           | `/api/v1/dataset/`                             |
+| `GET`    | [Get metadata information about this API resource (dataset--info)](/developer-docs/api/get-metadata-information-about-this-api-resource-dataset-info)      | `/api/v1/dataset/_info`                        |
+| `GET`    | [Get a dataset](/developer-docs/api/get-a-dataset)                                                                                                         | `/api/v1/dataset/{id_or_uuid}`                 |
+| `GET`    | [Get charts and dashboards count associated to a dataset](/developer-docs/api/get-charts-and-dashboards-count-associated-to-a-dataset)                     | `/api/v1/dataset/{id_or_uuid}/related_objects` |
+| `DELETE` | [Delete a dataset](/developer-docs/api/delete-a-dataset)                                                                                                   | `/api/v1/dataset/{pk}`                         |
+| `PUT`    | [Update a dataset](/developer-docs/api/update-a-dataset)                                                                                                   | `/api/v1/dataset/{pk}`                         |
+| `DELETE` | [Delete a dataset column](/developer-docs/api/delete-a-dataset-column)                                                                                     | `/api/v1/dataset/{pk}/column/{column_id}`      |
+| `GET`    | [Get dataset drill info](/developer-docs/api/get-dataset-drill-info)                                                                                       | `/api/v1/dataset/{pk}/drill_info/`             |
+| `DELETE` | [Delete a dataset metric](/developer-docs/api/delete-a-dataset-metric)                                                                                     | `/api/v1/dataset/{pk}/metric/{metric_id}`      |
+| `PUT`    | [Refresh and update columns of a dataset](/developer-docs/api/refresh-and-update-columns-of-a-dataset)                                                     | `/api/v1/dataset/{pk}/refresh`                 |
+| `GET`    | [Get distinct values from field data (dataset-distinct-column-name)](/developer-docs/api/get-distinct-values-from-field-data-dataset-distinct-column-name) | `/api/v1/dataset/distinct/{column_name}`       |
+| `POST`   | [Duplicate a dataset](/developer-docs/api/duplicate-a-dataset)                                                                                             | `/api/v1/dataset/duplicate`                    |
+| `GET`    | [Download multiple datasets as YAML files](/developer-docs/api/download-multiple-datasets-as-yaml-files)                                                   | `/api/v1/dataset/export/`                      |
+| `POST`   | [Retrieve a table by name, or create it if it does not exist](/developer-docs/api/retrieve-a-table-by-name-or-create-it-if-it-does-not-exist)              | `/api/v1/dataset/get_or_create/`               |
+| `POST`   | [Import dataset(s) with associated databases](/developer-docs/api/import-dataset-s-with-associated-databases)                                              | `/api/v1/dataset/import/`                      |
+| `GET`    | [Get related fields data (dataset-related-column-name)](/developer-docs/api/get-related-fields-data-dataset-related-column-name)                           | `/api/v1/dataset/related/{column_name}`        |
+| `PUT`    | [Warm up the cache for each chart powered by the given table](/developer-docs/api/warm-up-the-cache-for-each-chart-powered-by-the-given-table)             | `/api/v1/dataset/warm_up_cache`                |

 </details>

@@ -156,36 +156,36 @@ curl -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \

 | Method   | Endpoint                                                                                                                                                                                     | Description                                                     |
 | -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------- |
-| `GET`    | [Get a list of databases](/developer-docs/6.1.0/api/get-a-list-of-databases)                                                                                                                       | `/api/v1/database/`                                             |
-| `POST`   | [Create a new database](/developer-docs/6.1.0/api/create-a-new-database)                                                                                                                           | `/api/v1/database/`                                             |
-| `GET`    | [Get metadata information about this API resource (database--info)](/developer-docs/6.1.0/api/get-metadata-information-about-this-api-resource-database-info)                                      | `/api/v1/database/_info`                                        |
-| `DELETE` | [Delete a database](/developer-docs/6.1.0/api/delete-a-database)                                                                                                                                   | `/api/v1/database/{pk}`                                         |
-| `GET`    | [Get a database](/developer-docs/6.1.0/api/get-a-database)                                                                                                                                         | `/api/v1/database/{pk}`                                         |
-| `PUT`    | [Change a database](/developer-docs/6.1.0/api/change-a-database)                                                                                                                                   | `/api/v1/database/{pk}`                                         |
-| `GET`    | [Get all catalogs from a database](/developer-docs/6.1.0/api/get-all-catalogs-from-a-database)                                                                                                     | `/api/v1/database/{pk}/catalogs/`                               |
-| `GET`    | [Get a database connection info](/developer-docs/6.1.0/api/get-a-database-connection-info)                                                                                                         | `/api/v1/database/{pk}/connection`                              |
-| `GET`    | [Get function names supported by a database](/developer-docs/6.1.0/api/get-function-names-supported-by-a-database)                                                                                 | `/api/v1/database/{pk}/function_names/`                         |
-| `GET`    | [Get charts and dashboards count associated to a database](/developer-docs/6.1.0/api/get-charts-and-dashboards-count-associated-to-a-database)                                                     | `/api/v1/database/{pk}/related_objects/`                        |
-| `GET`    | [The list of the database schemas where to upload information](/developer-docs/6.1.0/api/the-list-of-the-database-schemas-where-to-upload-information)                                             | `/api/v1/database/{pk}/schemas_access_for_file_upload/`         |
-| `GET`    | [Get all schemas from a database](/developer-docs/6.1.0/api/get-all-schemas-from-a-database)                                                                                                       | `/api/v1/database/{pk}/schemas/`                                |
-| `GET`    | [Get database select star for table (database-pk-select-star-table-name)](/developer-docs/6.1.0/api/get-database-select-star-for-table-database-pk-select-star-table-name)                         | `/api/v1/database/{pk}/select_star/{table_name}/`               |
-| `GET`    | [Get database select star for table (database-pk-select-star-table-name-schema-name)](/developer-docs/6.1.0/api/get-database-select-star-for-table-database-pk-select-star-table-name-schema-name) | `/api/v1/database/{pk}/select_star/{table_name}/{schema_name}/` |
-| `POST`   | [Re-sync all permissions for a database connection](/developer-docs/6.1.0/api/re-sync-all-permissions-for-a-database-connection)                                                                   | `/api/v1/database/{pk}/sync_permissions/`                       |
-| `GET`    | [Get table extra metadata (database-pk-table-extra-table-name-schema-name)](/developer-docs/6.1.0/api/get-table-extra-metadata-database-pk-table-extra-table-name-schema-name)                     | `/api/v1/database/{pk}/table_extra/{table_name}/{schema_name}/` |
-| `GET`    | [Get table metadata](/developer-docs/6.1.0/api/get-table-metadata)                                                                                                                                 | `/api/v1/database/{pk}/table_metadata/`                         |
-| `GET`    | [Get table extra metadata (database-pk-table-metadata-extra)](/developer-docs/6.1.0/api/get-table-extra-metadata-database-pk-table-metadata-extra)                                                 | `/api/v1/database/{pk}/table_metadata/extra/`                   |
-| `GET`    | [Get database table metadata](/developer-docs/6.1.0/api/get-database-table-metadata)                                                                                                               | `/api/v1/database/{pk}/table/{table_name}/{schema_name}/`       |
-| `GET`    | [Get a list of tables for given database](/developer-docs/6.1.0/api/get-a-list-of-tables-for-given-database)                                                                                       | `/api/v1/database/{pk}/tables/`                                 |
-| `POST`   | [Upload a file to a database table](/developer-docs/6.1.0/api/upload-a-file-to-a-database-table)                                                                                                   | `/api/v1/database/{pk}/upload/`                                 |
-| `POST`   | [Validate arbitrary SQL](/developer-docs/6.1.0/api/validate-arbitrary-sql)                                                                                                                         | `/api/v1/database/{pk}/validate_sql/`                           |
-| `GET`    | [Get names of databases currently available](/developer-docs/6.1.0/api/get-names-of-databases-currently-available)                                                                                 | `/api/v1/database/available/`                                   |
-| `GET`    | [Download database(s) and associated dataset(s) as a zip file](/developer-docs/6.1.0/api/download-database-s-and-associated-dataset-s-as-a-zip-file)                                               | `/api/v1/database/export/`                                      |
-| `POST`   | [Import database(s) with associated datasets](/developer-docs/6.1.0/api/import-database-s-with-associated-datasets)                                                                                | `/api/v1/database/import/`                                      |
-| `GET`    | [Receive personal access tokens from OAuth2](/developer-docs/6.1.0/api/receive-personal-access-tokens-from-o-auth-2)                                                                               | `/api/v1/database/oauth2/`                                      |
-| `GET`    | [Get related fields data (database-related-column-name)](/developer-docs/6.1.0/api/get-related-fields-data-database-related-column-name)                                                           | `/api/v1/database/related/{column_name}`                        |
-| `POST`   | [Test a database connection](/developer-docs/6.1.0/api/test-a-database-connection)                                                                                                                 | `/api/v1/database/test_connection/`                             |
-| `POST`   | [Upload a file and returns file metadata](/developer-docs/6.1.0/api/upload-a-file-and-returns-file-metadata)                                                                                       | `/api/v1/database/upload_metadata/`                             |
-| `POST`   | [Validate database connection parameters](/developer-docs/6.1.0/api/validate-database-connection-parameters)                                                                                       | `/api/v1/database/validate_parameters/`                         |
+| `GET`    | [Get a list of databases](/developer-docs/api/get-a-list-of-databases)                                                                                                                       | `/api/v1/database/`                                             |
+| `POST`   | [Create a new database](/developer-docs/api/create-a-new-database)                                                                                                                           | `/api/v1/database/`                                             |
+| `GET`    | [Get metadata information about this API resource (database--info)](/developer-docs/api/get-metadata-information-about-this-api-resource-database-info)                                      | `/api/v1/database/_info`                                        |
+| `DELETE` | [Delete a database](/developer-docs/api/delete-a-database)                                                                                                                                   | `/api/v1/database/{pk}`                                         |
+| `GET`    | [Get a database](/developer-docs/api/get-a-database)                                                                                                                                         | `/api/v1/database/{pk}`                                         |
+| `PUT`    | [Change a database](/developer-docs/api/change-a-database)                                                                                                                                   | `/api/v1/database/{pk}`                                         |
+| `GET`    | [Get all catalogs from a database](/developer-docs/api/get-all-catalogs-from-a-database)                                                                                                     | `/api/v1/database/{pk}/catalogs/`                               |
+| `GET`    | [Get a database connection info](/developer-docs/api/get-a-database-connection-info)                                                                                                         | `/api/v1/database/{pk}/connection`                              |
+| `GET`    | [Get function names supported by a database](/developer-docs/api/get-function-names-supported-by-a-database)                                                                                 | `/api/v1/database/{pk}/function_names/`                         |
+| `GET`    | [Get charts and dashboards count associated to a database](/developer-docs/api/get-charts-and-dashboards-count-associated-to-a-database)                                                     | `/api/v1/database/{pk}/related_objects/`                        |
+| `GET`    | [The list of the database schemas where to upload information](/developer-docs/api/the-list-of-the-database-schemas-where-to-upload-information)                                             | `/api/v1/database/{pk}/schemas_access_for_file_upload/`         |
+| `GET`    | [Get all schemas from a database](/developer-docs/api/get-all-schemas-from-a-database)                                                                                                       | `/api/v1/database/{pk}/schemas/`                                |
+| `GET`    | [Get database select star for table (database-pk-select-star-table-name)](/developer-docs/api/get-database-select-star-for-table-database-pk-select-star-table-name)                         | `/api/v1/database/{pk}/select_star/{table_name}/`               |
+| `GET`    | [Get database select star for table (database-pk-select-star-table-name-schema-name)](/developer-docs/api/get-database-select-star-for-table-database-pk-select-star-table-name-schema-name) | `/api/v1/database/{pk}/select_star/{table_name}/{schema_name}/` |
+| `POST`   | [Re-sync all permissions for a database connection](/developer-docs/api/re-sync-all-permissions-for-a-database-connection)                                                                   | `/api/v1/database/{pk}/sync_permissions/`                       |
+| `GET`    | [Get table extra metadata (database-pk-table-extra-table-name-schema-name)](/developer-docs/api/get-table-extra-metadata-database-pk-table-extra-table-name-schema-name)                     | `/api/v1/database/{pk}/table_extra/{table_name}/{schema_name}/` |
+| `GET`    | [Get table metadata](/developer-docs/api/get-table-metadata)                                                                                                                                 | `/api/v1/database/{pk}/table_metadata/`                         |
+| `GET`    | [Get table extra metadata (database-pk-table-metadata-extra)](/developer-docs/api/get-table-extra-metadata-database-pk-table-metadata-extra)                                                 | `/api/v1/database/{pk}/table_metadata/extra/`                   |
+| `GET`    | [Get database table metadata](/developer-docs/api/get-database-table-metadata)                                                                                                               | `/api/v1/database/{pk}/table/{table_name}/{schema_name}/`       |
+| `GET`    | [Get a list of tables for given database](/developer-docs/api/get-a-list-of-tables-for-given-database)                                                                                       | `/api/v1/database/{pk}/tables/`                                 |
+| `POST`   | [Upload a file to a database table](/developer-docs/api/upload-a-file-to-a-database-table)                                                                                                   | `/api/v1/database/{pk}/upload/`                                 |
+| `POST`   | [Validate arbitrary SQL](/developer-docs/api/validate-arbitrary-sql)                                                                                                                         | `/api/v1/database/{pk}/validate_sql/`                           |
+| `GET`    | [Get names of databases currently available](/developer-docs/api/get-names-of-databases-currently-available)                                                                                 | `/api/v1/database/available/`                                   |
+| `GET`    | [Download database(s) and associated dataset(s) as a zip file](/developer-docs/api/download-database-s-and-associated-dataset-s-as-a-zip-file)                                               | `/api/v1/database/export/`                                      |
+| `POST`   | [Import database(s) with associated datasets](/developer-docs/api/import-database-s-with-associated-datasets)                                                                                | `/api/v1/database/import/`                                      |
+| `GET`    | [Receive personal access tokens from OAuth2](/developer-docs/api/receive-personal-access-tokens-from-o-auth-2)                                                                               | `/api/v1/database/oauth2/`                                      |
+| `GET`    | [Get related fields data (database-related-column-name)](/developer-docs/api/get-related-fields-data-database-related-column-name)                                                           | `/api/v1/database/related/{column_name}`                        |
+| `POST`   | [Test a database connection](/developer-docs/api/test-a-database-connection)                                                                                                                 | `/api/v1/database/test_connection/`                             |
+| `POST`   | [Upload a file and returns file metadata](/developer-docs/api/upload-a-file-and-returns-file-metadata)                                                                                       | `/api/v1/database/upload_metadata/`                             |
+| `POST`   | [Validate database connection parameters](/developer-docs/api/validate-database-connection-parameters)                                                                                       | `/api/v1/database/validate_parameters/`                         |

 </details>

@@ -196,7 +196,7 @@ curl -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \

 | Method | Endpoint                                                                                                                                   | Description        |
 | ------ | ------------------------------------------------------------------------------------------------------------------------------------------ | ------------------ |
-| `GET`  | [Assemble Explore related information in a single endpoint](/developer-docs/6.1.0/api/assemble-explore-related-information-in-a-single-endpoint) | `/api/v1/explore/` |
+| `GET`  | [Assemble Explore related information in a single endpoint](/developer-docs/api/assemble-explore-related-information-in-a-single-endpoint) | `/api/v1/explore/` |

 </details>

@@ -205,13 +205,13 @@ curl -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \

 | Method | Endpoint                                                                                                             | Description                          |
 | ------ | -------------------------------------------------------------------------------------------------------------------- | ------------------------------------ |
-| `GET`  | [Get the bootstrap data for SqlLab page](/developer-docs/6.1.0/api/get-the-bootstrap-data-for-sql-lab-page)                | `/api/v1/sqllab/`                    |
-| `POST` | [Estimate the SQL query execution cost](/developer-docs/6.1.0/api/estimate-the-sql-query-execution-cost)                   | `/api/v1/sqllab/estimate/`           |
-| `POST` | [Execute a SQL query](/developer-docs/6.1.0/api/execute-a-sql-query)                                                       | `/api/v1/sqllab/execute/`            |
-| `POST` | [Export SQL query results to CSV with streaming](/developer-docs/6.1.0/api/export-sql-query-results-to-csv-with-streaming) | `/api/v1/sqllab/export_streaming/`   |
-| `GET`  | [Export the SQL query results to a CSV](/developer-docs/6.1.0/api/export-the-sql-query-results-to-a-csv)                   | `/api/v1/sqllab/export/{client_id}/` |
-| `POST` | [Format SQL code](/developer-docs/6.1.0/api/format-sql-code)                                                               | `/api/v1/sqllab/format_sql/`         |
-| `GET`  | [Get the result of a SQL query execution](/developer-docs/6.1.0/api/get-the-result-of-a-sql-query-execution)               | `/api/v1/sqllab/results/`            |
+| `GET`  | [Get the bootstrap data for SqlLab page](/developer-docs/api/get-the-bootstrap-data-for-sql-lab-page)                | `/api/v1/sqllab/`                    |
+| `POST` | [Estimate the SQL query execution cost](/developer-docs/api/estimate-the-sql-query-execution-cost)                   | `/api/v1/sqllab/estimate/`           |
+| `POST` | [Execute a SQL query](/developer-docs/api/execute-a-sql-query)                                                       | `/api/v1/sqllab/execute/`            |
+| `POST` | [Export SQL query results to CSV with streaming](/developer-docs/api/export-sql-query-results-to-csv-with-streaming) | `/api/v1/sqllab/export_streaming/`   |
+| `GET`  | [Export the SQL query results to a CSV](/developer-docs/api/export-the-sql-query-results-to-a-csv)                   | `/api/v1/sqllab/export/{client_id}/` |
+| `POST` | [Format SQL code](/developer-docs/api/format-sql-code)                                                               | `/api/v1/sqllab/format_sql/`         |
+| `GET`  | [Get the result of a SQL query execution](/developer-docs/api/get-the-result-of-a-sql-query-execution)               | `/api/v1/sqllab/results/`            |

 </details>

@@ -220,23 +220,23 @@ curl -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \

 | Method   | Endpoint                                                                                                                                                           | Description                                  |
 | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------- |
-| `GET`    | [Get a list of queries](/developer-docs/6.1.0/api/get-a-list-of-queries)                                                                                                 | `/api/v1/query/`                             |
-| `GET`    | [Get query detail information](/developer-docs/6.1.0/api/get-query-detail-information)                                                                                   | `/api/v1/query/{pk}`                         |
-| `GET`    | [Get distinct values from field data (query-distinct-column-name)](/developer-docs/6.1.0/api/get-distinct-values-from-field-data-query-distinct-column-name)             | `/api/v1/query/distinct/{column_name}`       |
-| `GET`    | [Get related fields data (query-related-column-name)](/developer-docs/6.1.0/api/get-related-fields-data-query-related-column-name)                                       | `/api/v1/query/related/{column_name}`        |
-| `POST`   | [Manually stop a query with client_id](/developer-docs/6.1.0/api/manually-stop-a-query-with-client-id)                                                                   | `/api/v1/query/stop`                         |
-| `GET`    | [Get a list of queries that changed after last_updated_ms](/developer-docs/6.1.0/api/get-a-list-of-queries-that-changed-after-last-updated-ms)                           | `/api/v1/query/updated_since`                |
-| `DELETE` | [Bulk delete saved queries](/developer-docs/6.1.0/api/bulk-delete-saved-queries)                                                                                         | `/api/v1/saved_query/`                       |
-| `GET`    | [Get a list of saved queries](/developer-docs/6.1.0/api/get-a-list-of-saved-queries)                                                                                     | `/api/v1/saved_query/`                       |
-| `POST`   | [Create a saved query](/developer-docs/6.1.0/api/create-a-saved-query)                                                                                                   | `/api/v1/saved_query/`                       |
-| `GET`    | [Get metadata information about this API resource (saved-query--info)](/developer-docs/6.1.0/api/get-metadata-information-about-this-api-resource-saved-query-info)      | `/api/v1/saved_query/_info`                  |
-| `DELETE` | [Delete a saved query](/developer-docs/6.1.0/api/delete-a-saved-query)                                                                                                   | `/api/v1/saved_query/{pk}`                   |
-| `GET`    | [Get a saved query](/developer-docs/6.1.0/api/get-a-saved-query)                                                                                                         | `/api/v1/saved_query/{pk}`                   |
-| `PUT`    | [Update a saved query](/developer-docs/6.1.0/api/update-a-saved-query)                                                                                                   | `/api/v1/saved_query/{pk}`                   |
-| `GET`    | [Get distinct values from field data (saved-query-distinct-column-name)](/developer-docs/6.1.0/api/get-distinct-values-from-field-data-saved-query-distinct-column-name) | `/api/v1/saved_query/distinct/{column_name}` |
-| `GET`    | [Download multiple saved queries as YAML files](/developer-docs/6.1.0/api/download-multiple-saved-queries-as-yaml-files)                                                 | `/api/v1/saved_query/export/`                |
-| `POST`   | [Import saved queries with associated databases](/developer-docs/6.1.0/api/import-saved-queries-with-associated-databases)                                               | `/api/v1/saved_query/import/`                |
-| `GET`    | [Get related fields data (saved-query-related-column-name)](/developer-docs/6.1.0/api/get-related-fields-data-saved-query-related-column-name)                           | `/api/v1/saved_query/related/{column_name}`  |
+| `GET`    | [Get a list of queries](/developer-docs/api/get-a-list-of-queries)                                                                                                 | `/api/v1/query/`                             |
+| `GET`    | [Get query detail information](/developer-docs/api/get-query-detail-information)                                                                                   | `/api/v1/query/{pk}`                         |
+| `GET`    | [Get distinct values from field data (query-distinct-column-name)](/developer-docs/api/get-distinct-values-from-field-data-query-distinct-column-name)             | `/api/v1/query/distinct/{column_name}`       |
+| `GET`    | [Get related fields data (query-related-column-name)](/developer-docs/api/get-related-fields-data-query-related-column-name)                                       | `/api/v1/query/related/{column_name}`        |
+| `POST`   | [Manually stop a query with client_id](/developer-docs/api/manually-stop-a-query-with-client-id)                                                                   | `/api/v1/query/stop`                         |
+| `GET`    | [Get a list of queries that changed after last_updated_ms](/developer-docs/api/get-a-list-of-queries-that-changed-after-last-updated-ms)                           | `/api/v1/query/updated_since`                |
+| `DELETE` | [Bulk delete saved queries](/developer-docs/api/bulk-delete-saved-queries)                                                                                         | `/api/v1/saved_query/`                       |
+| `GET`    | [Get a list of saved queries](/developer-docs/api/get-a-list-of-saved-queries)                                                                                     | `/api/v1/saved_query/`                       |
+| `POST`   | [Create a saved query](/developer-docs/api/create-a-saved-query)                                                                                                   | `/api/v1/saved_query/`                       |
+| `GET`    | [Get metadata information about this API resource (saved-query--info)](/developer-docs/api/get-metadata-information-about-this-api-resource-saved-query-info)      | `/api/v1/saved_query/_info`                  |
+| `DELETE` | [Delete a saved query](/developer-docs/api/delete-a-saved-query)                                                                                                   | `/api/v1/saved_query/{pk}`                   |
+| `GET`    | [Get a saved query](/developer-docs/api/get-a-saved-query)                                                                                                         | `/api/v1/saved_query/{pk}`                   |
+| `PUT`    | [Update a saved query](/developer-docs/api/update-a-saved-query)                                                                                                   | `/api/v1/saved_query/{pk}`                   |
+| `GET`    | [Get distinct values from field data (saved-query-distinct-column-name)](/developer-docs/api/get-distinct-values-from-field-data-saved-query-distinct-column-name) | `/api/v1/saved_query/distinct/{column_name}` |
+| `GET`    | [Download multiple saved queries as YAML files](/developer-docs/api/download-multiple-saved-queries-as-yaml-files)                                                 | `/api/v1/saved_query/export/`                |
+| `POST`   | [Import saved queries with associated databases](/developer-docs/api/import-saved-queries-with-associated-databases)                                               | `/api/v1/saved_query/import/`                |
+| `GET`    | [Get related fields data (saved-query-related-column-name)](/developer-docs/api/get-related-fields-data-saved-query-related-column-name)                           | `/api/v1/saved_query/related/{column_name}`  |

 </details>

@@ -245,8 +245,8 @@ curl -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \

 | Method | Endpoint                                                                                                             | Description                                                                         |
 | ------ | -------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------- |
-| `GET`  | [Get possible values for a datasource column](/developer-docs/6.1.0/api/get-possible-values-for-a-datasource-column)       | `/api/v1/datasource/{datasource_type}/{datasource_id}/column/{column_name}/values/` |
-| `POST` | [Validate a SQL expression against a datasource](/developer-docs/6.1.0/api/validate-a-sql-expression-against-a-datasource) | `/api/v1/datasource/{datasource_type}/{datasource_id}/validate_expression/`         |
+| `GET`  | [Get possible values for a datasource column](/developer-docs/api/get-possible-values-for-a-datasource-column)       | `/api/v1/datasource/{datasource_type}/{datasource_id}/column/{column_name}/values/` |
+| `POST` | [Validate a SQL expression against a datasource](/developer-docs/api/validate-a-sql-expression-against-a-datasource) | `/api/v1/datasource/{datasource_type}/{datasource_id}/validate_expression/`         |

 </details>

@@ -255,8 +255,8 @@ curl -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \

 | Method | Endpoint                                                                                                             | Description                          |
 | ------ | -------------------------------------------------------------------------------------------------------------------- | ------------------------------------ |
-| `GET`  | [Return an AdvancedDataTypeResponse](/developer-docs/6.1.0/api/return-an-advanced-data-type-response)                      | `/api/v1/advanced_data_type/convert` |
-| `GET`  | [Return a list of available advanced data types](/developer-docs/6.1.0/api/return-a-list-of-available-advanced-data-types) | `/api/v1/advanced_data_type/types`   |
+| `GET`  | [Return an AdvancedDataTypeResponse](/developer-docs/api/return-an-advanced-data-type-response)                      | `/api/v1/advanced_data_type/convert` |
+| `GET`  | [Return a list of available advanced data types](/developer-docs/api/return-a-list-of-available-advanced-data-types) | `/api/v1/advanced_data_type/types`   |

 </details>

@@ -267,21 +267,21 @@ curl -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \

 | Method   | Endpoint                                                                                                                 | Description                                    |
 | -------- | ------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------- |
-| `DELETE` | [Bulk delete tags](/developer-docs/6.1.0/api/bulk-delete-tags)                                                                 | `/api/v1/tag/`                                 |
-| `GET`    | [Get a list of tags](/developer-docs/6.1.0/api/get-a-list-of-tags)                                                             | `/api/v1/tag/`                                 |
-| `POST`   | [Create a tag](/developer-docs/6.1.0/api/create-a-tag)                                                                         | `/api/v1/tag/`                                 |
-| `GET`    | [Get metadata information about tag API endpoints](/developer-docs/6.1.0/api/get-metadata-information-about-tag-api-endpoints) | `/api/v1/tag/_info`                            |
-| `POST`   | [Add tags to an object](/developer-docs/6.1.0/api/add-tags-to-an-object)                                                       | `/api/v1/tag/{object_type}/{object_id}/`       |
-| `DELETE` | [Delete a tagged object](/developer-docs/6.1.0/api/delete-a-tagged-object)                                                     | `/api/v1/tag/{object_type}/{object_id}/{tag}/` |
-| `DELETE` | [Delete a tag](/developer-docs/6.1.0/api/delete-a-tag)                                                                         | `/api/v1/tag/{pk}`                             |
-| `GET`    | [Get a tag detail information](/developer-docs/6.1.0/api/get-a-tag-detail-information)                                         | `/api/v1/tag/{pk}`                             |
-| `PUT`    | [Update a tag](/developer-docs/6.1.0/api/update-a-tag)                                                                         | `/api/v1/tag/{pk}`                             |
-| `DELETE` | [Delete tag by pk favorites](/developer-docs/6.1.0/api/delete-tag-by-pk-favorites)                                             | `/api/v1/tag/{pk}/favorites/`                  |
-| `POST`   | [Create tag by pk favorites](/developer-docs/6.1.0/api/create-tag-by-pk-favorites)                                             | `/api/v1/tag/{pk}/favorites/`                  |
-| `POST`   | [Bulk create tags and tagged objects](/developer-docs/6.1.0/api/bulk-create-tags-and-tagged-objects)                           | `/api/v1/tag/bulk_create`                      |
-| `GET`    | [Get tag favorite status](/developer-docs/6.1.0/api/get-tag-favorite-status)                                                   | `/api/v1/tag/favorite_status/`                 |
-| `GET`    | [Get all objects associated with a tag](/developer-docs/6.1.0/api/get-all-objects-associated-with-a-tag)                       | `/api/v1/tag/get_objects/`                     |
-| `GET`    | [Get related fields data (tag-related-column-name)](/developer-docs/6.1.0/api/get-related-fields-data-tag-related-column-name) | `/api/v1/tag/related/{column_name}`            |
+| `DELETE` | [Bulk delete tags](/developer-docs/api/bulk-delete-tags)                                                                 | `/api/v1/tag/`                                 |
+| `GET`    | [Get a list of tags](/developer-docs/api/get-a-list-of-tags)                                                             | `/api/v1/tag/`                                 |
+| `POST`   | [Create a tag](/developer-docs/api/create-a-tag)                                                                         | `/api/v1/tag/`                                 |
+| `GET`    | [Get metadata information about tag API endpoints](/developer-docs/api/get-metadata-information-about-tag-api-endpoints) | `/api/v1/tag/_info`                            |
+| `POST`   | [Add tags to an object](/developer-docs/api/add-tags-to-an-object)                                                       | `/api/v1/tag/{object_type}/{object_id}/`       |
+| `DELETE` | [Delete a tagged object](/developer-docs/api/delete-a-tagged-object)                                                     | `/api/v1/tag/{object_type}/{object_id}/{tag}/` |
+| `DELETE` | [Delete a tag](/developer-docs/api/delete-a-tag)                                                                         | `/api/v1/tag/{pk}`                             |
+| `GET`    | [Get a tag detail information](/developer-docs/api/get-a-tag-detail-information)                                         | `/api/v1/tag/{pk}`                             |
+| `PUT`    | [Update a tag](/developer-docs/api/update-a-tag)                                                                         | `/api/v1/tag/{pk}`                             |
+| `DELETE` | [Delete tag by pk favorites](/developer-docs/api/delete-tag-by-pk-favorites)                                             | `/api/v1/tag/{pk}/favorites/`                  |
+| `POST`   | [Create tag by pk favorites](/developer-docs/api/create-tag-by-pk-favorites)                                             | `/api/v1/tag/{pk}/favorites/`                  |
+| `POST`   | [Bulk create tags and tagged objects](/developer-docs/api/bulk-create-tags-and-tagged-objects)                           | `/api/v1/tag/bulk_create`                      |
+| `GET`    | [Get tag favorite status](/developer-docs/api/get-tag-favorite-status)                                                   | `/api/v1/tag/favorite_status/`                 |
+| `GET`    | [Get all objects associated with a tag](/developer-docs/api/get-all-objects-associated-with-a-tag)                       | `/api/v1/tag/get_objects/`                     |
+| `GET`    | [Get related fields data (tag-related-column-name)](/developer-docs/api/get-related-fields-data-tag-related-column-name) | `/api/v1/tag/related/{column_name}`            |

 </details>

@@ -290,20 +290,20 @@ curl -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \

 | Method   | Endpoint                                                                                                                                                                 | Description                                                |
 | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------- |
-| `DELETE` | [Delete multiple annotation layers in a bulk operation](/developer-docs/6.1.0/api/delete-multiple-annotation-layers-in-a-bulk-operation)                                       | `/api/v1/annotation_layer/`                                |
-| `GET`    | [Get a list of annotation layers (annotation-layer)](/developer-docs/6.1.0/api/get-a-list-of-annotation-layers-annotation-layer)                                               | `/api/v1/annotation_layer/`                                |
-| `POST`   | [Create an annotation layer (annotation-layer)](/developer-docs/6.1.0/api/create-an-annotation-layer-annotation-layer)                                                         | `/api/v1/annotation_layer/`                                |
-| `GET`    | [Get metadata information about this API resource (annotation-layer--info)](/developer-docs/6.1.0/api/get-metadata-information-about-this-api-resource-annotation-layer-info)  | `/api/v1/annotation_layer/_info`                           |
-| `DELETE` | [Delete annotation layer (annotation-layer-pk)](/developer-docs/6.1.0/api/delete-annotation-layer-annotation-layer-pk)                                                         | `/api/v1/annotation_layer/{pk}`                            |
-| `GET`    | [Get an annotation layer (annotation-layer-pk)](/developer-docs/6.1.0/api/get-an-annotation-layer-annotation-layer-pk)                                                         | `/api/v1/annotation_layer/{pk}`                            |
-| `PUT`    | [Update an annotation layer (annotation-layer-pk)](/developer-docs/6.1.0/api/update-an-annotation-layer-annotation-layer-pk)                                                   | `/api/v1/annotation_layer/{pk}`                            |
-| `DELETE` | [Bulk delete annotation layers](/developer-docs/6.1.0/api/bulk-delete-annotation-layers)                                                                                       | `/api/v1/annotation_layer/{pk}/annotation/`                |
-| `GET`    | [Get a list of annotation layers (annotation-layer-pk-annotation)](/developer-docs/6.1.0/api/get-a-list-of-annotation-layers-annotation-layer-pk-annotation)                   | `/api/v1/annotation_layer/{pk}/annotation/`                |
-| `POST`   | [Create an annotation layer (annotation-layer-pk-annotation)](/developer-docs/6.1.0/api/create-an-annotation-layer-annotation-layer-pk-annotation)                             | `/api/v1/annotation_layer/{pk}/annotation/`                |
-| `DELETE` | [Delete annotation layer (annotation-layer-pk-annotation-annotation-id)](/developer-docs/6.1.0/api/delete-annotation-layer-annotation-layer-pk-annotation-annotation-id)       | `/api/v1/annotation_layer/{pk}/annotation/{annotation_id}` |
-| `GET`    | [Get an annotation layer (annotation-layer-pk-annotation-annotation-id)](/developer-docs/6.1.0/api/get-an-annotation-layer-annotation-layer-pk-annotation-annotation-id)       | `/api/v1/annotation_layer/{pk}/annotation/{annotation_id}` |
-| `PUT`    | [Update an annotation layer (annotation-layer-pk-annotation-annotation-id)](/developer-docs/6.1.0/api/update-an-annotation-layer-annotation-layer-pk-annotation-annotation-id) | `/api/v1/annotation_layer/{pk}/annotation/{annotation_id}` |
-| `GET`    | [Get related fields data (annotation-layer-related-column-name)](/developer-docs/6.1.0/api/get-related-fields-data-annotation-layer-related-column-name)                       | `/api/v1/annotation_layer/related/{column_name}`           |
+| `DELETE` | [Delete multiple annotation layers in a bulk operation](/developer-docs/api/delete-multiple-annotation-layers-in-a-bulk-operation)                                       | `/api/v1/annotation_layer/`                                |
+| `GET`    | [Get a list of annotation layers (annotation-layer)](/developer-docs/api/get-a-list-of-annotation-layers-annotation-layer)                                               | `/api/v1/annotation_layer/`                                |
+| `POST`   | [Create an annotation layer (annotation-layer)](/developer-docs/api/create-an-annotation-layer-annotation-layer)                                                         | `/api/v1/annotation_layer/`                                |
+| `GET`    | [Get metadata information about this API resource (annotation-layer--info)](/developer-docs/api/get-metadata-information-about-this-api-resource-annotation-layer-info)  | `/api/v1/annotation_layer/_info`                           |
+| `DELETE` | [Delete annotation layer (annotation-layer-pk)](/developer-docs/api/delete-annotation-layer-annotation-layer-pk)                                                         | `/api/v1/annotation_layer/{pk}`                            |
+| `GET`    | [Get an annotation layer (annotation-layer-pk)](/developer-docs/api/get-an-annotation-layer-annotation-layer-pk)                                                         | `/api/v1/annotation_layer/{pk}`                            |
+| `PUT`    | [Update an annotation layer (annotation-layer-pk)](/developer-docs/api/update-an-annotation-layer-annotation-layer-pk)                                                   | `/api/v1/annotation_layer/{pk}`                            |
+| `DELETE` | [Bulk delete annotation layers](/developer-docs/api/bulk-delete-annotation-layers)                                                                                       | `/api/v1/annotation_layer/{pk}/annotation/`                |
+| `GET`    | [Get a list of annotation layers (annotation-layer-pk-annotation)](/developer-docs/api/get-a-list-of-annotation-layers-annotation-layer-pk-annotation)                   | `/api/v1/annotation_layer/{pk}/annotation/`                |
+| `POST`   | [Create an annotation layer (annotation-layer-pk-annotation)](/developer-docs/api/create-an-annotation-layer-annotation-layer-pk-annotation)                             | `/api/v1/annotation_layer/{pk}/annotation/`                |
+| `DELETE` | [Delete annotation layer (annotation-layer-pk-annotation-annotation-id)](/developer-docs/api/delete-annotation-layer-annotation-layer-pk-annotation-annotation-id)       | `/api/v1/annotation_layer/{pk}/annotation/{annotation_id}` |
+| `GET`    | [Get an annotation layer (annotation-layer-pk-annotation-annotation-id)](/developer-docs/api/get-an-annotation-layer-annotation-layer-pk-annotation-annotation-id)       | `/api/v1/annotation_layer/{pk}/annotation/{annotation_id}` |
+| `PUT`    | [Update an annotation layer (annotation-layer-pk-annotation-annotation-id)](/developer-docs/api/update-an-annotation-layer-annotation-layer-pk-annotation-annotation-id) | `/api/v1/annotation_layer/{pk}/annotation/{annotation_id}` |
+| `GET`    | [Get related fields data (annotation-layer-related-column-name)](/developer-docs/api/get-related-fields-data-annotation-layer-related-column-name)                       | `/api/v1/annotation_layer/related/{column_name}`           |

 </details>

@@ -312,14 +312,14 @@ curl -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \

 | Method   | Endpoint                                                                                                                                                        | Description                                  |
 | -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------- |
-| `DELETE` | [Bulk delete CSS templates](/developer-docs/6.1.0/api/bulk-delete-css-templates)                                                                                      | `/api/v1/css_template/`                      |
-| `GET`    | [Get a list of CSS templates](/developer-docs/6.1.0/api/get-a-list-of-css-templates)                                                                                  | `/api/v1/css_template/`                      |
-| `POST`   | [Create a CSS template](/developer-docs/6.1.0/api/create-a-css-template)                                                                                              | `/api/v1/css_template/`                      |
-| `GET`    | [Get metadata information about this API resource (css-template--info)](/developer-docs/6.1.0/api/get-metadata-information-about-this-api-resource-css-template-info) | `/api/v1/css_template/_info`                 |
-| `DELETE` | [Delete a CSS template](/developer-docs/6.1.0/api/delete-a-css-template)                                                                                              | `/api/v1/css_template/{pk}`                  |
-| `GET`    | [Get a CSS template](/developer-docs/6.1.0/api/get-a-css-template)                                                                                                    | `/api/v1/css_template/{pk}`                  |
-| `PUT`    | [Update a CSS template](/developer-docs/6.1.0/api/update-a-css-template)                                                                                              | `/api/v1/css_template/{pk}`                  |
-| `GET`    | [Get related fields data (css-template-related-column-name)](/developer-docs/6.1.0/api/get-related-fields-data-css-template-related-column-name)                      | `/api/v1/css_template/related/{column_name}` |
+| `DELETE` | [Bulk delete CSS templates](/developer-docs/api/bulk-delete-css-templates)                                                                                      | `/api/v1/css_template/`                      |
+| `GET`    | [Get a list of CSS templates](/developer-docs/api/get-a-list-of-css-templates)                                                                                  | `/api/v1/css_template/`                      |
+| `POST`   | [Create a CSS template](/developer-docs/api/create-a-css-template)                                                                                              | `/api/v1/css_template/`                      |
+| `GET`    | [Get metadata information about this API resource (css-template--info)](/developer-docs/api/get-metadata-information-about-this-api-resource-css-template-info) | `/api/v1/css_template/_info`                 |
+| `DELETE` | [Delete a CSS template](/developer-docs/api/delete-a-css-template)                                                                                              | `/api/v1/css_template/{pk}`                  |
+| `GET`    | [Get a CSS template](/developer-docs/api/get-a-css-template)                                                                                                    | `/api/v1/css_template/{pk}`                  |
+| `PUT`    | [Update a CSS template](/developer-docs/api/update-a-css-template)                                                                                              | `/api/v1/css_template/{pk}`                  |
+| `GET`    | [Get related fields data (css-template-related-column-name)](/developer-docs/api/get-related-fields-data-css-template-related-column-name)                      | `/api/v1/css_template/related/{column_name}` |

 </details>

@@ -330,8 +330,8 @@ curl -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \

 | Method | Endpoint                                                                                              | Description                         |
 | ------ | ----------------------------------------------------------------------------------------------------- | ----------------------------------- |
-| `POST` | [Create a new dashboard's permanent link](/developer-docs/6.1.0/api/create-a-new-dashboards-permanent-link) | `/api/v1/dashboard/{pk}/permalink`  |
-| `GET`  | [Get dashboard's permanent link state](/developer-docs/6.1.0/api/get-dashboards-permanent-link-state)       | `/api/v1/dashboard/permalink/{key}` |
+| `POST` | [Create a new dashboard's permanent link](/developer-docs/api/create-a-new-dashboards-permanent-link) | `/api/v1/dashboard/{pk}/permalink`  |
+| `GET`  | [Get dashboard's permanent link state](/developer-docs/api/get-dashboards-permanent-link-state)       | `/api/v1/dashboard/permalink/{key}` |

 </details>

@@ -340,8 +340,8 @@ curl -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \

 | Method | Endpoint                                                                                                             | Description                       |
 | ------ | -------------------------------------------------------------------------------------------------------------------- | --------------------------------- |
-| `POST` | [Create a new permanent link (explore-permalink)](/developer-docs/6.1.0/api/create-a-new-permanent-link-explore-permalink) | `/api/v1/explore/permalink`       |
-| `GET`  | [Get chart's permanent link state](/developer-docs/6.1.0/api/get-charts-permanent-link-state)                              | `/api/v1/explore/permalink/{key}` |
+| `POST` | [Create a new permanent link (explore-permalink)](/developer-docs/api/create-a-new-permanent-link-explore-permalink) | `/api/v1/explore/permalink`       |
+| `GET`  | [Get chart's permanent link state](/developer-docs/api/get-charts-permanent-link-state)                              | `/api/v1/explore/permalink/{key}` |

 </details>

@@ -350,8 +350,8 @@ curl -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \

 | Method | Endpoint                                                                                                           | Description                      |
 | ------ | ------------------------------------------------------------------------------------------------------------------ | -------------------------------- |
-| `POST` | [Create a new permanent link (sqllab-permalink)](/developer-docs/6.1.0/api/create-a-new-permanent-link-sqllab-permalink) | `/api/v1/sqllab/permalink`       |
-| `GET`  | [Get permanent link state for SQLLab editor.](/developer-docs/6.1.0/api/get-permanent-link-state-for-sql-lab-editor)     | `/api/v1/sqllab/permalink/{key}` |
+| `POST` | [Create a new permanent link (sqllab-permalink)](/developer-docs/api/create-a-new-permanent-link-sqllab-permalink) | `/api/v1/sqllab/permalink`       |
+| `GET`  | [Get permanent link state for SQLLab editor.](/developer-docs/api/get-permanent-link-state-for-sql-lab-editor)     | `/api/v1/sqllab/permalink/{key}` |

 </details>

@@ -360,7 +360,7 @@ curl -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \

 | Method | Endpoint                                                                                                                     | Description                         |
 | ------ | ---------------------------------------------------------------------------------------------------------------------------- | ----------------------------------- |
-| `GET`  | [Get a report schedule log (embedded-dashboard-uuid)](/developer-docs/6.1.0/api/get-a-report-schedule-log-embedded-dashboard-uuid) | `/api/v1/embedded_dashboard/{uuid}` |
+| `GET`  | [Get a report schedule log (embedded-dashboard-uuid)](/developer-docs/api/get-a-report-schedule-log-embedded-dashboard-uuid) | `/api/v1/embedded_dashboard/{uuid}` |

 </details>

@@ -369,10 +369,10 @@ curl -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \

 | Method   | Endpoint                                                                                              | Description                                 |
 | -------- | ----------------------------------------------------------------------------------------------------- | ------------------------------------------- |
-| `POST`   | [Create a dashboard's filter state](/developer-docs/6.1.0/api/create-a-dashboards-filter-state)             | `/api/v1/dashboard/{pk}/filter_state`       |
-| `DELETE` | [Delete a dashboard's filter state value](/developer-docs/6.1.0/api/delete-a-dashboards-filter-state-value) | `/api/v1/dashboard/{pk}/filter_state/{key}` |
-| `GET`    | [Get a dashboard's filter state value](/developer-docs/6.1.0/api/get-a-dashboards-filter-state-value)       | `/api/v1/dashboard/{pk}/filter_state/{key}` |
-| `PUT`    | [Update a dashboard's filter state value](/developer-docs/6.1.0/api/update-a-dashboards-filter-state-value) | `/api/v1/dashboard/{pk}/filter_state/{key}` |
+| `POST`   | [Create a dashboard's filter state](/developer-docs/api/create-a-dashboards-filter-state)             | `/api/v1/dashboard/{pk}/filter_state`       |
+| `DELETE` | [Delete a dashboard's filter state value](/developer-docs/api/delete-a-dashboards-filter-state-value) | `/api/v1/dashboard/{pk}/filter_state/{key}` |
+| `GET`    | [Get a dashboard's filter state value](/developer-docs/api/get-a-dashboards-filter-state-value)       | `/api/v1/dashboard/{pk}/filter_state/{key}` |
+| `PUT`    | [Update a dashboard's filter state value](/developer-docs/api/update-a-dashboards-filter-state-value) | `/api/v1/dashboard/{pk}/filter_state/{key}` |

 </details>

@@ -381,10 +381,10 @@ curl -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \

 | Method   | Endpoint                                                                         | Description                       |
 | -------- | -------------------------------------------------------------------------------- | --------------------------------- |
-| `POST`   | [Create a new form_data](/developer-docs/6.1.0/api/create-a-new-form-data)             | `/api/v1/explore/form_data`       |
-| `DELETE` | [Delete a form_data](/developer-docs/6.1.0/api/delete-a-form-data)                     | `/api/v1/explore/form_data/{key}` |
-| `GET`    | [Get a form_data](/developer-docs/6.1.0/api/get-a-form-data)                           | `/api/v1/explore/form_data/{key}` |
-| `PUT`    | [Update an existing form_data](/developer-docs/6.1.0/api/update-an-existing-form-data) | `/api/v1/explore/form_data/{key}` |
+| `POST`   | [Create a new form_data](/developer-docs/api/create-a-new-form-data)             | `/api/v1/explore/form_data`       |
+| `DELETE` | [Delete a form_data](/developer-docs/api/delete-a-form-data)                     | `/api/v1/explore/form_data/{key}` |
+| `GET`    | [Get a form_data](/developer-docs/api/get-a-form-data)                           | `/api/v1/explore/form_data/{key}` |
+| `PUT`    | [Update an existing form_data](/developer-docs/api/update-an-existing-form-data) | `/api/v1/explore/form_data/{key}` |

 </details>

@@ -395,17 +395,17 @@ curl -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \

 | Method   | Endpoint                                                                                                                                            | Description                            |
 | -------- | --------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------- |
-| `DELETE` | [Bulk delete report schedules](/developer-docs/6.1.0/api/bulk-delete-report-schedules)                                                                    | `/api/v1/report/`                      |
-| `GET`    | [Get a list of report schedules](/developer-docs/6.1.0/api/get-a-list-of-report-schedules)                                                                | `/api/v1/report/`                      |
-| `POST`   | [Create a report schedule](/developer-docs/6.1.0/api/create-a-report-schedule)                                                                            | `/api/v1/report/`                      |
-| `GET`    | [Get metadata information about this API resource (report--info)](/developer-docs/6.1.0/api/get-metadata-information-about-this-api-resource-report-info) | `/api/v1/report/_info`                 |
-| `DELETE` | [Delete a report schedule](/developer-docs/6.1.0/api/delete-a-report-schedule)                                                                            | `/api/v1/report/{pk}`                  |
-| `GET`    | [Get a report schedule](/developer-docs/6.1.0/api/get-a-report-schedule)                                                                                  | `/api/v1/report/{pk}`                  |
-| `PUT`    | [Update a report schedule](/developer-docs/6.1.0/api/update-a-report-schedule)                                                                            | `/api/v1/report/{pk}`                  |
-| `GET`    | [Get a list of report schedule logs](/developer-docs/6.1.0/api/get-a-list-of-report-schedule-logs)                                                        | `/api/v1/report/{pk}/log/`             |
-| `GET`    | [Get a report schedule log (report-pk-log-log-id)](/developer-docs/6.1.0/api/get-a-report-schedule-log-report-pk-log-log-id)                              | `/api/v1/report/{pk}/log/{log_id}`     |
-| `GET`    | [Get related fields data (report-related-column-name)](/developer-docs/6.1.0/api/get-related-fields-data-report-related-column-name)                      | `/api/v1/report/related/{column_name}` |
-| `GET`    | [Get slack channels](/developer-docs/6.1.0/api/get-slack-channels)                                                                                        | `/api/v1/report/slack_channels/`       |
+| `DELETE` | [Bulk delete report schedules](/developer-docs/api/bulk-delete-report-schedules)                                                                    | `/api/v1/report/`                      |
+| `GET`    | [Get a list of report schedules](/developer-docs/api/get-a-list-of-report-schedules)                                                                | `/api/v1/report/`                      |
+| `POST`   | [Create a report schedule](/developer-docs/api/create-a-report-schedule)                                                                            | `/api/v1/report/`                      |
+| `GET`    | [Get metadata information about this API resource (report--info)](/developer-docs/api/get-metadata-information-about-this-api-resource-report-info) | `/api/v1/report/_info`                 |
+| `DELETE` | [Delete a report schedule](/developer-docs/api/delete-a-report-schedule)                                                                            | `/api/v1/report/{pk}`                  |
+| `GET`    | [Get a report schedule](/developer-docs/api/get-a-report-schedule)                                                                                  | `/api/v1/report/{pk}`                  |
+| `PUT`    | [Update a report schedule](/developer-docs/api/update-a-report-schedule)                                                                            | `/api/v1/report/{pk}`                  |
+| `GET`    | [Get a list of report schedule logs](/developer-docs/api/get-a-list-of-report-schedule-logs)                                                        | `/api/v1/report/{pk}/log/`             |
+| `GET`    | [Get a report schedule log (report-pk-log-log-id)](/developer-docs/api/get-a-report-schedule-log-report-pk-log-log-id)                              | `/api/v1/report/{pk}/log/{log_id}`     |
+| `GET`    | [Get related fields data (report-related-column-name)](/developer-docs/api/get-related-fields-data-report-related-column-name)                      | `/api/v1/report/related/{column_name}` |
+| `GET`    | [Get slack channels](/developer-docs/api/get-slack-channels)                                                                                        | `/api/v1/report/slack_channels/`       |

 </details>

@@ -416,17 +416,17 @@ curl -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \

 | Method   | Endpoint                                                                                                         | Description                                     |
 | -------- | ---------------------------------------------------------------------------------------------------------------- | ----------------------------------------------- |
-| `GET`    | [Get security roles](/developer-docs/6.1.0/api/get-security-roles)                                                     | `/api/v1/security/roles/`                       |
-| `POST`   | [Create security roles](/developer-docs/6.1.0/api/create-security-roles)                                               | `/api/v1/security/roles/`                       |
-| `GET`    | [Get security roles info](/developer-docs/6.1.0/api/get-security-roles-info)                                           | `/api/v1/security/roles/_info`                  |
-| `DELETE` | [Delete security roles by pk](/developer-docs/6.1.0/api/delete-security-roles-by-pk)                                   | `/api/v1/security/roles/{pk}`                   |
-| `GET`    | [Get security roles by pk](/developer-docs/6.1.0/api/get-security-roles-by-pk)                                         | `/api/v1/security/roles/{pk}`                   |
-| `PUT`    | [Update security roles by pk](/developer-docs/6.1.0/api/update-security-roles-by-pk)                                   | `/api/v1/security/roles/{pk}`                   |
-| `PUT`    | [Update security roles by role_id groups](/developer-docs/6.1.0/api/update-security-roles-by-role-id-groups)           | `/api/v1/security/roles/{role_id}/groups`       |
-| `POST`   | [Create security roles by role_id permissions](/developer-docs/6.1.0/api/create-security-roles-by-role-id-permissions) | `/api/v1/security/roles/{role_id}/permissions`  |
-| `GET`    | [Get security roles by role_id permissions](/developer-docs/6.1.0/api/get-security-roles-by-role-id-permissions)       | `/api/v1/security/roles/{role_id}/permissions/` |
-| `PUT`    | [Update security roles by role_id users](/developer-docs/6.1.0/api/update-security-roles-by-role-id-users)             | `/api/v1/security/roles/{role_id}/users`        |
-| `GET`    | [List roles](/developer-docs/6.1.0/api/list-roles)                                                                     | `/api/v1/security/roles/search/`                |
+| `GET`    | [Get security roles](/developer-docs/api/get-security-roles)                                                     | `/api/v1/security/roles/`                       |
+| `POST`   | [Create security roles](/developer-docs/api/create-security-roles)                                               | `/api/v1/security/roles/`                       |
+| `GET`    | [Get security roles info](/developer-docs/api/get-security-roles-info)                                           | `/api/v1/security/roles/_info`                  |
+| `DELETE` | [Delete security roles by pk](/developer-docs/api/delete-security-roles-by-pk)                                   | `/api/v1/security/roles/{pk}`                   |
+| `GET`    | [Get security roles by pk](/developer-docs/api/get-security-roles-by-pk)                                         | `/api/v1/security/roles/{pk}`                   |
+| `PUT`    | [Update security roles by pk](/developer-docs/api/update-security-roles-by-pk)                                   | `/api/v1/security/roles/{pk}`                   |
+| `PUT`    | [Update security roles by role_id groups](/developer-docs/api/update-security-roles-by-role-id-groups)           | `/api/v1/security/roles/{role_id}/groups`       |
+| `POST`   | [Create security roles by role_id permissions](/developer-docs/api/create-security-roles-by-role-id-permissions) | `/api/v1/security/roles/{role_id}/permissions`  |
+| `GET`    | [Get security roles by role_id permissions](/developer-docs/api/get-security-roles-by-role-id-permissions)       | `/api/v1/security/roles/{role_id}/permissions/` |
+| `PUT`    | [Update security roles by role_id users](/developer-docs/api/update-security-roles-by-role-id-users)             | `/api/v1/security/roles/{role_id}/users`        |
+| `GET`    | [List roles](/developer-docs/api/list-roles)                                                                     | `/api/v1/security/roles/search/`                |

 </details>

@@ -435,12 +435,12 @@ curl -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \

 | Method   | Endpoint                                                                       | Description                    |
 | -------- | ------------------------------------------------------------------------------ | ------------------------------ |
-| `GET`    | [Get security users](/developer-docs/6.1.0/api/get-security-users)                   | `/api/v1/security/users/`      |
-| `POST`   | [Create security users](/developer-docs/6.1.0/api/create-security-users)             | `/api/v1/security/users/`      |
-| `GET`    | [Get security users info](/developer-docs/6.1.0/api/get-security-users-info)         | `/api/v1/security/users/_info` |
-| `DELETE` | [Delete security users by pk](/developer-docs/6.1.0/api/delete-security-users-by-pk) | `/api/v1/security/users/{pk}`  |
-| `GET`    | [Get security users by pk](/developer-docs/6.1.0/api/get-security-users-by-pk)       | `/api/v1/security/users/{pk}`  |
-| `PUT`    | [Update security users by pk](/developer-docs/6.1.0/api/update-security-users-by-pk) | `/api/v1/security/users/{pk}`  |
+| `GET`    | [Get security users](/developer-docs/api/get-security-users)                   | `/api/v1/security/users/`      |
+| `POST`   | [Create security users](/developer-docs/api/create-security-users)             | `/api/v1/security/users/`      |
+| `GET`    | [Get security users info](/developer-docs/api/get-security-users-info)         | `/api/v1/security/users/_info` |
+| `DELETE` | [Delete security users by pk](/developer-docs/api/delete-security-users-by-pk) | `/api/v1/security/users/{pk}`  |
+| `GET`    | [Get security users by pk](/developer-docs/api/get-security-users-by-pk)       | `/api/v1/security/users/{pk}`  |
+| `PUT`    | [Update security users by pk](/developer-docs/api/update-security-users-by-pk) | `/api/v1/security/users/{pk}`  |

 </details>

@@ -449,9 +449,9 @@ curl -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \

 | Method | Endpoint                                                                             | Description                          |
 | ------ | ------------------------------------------------------------------------------------ | ------------------------------------ |
-| `GET`  | [Get security permissions](/developer-docs/6.1.0/api/get-security-permissions)             | `/api/v1/security/permissions/`      |
-| `GET`  | [Get security permissions info](/developer-docs/6.1.0/api/get-security-permissions-info)   | `/api/v1/security/permissions/_info` |
-| `GET`  | [Get security permissions by pk](/developer-docs/6.1.0/api/get-security-permissions-by-pk) | `/api/v1/security/permissions/{pk}`  |
+| `GET`  | [Get security permissions](/developer-docs/api/get-security-permissions)             | `/api/v1/security/permissions/`      |
+| `GET`  | [Get security permissions info](/developer-docs/api/get-security-permissions-info)   | `/api/v1/security/permissions/_info` |
+| `GET`  | [Get security permissions by pk](/developer-docs/api/get-security-permissions-by-pk) | `/api/v1/security/permissions/{pk}`  |

 </details>

@@ -460,12 +460,12 @@ curl -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \

 | Method   | Endpoint                                                                               | Description                        |
 | -------- | -------------------------------------------------------------------------------------- | ---------------------------------- |
-| `GET`    | [Get security resources](/developer-docs/6.1.0/api/get-security-resources)                   | `/api/v1/security/resources/`      |
-| `POST`   | [Create security resources](/developer-docs/6.1.0/api/create-security-resources)             | `/api/v1/security/resources/`      |
-| `GET`    | [Get security resources info](/developer-docs/6.1.0/api/get-security-resources-info)         | `/api/v1/security/resources/_info` |
-| `DELETE` | [Delete security resources by pk](/developer-docs/6.1.0/api/delete-security-resources-by-pk) | `/api/v1/security/resources/{pk}`  |
-| `GET`    | [Get security resources by pk](/developer-docs/6.1.0/api/get-security-resources-by-pk)       | `/api/v1/security/resources/{pk}`  |
-| `PUT`    | [Update security resources by pk](/developer-docs/6.1.0/api/update-security-resources-by-pk) | `/api/v1/security/resources/{pk}`  |
+| `GET`    | [Get security resources](/developer-docs/api/get-security-resources)                   | `/api/v1/security/resources/`      |
+| `POST`   | [Create security resources](/developer-docs/api/create-security-resources)             | `/api/v1/security/resources/`      |
+| `GET`    | [Get security resources info](/developer-docs/api/get-security-resources-info)         | `/api/v1/security/resources/_info` |
+| `DELETE` | [Delete security resources by pk](/developer-docs/api/delete-security-resources-by-pk) | `/api/v1/security/resources/{pk}`  |
+| `GET`    | [Get security resources by pk](/developer-docs/api/get-security-resources-by-pk)       | `/api/v1/security/resources/{pk}`  |
+| `PUT`    | [Update security resources by pk](/developer-docs/api/update-security-resources-by-pk) | `/api/v1/security/resources/{pk}`  |

 </details>

@@ -474,12 +474,12 @@ curl -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \

 | Method   | Endpoint                                                                                                       | Description                                    |
 | -------- | -------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- |
-| `GET`    | [Get security permissions resources](/developer-docs/6.1.0/api/get-security-permissions-resources)                   | `/api/v1/security/permissions-resources/`      |
-| `POST`   | [Create security permissions resources](/developer-docs/6.1.0/api/create-security-permissions-resources)             | `/api/v1/security/permissions-resources/`      |
-| `GET`    | [Get security permissions resources info](/developer-docs/6.1.0/api/get-security-permissions-resources-info)         | `/api/v1/security/permissions-resources/_info` |
-| `DELETE` | [Delete security permissions resources by pk](/developer-docs/6.1.0/api/delete-security-permissions-resources-by-pk) | `/api/v1/security/permissions-resources/{pk}`  |
-| `GET`    | [Get security permissions resources by pk](/developer-docs/6.1.0/api/get-security-permissions-resources-by-pk)       | `/api/v1/security/permissions-resources/{pk}`  |
-| `PUT`    | [Update security permissions resources by pk](/developer-docs/6.1.0/api/update-security-permissions-resources-by-pk) | `/api/v1/security/permissions-resources/{pk}`  |
+| `GET`    | [Get security permissions resources](/developer-docs/api/get-security-permissions-resources)                   | `/api/v1/security/permissions-resources/`      |
+| `POST`   | [Create security permissions resources](/developer-docs/api/create-security-permissions-resources)             | `/api/v1/security/permissions-resources/`      |
+| `GET`    | [Get security permissions resources info](/developer-docs/api/get-security-permissions-resources-info)         | `/api/v1/security/permissions-resources/_info` |
+| `DELETE` | [Delete security permissions resources by pk](/developer-docs/api/delete-security-permissions-resources-by-pk) | `/api/v1/security/permissions-resources/{pk}`  |
+| `GET`    | [Get security permissions resources by pk](/developer-docs/api/get-security-permissions-resources-by-pk)       | `/api/v1/security/permissions-resources/{pk}`  |
+| `PUT`    | [Update security permissions resources by pk](/developer-docs/api/update-security-permissions-resources-by-pk) | `/api/v1/security/permissions-resources/{pk}`  |

 </details>

@@ -488,14 +488,14 @@ curl -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \

 | Method   | Endpoint                                                                                                                                                                | Description                                      |
 | -------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------ |
-| `DELETE` | [Bulk delete RLS rules](/developer-docs/6.1.0/api/bulk-delete-rls-rules)                                                                                                      | `/api/v1/rowlevelsecurity/`                      |
-| `GET`    | [Get a list of RLS](/developer-docs/6.1.0/api/get-a-list-of-rls)                                                                                                              | `/api/v1/rowlevelsecurity/`                      |
-| `POST`   | [Create a new RLS rule](/developer-docs/6.1.0/api/create-a-new-rls-rule)                                                                                                      | `/api/v1/rowlevelsecurity/`                      |
-| `GET`    | [Get metadata information about this API resource (rowlevelsecurity--info)](/developer-docs/6.1.0/api/get-metadata-information-about-this-api-resource-rowlevelsecurity-info) | `/api/v1/rowlevelsecurity/_info`                 |
-| `DELETE` | [Delete an RLS](/developer-docs/6.1.0/api/delete-an-rls)                                                                                                                      | `/api/v1/rowlevelsecurity/{pk}`                  |
-| `GET`    | [Get an RLS](/developer-docs/6.1.0/api/get-an-rls)                                                                                                                            | `/api/v1/rowlevelsecurity/{pk}`                  |
-| `PUT`    | [Update an RLS rule](/developer-docs/6.1.0/api/update-an-rls-rule)                                                                                                            | `/api/v1/rowlevelsecurity/{pk}`                  |
-| `GET`    | [Get related fields data (rowlevelsecurity-related-column-name)](/developer-docs/6.1.0/api/get-related-fields-data-rowlevelsecurity-related-column-name)                      | `/api/v1/rowlevelsecurity/related/{column_name}` |
+| `DELETE` | [Bulk delete RLS rules](/developer-docs/api/bulk-delete-rls-rules)                                                                                                      | `/api/v1/rowlevelsecurity/`                      |
+| `GET`    | [Get a list of RLS](/developer-docs/api/get-a-list-of-rls)                                                                                                              | `/api/v1/rowlevelsecurity/`                      |
+| `POST`   | [Create a new RLS rule](/developer-docs/api/create-a-new-rls-rule)                                                                                                      | `/api/v1/rowlevelsecurity/`                      |
+| `GET`    | [Get metadata information about this API resource (rowlevelsecurity--info)](/developer-docs/api/get-metadata-information-about-this-api-resource-rowlevelsecurity-info) | `/api/v1/rowlevelsecurity/_info`                 |
+| `DELETE` | [Delete an RLS](/developer-docs/api/delete-an-rls)                                                                                                                      | `/api/v1/rowlevelsecurity/{pk}`                  |
+| `GET`    | [Get an RLS](/developer-docs/api/get-an-rls)                                                                                                                            | `/api/v1/rowlevelsecurity/{pk}`                  |
+| `PUT`    | [Update an RLS rule](/developer-docs/api/update-an-rls-rule)                                                                                                            | `/api/v1/rowlevelsecurity/{pk}`                  |
+| `GET`    | [Get related fields data (rowlevelsecurity-related-column-name)](/developer-docs/api/get-related-fields-data-rowlevelsecurity-related-column-name)                      | `/api/v1/rowlevelsecurity/related/{column_name}` |

 </details>

@@ -506,8 +506,8 @@ curl -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \

 | Method | Endpoint                                                             | Description              |
 | ------ | -------------------------------------------------------------------- | ------------------------ |
-| `GET`  | [Export all assets](/developer-docs/6.1.0/api/export-all-assets)           | `/api/v1/assets/export/` |
-| `POST` | [Import multiple assets](/developer-docs/6.1.0/api/import-multiple-assets) | `/api/v1/assets/import/` |
+| `GET`  | [Export all assets](/developer-docs/api/export-all-assets)           | `/api/v1/assets/export/` |
+| `POST` | [Import multiple assets](/developer-docs/api/import-multiple-assets) | `/api/v1/assets/import/` |

 </details>

@@ -516,7 +516,7 @@ curl -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \

 | Method | Endpoint                                                                                                                                 | Description                   |
 | ------ | ---------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------- |
-| `POST` | [Invalidate cache records and remove the database records](/developer-docs/6.1.0/api/invalidate-cache-records-and-remove-the-database-records) | `/api/v1/cachekey/invalidate` |
+| `POST` | [Invalidate cache records and remove the database records](/developer-docs/api/invalidate-cache-records-and-remove-the-database-records) | `/api/v1/cachekey/invalidate` |

 </details>

@@ -525,10 +525,10 @@ curl -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \

 | Method | Endpoint                                                                                       | Description                    |
 | ------ | ---------------------------------------------------------------------------------------------- | ------------------------------ |
-| `GET`  | [Get a list of logs](/developer-docs/6.1.0/api/get-a-list-of-logs)                                   | `/api/v1/log/`                 |
-| `POST` | [Create log](/developer-docs/6.1.0/api/create-log)                                                   | `/api/v1/log/`                 |
-| `GET`  | [Get a log detail information](/developer-docs/6.1.0/api/get-a-log-detail-information)               | `/api/v1/log/{pk}`             |
-| `GET`  | [Get recent activity data for a user](/developer-docs/6.1.0/api/get-recent-activity-data-for-a-user) | `/api/v1/log/recent_activity/` |
+| `GET`  | [Get a list of logs](/developer-docs/api/get-a-list-of-logs)                                   | `/api/v1/log/`                 |
+| `POST` | [Create log](/developer-docs/api/create-log)                                                   | `/api/v1/log/`                 |
+| `GET`  | [Get a log detail information](/developer-docs/api/get-a-log-detail-information)               | `/api/v1/log/{pk}`             |
+| `GET`  | [Get recent activity data for a user](/developer-docs/api/get-recent-activity-data-for-a-user) | `/api/v1/log/recent_activity/` |

 </details>

@@ -539,9 +539,9 @@ curl -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \

 | Method | Endpoint                                                               | Description         |
 | ------ | ---------------------------------------------------------------------- | ------------------- |
-| `GET`  | [Get the user object](/developer-docs/6.1.0/api/get-the-user-object)         | `/api/v1/me/`       |
-| `PUT`  | [Update the current user](/developer-docs/6.1.0/api/update-the-current-user) | `/api/v1/me/`       |
-| `GET`  | [Get the user roles](/developer-docs/6.1.0/api/get-the-user-roles)           | `/api/v1/me/roles/` |
+| `GET`  | [Get the user object](/developer-docs/api/get-the-user-object)         | `/api/v1/me/`       |
+| `PUT`  | [Update the current user](/developer-docs/api/update-the-current-user) | `/api/v1/me/`       |
+| `GET`  | [Get the user roles](/developer-docs/api/get-the-user-roles)           | `/api/v1/me/roles/` |

 </details>

@@ -550,7 +550,7 @@ curl -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \

 | Method | Endpoint                                                       | Description                         |
 | ------ | -------------------------------------------------------------- | ----------------------------------- |
-| `GET`  | [Get the user avatar](/developer-docs/6.1.0/api/get-the-user-avatar) | `/api/v1/user/{user_id}/avatar.png` |
+| `GET`  | [Get the user avatar](/developer-docs/api/get-the-user-avatar) | `/api/v1/user/{user_id}/avatar.png` |

 </details>

@@ -559,7 +559,7 @@ curl -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \

 | Method | Endpoint                                 | Description     |
 | ------ | ---------------------------------------- | --------------- |
-| `GET`  | [Get menu](/developer-docs/6.1.0/api/get-menu) | `/api/v1/menu/` |
+| `GET`  | [Get menu](/developer-docs/api/get-menu) | `/api/v1/menu/` |

 </details>

@@ -568,7 +568,7 @@ curl -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \

 | Method | Endpoint                                                                   | Description                  |
 | ------ | -------------------------------------------------------------------------- | ---------------------------- |
-| `GET`  | [Get all available domains](/developer-docs/6.1.0/api/get-all-available-domains) | `/api/v1/available_domains/` |
+| `GET`  | [Get all available domains](/developer-docs/api/get-all-available-domains) | `/api/v1/available_domains/` |

 </details>

@@ -577,7 +577,7 @@ curl -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \

 | Method | Endpoint                                                                                       | Description            |
 | ------ | ---------------------------------------------------------------------------------------------- | ---------------------- |
-| `GET`  | [Read off of the Redis events stream](/developer-docs/6.1.0/api/read-off-of-the-redis-events-stream) | `/api/v1/async_event/` |
+| `GET`  | [Read off of the Redis events stream](/developer-docs/api/read-off-of-the-redis-events-stream) | `/api/v1/async_event/` |

 </details>

@@ -586,7 +586,7 @@ curl -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \

 | Method | Endpoint                                                                     | Description               |
 | ------ | ---------------------------------------------------------------------------- | ------------------------- |
-| `GET`  | [Get api by version openapi](/developer-docs/6.1.0/api/get-api-by-version-openapi) | `/api/{version}/_openapi` |
+| `GET`  | [Get api by version openapi](/developer-docs/api/get-api-by-version-openapi) | `/api/{version}/_openapi` |

 </details>

@@ -597,12 +597,12 @@ curl -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \

 | Method   | Endpoint                                                                         | Description                     |
 | -------- | -------------------------------------------------------------------------------- | ------------------------------- |
-| `GET`    | [Get security groups](/developer-docs/6.1.0/api/get-security-groups)                   | `/api/v1/security/groups/`      |
-| `POST`   | [Create security groups](/developer-docs/6.1.0/api/create-security-groups)             | `/api/v1/security/groups/`      |
-| `GET`    | [Get security groups info](/developer-docs/6.1.0/api/get-security-groups-info)         | `/api/v1/security/groups/_info` |
-| `DELETE` | [Delete security groups by pk](/developer-docs/6.1.0/api/delete-security-groups-by-pk) | `/api/v1/security/groups/{pk}`  |
-| `GET`    | [Get security groups by pk](/developer-docs/6.1.0/api/get-security-groups-by-pk)       | `/api/v1/security/groups/{pk}`  |
-| `PUT`    | [Update security groups by pk](/developer-docs/6.1.0/api/update-security-groups-by-pk) | `/api/v1/security/groups/{pk}`  |
+| `GET`    | [Get security groups](/developer-docs/api/get-security-groups)                   | `/api/v1/security/groups/`      |
+| `POST`   | [Create security groups](/developer-docs/api/create-security-groups)             | `/api/v1/security/groups/`      |
+| `GET`    | [Get security groups info](/developer-docs/api/get-security-groups-info)         | `/api/v1/security/groups/_info` |
+| `DELETE` | [Delete security groups by pk](/developer-docs/api/delete-security-groups-by-pk) | `/api/v1/security/groups/{pk}`  |
+| `GET`    | [Get security groups by pk](/developer-docs/api/get-security-groups-by-pk)       | `/api/v1/security/groups/{pk}`  |
+| `PUT`    | [Update security groups by pk](/developer-docs/api/update-security-groups-by-pk) | `/api/v1/security/groups/{pk}`  |

 </details>

@@ -611,20 +611,20 @@ curl -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \

 | Method   | Endpoint                                                                                                                                          | Description                             |
 | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------- |
-| `DELETE` | [Bulk delete themes](/developer-docs/6.1.0/api/bulk-delete-themes)                                                                                      | `/api/v1/theme/`                        |
-| `GET`    | [Get a list of themes](/developer-docs/6.1.0/api/get-a-list-of-themes)                                                                                  | `/api/v1/theme/`                        |
-| `POST`   | [Create a theme](/developer-docs/6.1.0/api/create-a-theme)                                                                                              | `/api/v1/theme/`                        |
-| `GET`    | [Get metadata information about this API resource (theme--info)](/developer-docs/6.1.0/api/get-metadata-information-about-this-api-resource-theme-info) | `/api/v1/theme/_info`                   |
-| `DELETE` | [Delete a theme](/developer-docs/6.1.0/api/delete-a-theme)                                                                                              | `/api/v1/theme/{pk}`                    |
-| `GET`    | [Get a theme](/developer-docs/6.1.0/api/get-a-theme)                                                                                                    | `/api/v1/theme/{pk}`                    |
-| `PUT`    | [Update a theme](/developer-docs/6.1.0/api/update-a-theme)                                                                                              | `/api/v1/theme/{pk}`                    |
-| `PUT`    | [Set a theme as the system dark theme](/developer-docs/6.1.0/api/set-a-theme-as-the-system-dark-theme)                                                  | `/api/v1/theme/{pk}/set_system_dark`    |
-| `PUT`    | [Set a theme as the system default theme](/developer-docs/6.1.0/api/set-a-theme-as-the-system-default-theme)                                            | `/api/v1/theme/{pk}/set_system_default` |
-| `GET`    | [Download multiple themes as YAML files](/developer-docs/6.1.0/api/download-multiple-themes-as-yaml-files)                                              | `/api/v1/theme/export/`                 |
-| `POST`   | [Import themes from a ZIP file](/developer-docs/6.1.0/api/import-themes-from-a-zip-file)                                                                | `/api/v1/theme/import/`                 |
-| `GET`    | [Get related fields data (theme-related-column-name)](/developer-docs/6.1.0/api/get-related-fields-data-theme-related-column-name)                      | `/api/v1/theme/related/{column_name}`   |
-| `DELETE` | [Clear the system dark theme](/developer-docs/6.1.0/api/clear-the-system-dark-theme)                                                                    | `/api/v1/theme/unset_system_dark`       |
-| `DELETE` | [Clear the system default theme](/developer-docs/6.1.0/api/clear-the-system-default-theme)                                                              | `/api/v1/theme/unset_system_default`    |
+| `DELETE` | [Bulk delete themes](/developer-docs/api/bulk-delete-themes)                                                                                      | `/api/v1/theme/`                        |
+| `GET`    | [Get a list of themes](/developer-docs/api/get-a-list-of-themes)                                                                                  | `/api/v1/theme/`                        |
+| `POST`   | [Create a theme](/developer-docs/api/create-a-theme)                                                                                              | `/api/v1/theme/`                        |
+| `GET`    | [Get metadata information about this API resource (theme--info)](/developer-docs/api/get-metadata-information-about-this-api-resource-theme-info) | `/api/v1/theme/_info`                   |
+| `DELETE` | [Delete a theme](/developer-docs/api/delete-a-theme)                                                                                              | `/api/v1/theme/{pk}`                    |
+| `GET`    | [Get a theme](/developer-docs/api/get-a-theme)                                                                                                    | `/api/v1/theme/{pk}`                    |
+| `PUT`    | [Update a theme](/developer-docs/api/update-a-theme)                                                                                              | `/api/v1/theme/{pk}`                    |
+| `PUT`    | [Set a theme as the system dark theme](/developer-docs/api/set-a-theme-as-the-system-dark-theme)                                                  | `/api/v1/theme/{pk}/set_system_dark`    |
+| `PUT`    | [Set a theme as the system default theme](/developer-docs/api/set-a-theme-as-the-system-default-theme)                                            | `/api/v1/theme/{pk}/set_system_default` |
+| `GET`    | [Download multiple themes as YAML files](/developer-docs/api/download-multiple-themes-as-yaml-files)                                              | `/api/v1/theme/export/`                 |
+| `POST`   | [Import themes from a ZIP file](/developer-docs/api/import-themes-from-a-zip-file)                                                                | `/api/v1/theme/import/`                 |
+| `GET`    | [Get related fields data (theme-related-column-name)](/developer-docs/api/get-related-fields-data-theme-related-column-name)                      | `/api/v1/theme/related/{column_name}`   |
+| `DELETE` | [Clear the system dark theme](/developer-docs/api/clear-the-system-dark-theme)                                                                    | `/api/v1/theme/unset_system_dark`       |
+| `DELETE` | [Clear the system default theme](/developer-docs/api/clear-the-system-default-theme)                                                              | `/api/v1/theme/unset_system_default`    |

 </details>

@@ -633,14 +633,14 @@ curl -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \

 | Method   | Endpoint                                                                                                                                                                                           | Description                                                  |
 | -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------ |
-| `GET`    | [Get security user registrations](/developer-docs/6.1.0/api/get-security-user-registrations)                                                                                                             | `/api/v1/security/user_registrations/`                       |
-| `POST`   | [Create security user registrations](/developer-docs/6.1.0/api/create-security-user-registrations)                                                                                                       | `/api/v1/security/user_registrations/`                       |
-| `GET`    | [Get security user registrations info](/developer-docs/6.1.0/api/get-security-user-registrations-info)                                                                                                   | `/api/v1/security/user_registrations/_info`                  |
-| `DELETE` | [Delete security user registrations by pk](/developer-docs/6.1.0/api/delete-security-user-registrations-by-pk)                                                                                           | `/api/v1/security/user_registrations/{pk}`                   |
-| `GET`    | [Get security user registrations by pk](/developer-docs/6.1.0/api/get-security-user-registrations-by-pk)                                                                                                 | `/api/v1/security/user_registrations/{pk}`                   |
-| `PUT`    | [Update security user registrations by pk](/developer-docs/6.1.0/api/update-security-user-registrations-by-pk)                                                                                           | `/api/v1/security/user_registrations/{pk}`                   |
-| `GET`    | [Get distinct values from field data (security-user-registrations-distinct-column-name)](/developer-docs/6.1.0/api/get-distinct-values-from-field-data-security-user-registrations-distinct-column-name) | `/api/v1/security/user_registrations/distinct/{column_name}` |
-| `GET`    | [Get related fields data (security-user-registrations-related-column-name)](/developer-docs/6.1.0/api/get-related-fields-data-security-user-registrations-related-column-name)                           | `/api/v1/security/user_registrations/related/{column_name}`  |
+| `GET`    | [Get security user registrations](/developer-docs/api/get-security-user-registrations)                                                                                                             | `/api/v1/security/user_registrations/`                       |
+| `POST`   | [Create security user registrations](/developer-docs/api/create-security-user-registrations)                                                                                                       | `/api/v1/security/user_registrations/`                       |
+| `GET`    | [Get security user registrations info](/developer-docs/api/get-security-user-registrations-info)                                                                                                   | `/api/v1/security/user_registrations/_info`                  |
+| `DELETE` | [Delete security user registrations by pk](/developer-docs/api/delete-security-user-registrations-by-pk)                                                                                           | `/api/v1/security/user_registrations/{pk}`                   |
+| `GET`    | [Get security user registrations by pk](/developer-docs/api/get-security-user-registrations-by-pk)                                                                                                 | `/api/v1/security/user_registrations/{pk}`                   |
+| `PUT`    | [Update security user registrations by pk](/developer-docs/api/update-security-user-registrations-by-pk)                                                                                           | `/api/v1/security/user_registrations/{pk}`                   |
+| `GET`    | [Get distinct values from field data (security-user-registrations-distinct-column-name)](/developer-docs/api/get-distinct-values-from-field-data-security-user-registrations-distinct-column-name) | `/api/v1/security/user_registrations/distinct/{column_name}` |
+| `GET`    | [Get related fields data (security-user-registrations-related-column-name)](/developer-docs/api/get-related-fields-data-security-user-registrations-related-column-name)                           | `/api/v1/security/user_registrations/related/{column_name}`  |

 </details>

@@ -46,43 +46,13 @@ import FAQSchema from '@site/src/components/FAQSchema';
      answer:
        'You need to register a free account at Mapbox.com, obtain an API key, and add it to your .env file at the key MAPBOX_API_KEY.',
    },
-    {
-      question: 'How to limit the timed refresh on a dashboard?',
-      answer:
-        'To exclude specific slices from the timed refresh process, add the timed_refresh_immune_slices key to the dashboard JSON Metadata field with the slice IDs to exclude.',
-    },
-    {
-      question: "Why does 'flask fab' or Superset freeze, hang, or not respond when started (my home directory is NFS mounted)?",
-      answer:
-        'By default, Superset creates and uses an SQLite database at ~/.superset/superset.db. SQLite is known to not work well if used on NFS due to broken file locking. Override the path with the SUPERSET_HOME environment variable or change SQLALCHEMY_DATABASE_URI in superset_config.py.',
-    },
-    {
-      question: 'What if the table schema changed?',
-      answer:
-        'Go to Data -> Datasets, click the edit icon next to the dataset whose schema has changed, and hit Sync columns from source from the Columns tab. The new columns will get merged.',
-    },
    {
      question: 'What database engine can I use as a backend for Superset?',
      answer:
        'Superset is tested using MySQL, PostgreSQL, and SQLite backends for storing its internal metadata. While Superset supports many databases as data sources, only these are recommended for the metadata store in production.',
    },
    {
-      question: 'How can I configure OAuth authentication and authorization?',
-      answer:
-        'Take a look at the Flask-AppBuilder OAuth configuration example, which shows how to configure OAuth authentication and authorization in Superset.',
-    },
-    {
-      question: 'Is there a way to force the dashboard to use specific colors?',
-      answer:
-        'It is possible on a per-dashboard basis by providing a mapping of labels to colors in the JSON Metadata attribute using the label_colors key. You can use a full hex color, a named color, or the index in the current color palette.',
-    },
-    {
-      question: 'How do I expand all chart descriptions on a dashboard by default?',
-      answer:
-        'Add the expand_all_slices key to the dashboard JSON Metadata field with a value of true. Charts that have already been manually expanded or collapsed keep that per-chart override regardless of the setting.',
-    },
-    {
-      question: 'Does Superset work with [insert database engine here]?',
+      question: 'Does Superset work with my database?',
      answer:
        'Superset supports any database with a Python SQLAlchemy dialect and DBAPI driver. Check the Connecting to Databases documentation for the full list of supported databases.',
    },
@@ -91,30 +61,15 @@ import FAQSchema from '@site/src/components/FAQSchema';
      answer:
        'Yes, Superset has a public REST API documented using Swagger. Enable FAB_API_SWAGGER_UI in superset_config.py to access interactive API documentation at /swagger/v1.',
    },
-    {
-      question: 'How can I see usage statistics (e.g., monthly active users)?',
-      answer:
-        'This functionality is not included with Superset, but you can extract and analyze the logs table in Superset\u2019s metadata database to see what actions have occurred.',
-    },
-    {
-      question: 'What does Hours Offset in the Edit Dataset view do?',
-      answer:
-        'In the Edit Dataset view, the hours offset lets you configure the number of hours to be added or subtracted from the time column. This can be used, for example, to convert UTC time to local time.',
-    },
    {
      question: 'Does Superset collect any telemetry data?',
      answer:
        'Superset uses Scarf by default to collect basic telemetry data to help maintainers understand version usage. Users can opt out by setting the SCARF_ANALYTICS environment variable to false.',
    },
    {
-      question: 'Does Superset have an archive panel or trash bin from which a user can recover deleted assets?',
+      question: 'Does Superset have a trash bin to recover deleted assets?',
      answer:
-        'No. Currently, there is no way to recover a deleted Superset dashboard, chart, dataset, or database from the UI. It is recommended to take periodic backups of the metadata database and use export functionality for recovery.',
-    },
-    {
-      question: 'I ran a security scan of the Superset container image and it showed dozens of "high" and "critical" vulnerabilities! Can you release a version of Superset without these?',
-      answer:
-        'These are dependency CVEs in software that Superset uses, mostly in the Linux kernel or Python. Superset addresses them by regularly updating dependencies and welcomes pull requests that fix dependency CVEs. The Superset security team focuses primarily on vulnerabilities in Superset itself.',
+        'No, there is no built-in way to recover deleted dashboards, charts, or datasets. It is recommended to take periodic backups of the metadata database and use export functionality for recovery.',
    },
  ]}
 />
@@ -259,7 +214,8 @@ frontend falls back to a built-in default of `5000` milliseconds.
 SUPERSET_DASHBOARD_MANUAL_REFRESH_STAGGER_MS = 0
 ```

-## Why does `flask fab` or Superset freeze, hang, or not respond when started (my home directory is NFS mounted)?
+**Why does ‘flask fab’ or superset freeze/hang/not responding when started (my home directory is
+NFS mounted)?**

 By default, Superset creates and uses an SQLite database at `~/.superset/superset.db`. SQLite is
 known to [not work well if used on NFS](https://www.sqlite.org/lockingv3.html) due to broken file
@@ -58,7 +58,7 @@ A modern, enterprise-ready business intelligence web application.
 [**Why Superset?**](#why-superset) |
 [**Supported Databases**](#supported-databases) |
 [**Installation and Configuration**](#installation-and-configuration) |
-[**Release Notes**](https://github.com/apache/superset/releases) |
+[**Release Notes**](https://github.com/apache/superset/blob/master/RELEASING/README.md#release-notes-for-recent-releases) |
 [**Get Involved**](#get-involved) |
 [**Contributor Guide**](#contributor-guide) |
 [**Resources**](#resources) |
@@ -328,12 +328,6 @@ Conditional formatting rules highlight cells based on their values. Rules can be

 Each rule has a **"Use gradient"** toggle: enabled applies a varying opacity (lighter = further from threshold), disabled applies a solid fill at full opacity regardless of value.

-For numeric rules, the optional **"Min bound"** / **"Max bound"** fields let you override the auto-detected color range with fixed values instead of relying on the minimum/maximum found in the data — useful when you want consistent coloring across dashboards or data refreshes.
-
-Set **"Bound unit"** to **"% of column"** to express the bounds as percentages of either the column maximum or **"Column sum"**, which adds the absolute values in the column so positive and negative values do not cancel into an unstable denominator. A non-positive maximum or zero sum falls back to the automatic data range. A percentage center based on **"Column sum"** must still resolve inside the color range to activate diverging colors. This option is unavailable with server pagination because the browser only receives one page of rows and cannot calculate a stable full-column denominator; existing percentage rules also use the automatic range while server pagination is enabled.
-
-For a diverging scale, set a **"Center value"** together with **"Low color"**, **"Mid color"**, and **"High color"**. Values below and above the center interpolate toward the corresponding endpoint color. Turning off **"Use gradient"** disables this interpolation and applies the base color as a solid fill.
-
 Each rule's color is set with a full color picker rather than a fixed dropdown of presets. Pick any custom color, or use the **Colors** preset swatches, which reference theme tokens (success, warning, error, and their background variants) so a rule's color updates automatically if the active theme changes, including switching between light and dark mode.

 When a rule targets a column with an active time comparison, a **Trend colors** preset also appears, letting you color cells green for an increase and red for a decrease (or the reverse).
@@ -412,18 +406,6 @@ ECharts option overrides bypass Superset's validation layer. Invalid option keys

 When the **Search Box** is visible in a Table chart, the **Download** action exports only the rows currently visible after the search filter is applied — not the full underlying dataset. This matches the visual output and is intentional. To export the full dataset regardless of search state, use the **Download as CSV** option from the chart's three-dot menu in the dashboard or from the Explore chart toolbar before applying a search filter.

-### Exporting a Chart as an Image or PDF
-
-Alongside the raw-data export options (CSV, JSON, Excel), a chart's three-dot menu — in a dashboard or from the Explore chart toolbar — offers a few ways to export a visual snapshot of the chart:
-
- **Export screenshot (jpeg)** — a single-click JPEG screenshot of the chart.
- **Export screenshot (png)** — opens a submenu with **Transparent background** and **Solid background** options. The solid option uses the current theme's background color. PNG produces a higher-quality image than the JPEG export.
- **Export as PDF** — downloads the chart as a PDF file.
-
-The dropdown menu is briefly hidden while the screenshot or PDF is being captured so it doesn't appear in the exported file. In Explore, these image and PDF options are available from the **Export All Data** submenu, and also from the **Export current view** submenu when the chart type supports current-view export.
-
-These menu items respect your permissions: the dashboard export menu only appears if you can download, and the image/PDF options are disabled if you lack image-export permission.
-
 ### Sharing a Specific Tab

 When a dashboard has tabs, each tab gets its own shareable URL. Navigate to the tab you want to share and copy the URL from your browser's address bar — the tab anchor is encoded in the URL so that anyone opening the link lands directly on that tab.
@@ -88,21 +88,6 @@ embedDashboard({

 If the callback returns `null` or is not provided, Superset uses its own permalink URL as a fallback.

-### Permalink origin rewriting
-
-This rewrite only applies to the non-embedded permalink path — it has no effect on embedded dashboards. When Superset is not embedded, it rewrites the origin of any permalink URL it generates to `window.location.origin` before showing it to the user, which keeps a proxied or subdirectory-deployed Superset from handing out a permalink that points at an internal hostname the user's browser can't reach.
-
-When Superset **is** embedded, this rewrite is skipped entirely regardless of the flag below: a `resolvePermalinkUrl` callback's return value is used as-is, and if no callback is provided (or it fails), the backend-supplied URL is also returned as-is.
-
-If your reverse proxy correctly forwards `X-Forwarded-Host` and you'd rather non-embedded permalinks carry the backend's literal origin, opt out of the rewrite with `EMBEDDED_DISABLE_PERMALINK_ORIGIN_REWRITE`:
-
-```python
-# superset_config.py
-EMBEDDED_DISABLE_PERMALINK_ORIGIN_REWRITE = True
-```
-
-This defaults to `False` (rewrite enabled) and only affects non-embedded permalinks. Flipping the default would regress the common proxied/subdirectory deployment by exposing an unreachable internal host in copied permalinks.
-
 ---

 ## Feature Flags for Embedded Mode
@@ -151,20 +151,6 @@ see some data!
 You should see months in the rows and Department and Travel Class in the columns. Publish this chart
 to your existing Tutorial Dashboard you created earlier.

-:::note
-Row and column totals/subtotals for the Pivot Table are correct even for non-additive metrics,
-such as ratios (`SUM(a)/SUM(b)`), `COUNT_DISTINCT`, `AVG`, and percentiles, not just additive ones
-like `SUM` or `COUNT`. Totals derive client-side, by reducing the same full-detail query results
-used to build the table, only when every selected metric is additive; if any selected metric is
-non-additive, Superset instead issues a database query at each total's own granularity for all
-metrics, so the total reflects each metric's own definition evaluated at that level rather than an
-incorrect combination of the displayed cells. Because of this, there's no separate "Aggregation
-function" control for totals in the Pivot Table: a total always reflects the metric's own
-definition. The Table chart's **Show summary** row is different: its **Summary aggregation**
-control can override a simple metric's own aggregation (to Sum or Average) for the summary row
-only — metrics built from custom SQL keep their own aggregation regardless.
-:::
-
 ### Line Chart

 In this section, we are going to create a line chart to understand the average price of a ticket by
@@ -11,11 +11,6 @@ When soft-delete is enabled, deleting a chart, dashboard, or dataset archives it
 instead of removing it permanently. The **Recently Archived** view lets owners
 and admins find archived objects and restore them.

-A chart used by an alert or report cannot be archived while that dependency
-exists. In the chart list view, the archive confirmation lists the alerts and
-reports that use the chart; a blocked attempt names them and asks you to
-detach or delete them first.
-
 :::note

 This view is gated by the `SOFT_DELETE` feature flag. When the flag is off the
@@ -26,8 +21,7 @@ page and its menu entry are hidden, and deletes are permanent as before.
 ## Finding archived objects

 Open **Recently Archived** and pick a type — **Chart**, **Dashboard**, or
-**Dataset** (shown as **Datasource** when semantic layers are enabled) — from
-the Type selector. The view shows one type at a time; each
+**Dataset** — from the Type selector. The view shows one type at a time; each
 type is read from its own list endpoint, so the same row-level access rules that
 govern the normal lists apply here.

@@ -70,24 +64,5 @@ alert or report is removed, and the reason is shown. Charts that belong to
 dashboards are removed from those dashboards as part of the deletion; the
 dashboards themselves are left in place.

-Before an archived dataset is deleted permanently, Superset checks which
-charts still use it and which dashboards contain those charts. The confirmation
-shows the total number of affected charts and dashboards, identifies the ones
-you are allowed to access, and reports the remaining objects only as restricted
-counts. Restricted names, identifiers, and links are not displayed. Archived
-dependents are included because they can still be recovered after the dataset
-is gone.
-
-Deleting the dataset does not delete those charts or dashboards. They remain
-in place without a usable dataset and may therefore be broken. If there are no
-dependents, the confirmation explicitly reports zero affected charts and
-dashboards.
-
-The dependency check fails closed. While it is loading, or if its result is
-unavailable, permanent deletion is disabled; cancel or retry the check. Superset
-checks again when you submit. If dependencies changed while the confirmation
-was open, the refreshed impact replaces the previous result and you must type
-DELETE again before proceeding.
-
 Objects are also deleted permanently on their own once they have been in the
 archive longer than the retention window, without anyone acting.
@@ -78,18 +78,6 @@ Charts are **not saved by default**. The workflow is intentionally iterative:
 To skip the preview and save immediately, include "and save it" in your prompt.
 :::

-:::info Deployment-specific chart types
-Use `get_chart_type_schema` before generating a chart to discover the types
-available on your Superset instance. Some deployments expose additional
-feature-gated visualizations. For example, a deployment with an AG Grid pivot
-extension enabled can expose `interactive_pivot`, which supports interactive
-row groups, pivot columns, totals, and period-over-period comparisons. Pair
-`comparison_period` (for example, `1 year ago`) with `comparison_type`
-(`values`, `difference`, `percentage`, or `ratio`). It is distinct from the
-built-in `pivot_table` chart type and is not offered when the host visualization
-is unavailable.
-:::
-
 ### Create Dashboards

 Build dashboards from a collection of charts:
@@ -260,12 +248,11 @@ Ask your admin for the MCP server URL and any authentication tokens you need.

 ### Datasets

-| Tool                     | Description                                                                                                                  |
-| ------------------------ | ---------------------------------------------------------------------------------------------------------------------------- |
-| `list_datasets`          | List datasets with filtering and search                                                                                      |
-| `get_dataset_info`       | Get dataset metadata (columns, metrics, schema details)                                                                      |
-| `create_virtual_dataset` | Create a virtual dataset from a SQL query                                                                                    |
-| `update_dataset_metric`  | Update a saved metric's expression, name, verbose_name, or format (affects every chart using it; requires dataset ownership) |
+| Tool                     | Description                                      |
+| ------------------------ | ------------------------------------------------ |
+| `list_datasets`          | List datasets with filtering and search          |
+| `get_dataset_info`       | Get dataset metadata (columns, metrics, filters) |
+| `create_virtual_dataset` | Create a virtual dataset from a SQL query        |

 ### Charts

@@ -15,29 +15,29 @@ description of what changed — "Chart renamed to Q3 Revenue", "Added filter on
 'Region'" — rather than a raw diff. You can search the history and filter it
 down to changes on the entity itself or on the things it depends on.

-## Enabling and disabling it
+## Enabling it
+
+Two switches are involved, and both matter.

 | Setting | Type | Effect |
 | --- | --- | --- |
 | `VERSION_HISTORY` | Feature flag | Shows the version history UI |
 | `ENABLE_VERSIONING_CAPTURE` | Config value | Records versions as entities are saved |

-Both default to on. To turn the feature off:
-
 ```python
 # superset_config.py
-FEATURE_FLAGS = {"VERSION_HISTORY": False}
-ENABLE_VERSIONING_CAPTURE = False
+FEATURE_FLAGS = {"VERSION_HISTORY": True}
+ENABLE_VERSIONING_CAPTURE = True
 ```

-Restart Superset and its workers for the capture change to take effect. Existing
-history remains readable while capture is off, but **Restore** is unavailable
-(404).
+Both default to off. They are separate because capture is the expensive half:
+an operator may want to start recording history before exposing the UI, so that
+there is something to show when they do.

-Disable them together: capture off with the UI left on gives a panel that
-stops filling — an empty or stale history misrepresents the entity as
-unchanged. History only accrues while capture is on; edits made while it was
-off are not reconstructed.
+Turning the UI on without capture gives a panel that reports "No history yet"
+and never fills, so enable capture first — or at the same time. History only
+accrues from the moment capture is switched on; earlier edits are not
+reconstructed.

 ## Viewing history

@@ -0,0 +1,71 @@
+/* eslint-env node */
+/**
+ * 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
+ * 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
+ *
+ *   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
+ * specific language governing permissions and limitations
+ * under the License.
+ */
+const typescriptEslintParser = require('@typescript-eslint/parser');
+const typescriptEslintPlugin = require('@typescript-eslint/eslint-plugin');
+const js = require('@eslint/js');
+const ts = require('typescript-eslint');
+const react = require('eslint-plugin-react');
+const globals = require('globals');
+const { defineConfig, globalIgnores } = require('eslint/config');
+
+module.exports = defineConfig([
+  {
+    files: ['**/*.{js,jsx,ts,tsx}'],
+  },
+  globalIgnores(['build/**/*', '.docusaurus/**/*', 'node_modules/**/*']),
+  js.configs.recommended,
+  ...ts.configs.recommended,
+  {
+    files: ['eslint.config.js'],
+    rules: {
+      '@typescript-eslint/no-require-imports': 'off',
+    },
+  },
+  {
+    languageOptions: {
+      parser: typescriptEslintParser,
+      parserOptions: {
+        ecmaFeatures: {
+          jsx: true,
+        },
+        ecmaVersion: 2020,
+        sourceType: 'module',
+      },
+      globals: {
+        ...globals.browser,
+        ...globals.node,
+      },
+    },
+    plugins: {
+      typescript: typescriptEslintPlugin,
+      react,
+    },
+    rules: {
+      'react/react-in-jsx-scope': 'off',
+      'react/prop-types': 'off',
+      '@typescript-eslint/explicit-module-boundary-types': 'off',
+    },
+    settings: {
+      react: {
+        version: 'detect',
+      },
+    },
+  },
+]);
@@ -1,139 +0,0 @@
-{
-  "$schema": "./node_modules/oxlint/configuration_schema.json",
-  "plugins": [
-    "typescript",
-    "react"
-  ],
-  "categories": {
-    "correctness": "off"
-  },
-  "env": {
-    "builtin": true,
-    "browser": true,
-    "node": true
-  },
-  "ignorePatterns": [
-    "build/**/*",
-    ".docusaurus/**/*",
-    "node_modules/**/*"
-  ],
-  "settings": {
-    "react": {
-      "version": "18.3.1"
-    }
-  },
-  "options": {
-    "typeAware": true
-  },
-  "rules": {
-    "constructor-super": "error",
-    "for-direction": "error",
-    "getter-return": "error",
-    "no-async-promise-executor": "error",
-    "no-case-declarations": "error",
-    "no-class-assign": "error",
-    "no-compare-neg-zero": "error",
-    "no-cond-assign": "error",
-    "no-const-assign": "error",
-    "no-constant-binary-expression": "error",
-    "no-constant-condition": "error",
-    "no-control-regex": "error",
-    "no-debugger": "error",
-    "no-delete-var": "error",
-    "no-dupe-class-members": "error",
-    "no-dupe-else-if": "error",
-    "no-dupe-keys": "error",
-    "no-duplicate-case": "error",
-    "no-empty": "error",
-    "no-empty-character-class": "error",
-    "no-empty-pattern": "error",
-    "no-empty-static-block": "error",
-    "no-ex-assign": "error",
-    "no-extra-boolean-cast": "error",
-    "no-fallthrough": "error",
-    "no-func-assign": "error",
-    "no-global-assign": "error",
-    "no-import-assign": "error",
-    "no-invalid-regexp": "error",
-    "no-irregular-whitespace": "error",
-    "no-loss-of-precision": "error",
-    "no-misleading-character-class": "error",
-    "no-new-native-nonconstructor": "error",
-    "no-nonoctal-decimal-escape": "error",
-    "no-obj-calls": "error",
-    "no-prototype-builtins": "error",
-    "no-redeclare": "error",
-    "no-regex-spaces": "error",
-    "no-self-assign": "error",
-    "no-setter-return": "error",
-    "no-shadow-restricted-names": "error",
-    "no-sparse-arrays": "error",
-    "no-this-before-super": "error",
-    "no-unexpected-multiline": "error",
-    "no-unreachable": "error",
-    "no-unsafe-finally": "error",
-    "no-unsafe-negation": "error",
-    "no-unsafe-optional-chaining": "error",
-    "no-unused-labels": "error",
-    "no-unused-private-class-members": "error",
-    "no-unused-vars": "error",
-    "no-useless-backreference": "error",
-    "no-useless-catch": "error",
-    "no-useless-escape": "error",
-    "no-with": "error",
-    "require-yield": "error",
-    "use-isnan": "error",
-    "valid-typeof": "error",
-    "no-array-constructor": "error",
-    "no-unused-expressions": "error",
-    "typescript/ban-ts-comment": "error",
-    "typescript/no-duplicate-enum-values": "error",
-    "typescript/no-empty-object-type": "error",
-    "typescript/no-explicit-any": "error",
-    "typescript/no-extra-non-null-assertion": "error",
-    "typescript/no-misused-new": "error",
-    "typescript/no-namespace": "error",
-    "typescript/no-non-null-asserted-optional-chain": "error",
-    "typescript/no-require-imports": "error",
-    "typescript/no-this-alias": "error",
-    "typescript/no-unnecessary-type-constraint": "error",
-    "typescript/no-unsafe-declaration-merging": "error",
-    "typescript/no-unsafe-function-type": "error",
-    "typescript/no-wrapper-object-types": "error",
-    "typescript/prefer-as-const": "error",
-    "typescript/prefer-namespace-keyword": "error",
-    "typescript/triple-slash-reference": "error"
-  },
-  "overrides": [
-    {
-      "files": [
-        "**/*.ts",
-        "**/*.tsx",
-        "**/*.mts",
-        "**/*.cts"
-      ],
-      "rules": {
-        "constructor-super": "off",
-        "getter-return": "off",
-        "no-class-assign": "off",
-        "no-const-assign": "off",
-        "no-dupe-class-members": "off",
-        "no-dupe-keys": "off",
-        "no-func-assign": "off",
-        "no-import-assign": "off",
-        "no-new-native-nonconstructor": "off",
-        "no-obj-calls": "off",
-        "no-redeclare": "off",
-        "no-setter-return": "off",
-        "no-this-before-super": "off",
-        "no-unreachable": "off",
-        "no-unsafe-negation": "off",
-        "no-var": "error",
-        "no-with": "off",
-        "prefer-const": "error",
-        "prefer-rest-params": "error",
-        "prefer-spread": "error"
-      }
-    }
-  ]
-}
@@ -29,7 +29,7 @@
    "lint:db-metadata": "python3 ../superset/db_engine_specs/lint_metadata.py",
    "lint:db-metadata:report": "python3 ../superset/db_engine_specs/lint_metadata.py --markdown -o ../superset/db_engine_specs/METADATA_STATUS.md",
    "update:readme-db-logos": "node scripts/generate-database-docs.mjs --update-readme",
-    "lint": "oxlint --config oxlint.json",
+    "eslint": "eslint .",
    "lint:docs-links": "node scripts/lint-docs-links.mjs",
    "version:add": "node scripts/manage-versions.mjs add",
    "version:remove": "node scripts/manage-versions.mjs remove",
@@ -58,15 +58,15 @@
    "@fontsource/inter": "^5.3.0",
    "@mdx-js/react": "^3.1.1",
    "@saucelabs/theme-github-codeblock": "^0.3.0",
-    "@storybook/addon-docs": "^10.5.10",
+    "@storybook/addon-docs": "^10.5.6",
    "@superset-ui/core": "^0.20.4",
-    "@swc/core": "^1.16.1",
-    "antd": "^6.6.2",
-    "baseline-browser-mapping": "^2.11.20",
-    "caniuse-lite": "^1.0.30001810",
-    "docusaurus-plugin-openapi-docs": "^5.2.0",
-    "docusaurus-theme-openapi-docs": "^5.2.0",
-    "js-yaml": "^5.4.1",
+    "@swc/core": "^1.15.47",
+    "antd": "^6.5.3",
+    "baseline-browser-mapping": "^2.11.12",
+    "caniuse-lite": "^1.0.30001806",
+    "docusaurus-plugin-openapi-docs": "^5.1.3",
+    "docusaurus-theme-openapi-docs": "^5.1.3",
+    "js-yaml": "^5.2.3",
    "json-bigint": "^1.0.0",
    "prism-react-renderer": "^2.4.1",
    "react": "^18.3.1",
@@ -76,22 +76,28 @@
    "react-svg-pan-zoom": "^3.13.1",
    "react-table": "^7.8.0",
    "remark-import-partial": "^0.0.2",
-    "reselect": "^5.3.0",
-    "storybook": "^10.5.10",
-    "swagger-ui-react": "^5.32.14",
+    "reselect": "^5.2.0",
+    "storybook": "^10.5.6",
+    "swagger-ui-react": "^5.32.12",
    "swc-loader": "^0.2.7",
    "tinycolor2": "^1.4.2",
    "unist-util-visit": "^5.1.0"
  },
  "devDependencies": {
    "@docusaurus/module-type-aliases": "^3.10.2",
+    "@docusaurus/tsconfig": "^3.10.2",
+    "@eslint/js": "^9.39.2",
    "@types/js-yaml": "^4.0.9",
    "@types/react": "^19.1.8",
-    "oxfmt": "^0.65.0",
-    "oxlint": "^1.80.0",
-    "oxlint-tsgolint": "^7.0.2001",
-    "typescript": "7.0.2",
-    "webpack": "^5.110.1"
+    "@typescript-eslint/eslint-plugin": "^8.66.0",
+    "@typescript-eslint/parser": "^8.66.0",
+    "eslint": "^9.39.2",
+    "eslint-plugin-react": "^7.37.5",
+    "globals": "^17.9.0",
+    "oxfmt": "^0.62.0",
+    "typescript": "~6.0.3",
+    "typescript-eslint": "^8.66.0",
+    "webpack": "^5.109.2"
  },
  "browserslist": {
    "production": [
@@ -287,6 +287,7 @@ def add_missing_operation_ids(spec: dict[str, Any]) -> int:
 TAG_DESCRIPTIONS = {
    "Advanced Data Type": "Advanced data type operations and conversions.",
    "Annotation Layers": "Manage annotation layers and annotations for charts.",
+    "AsyncEventsRestApi": "Real-time event streaming via Server-Sent Events (SSE).",
    "Available Domains": "Get available domains for the Superset instance.",
    "CSS Templates": "Manage CSS templates for custom dashboard styling.",
    "CacheRestApi": "Cache management and invalidation operations.",
@@ -93,6 +93,7 @@ const CATEGORY_GROUPS = {
    'User',
    'Menu',
    'Available Domains',
+    'AsyncEventsRestApi',
    'OpenApi',
  ],
 };
@@ -1,236 +0,0 @@
-<!--
-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
-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
-
-  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
-specific language governing permissions and limitations
-under the License.
-->
-
-# SIP: System-wide MEDIAN, Sample Standard Deviation, and Sample Variance metric aggregates
-
-## [DRAFT — proposal for discussion]
-
-This document now has an accompanying implementation in this PR, for the
-proposed mechanism plus a first, empirically-verified engine set (Postgres,
-MySQL, DuckDB, Redshift by inheritance). It is intended to seed discussion on
-whether this is the right shape and scope before it goes up for a formal SIP
-vote, not to pre-empt that discussion, the code exists so reviewers have a
-concrete design to react to rather than a description of one.
-
-## Motivation
-
-Before #41184 (SIP-216, the non-additive-totals fix), the Pivot Table chart
-exposed an "Aggregation function" control with 18 choices, including
-`Median`, `Sample Standard Deviation`, `Sample Variance`, `First`, `Last`,
-`Count Unique Values`, and `List Unique Values`. #41184 deleted that control
-wholesale, and deliberately so: it re-aggregated already-aggregated cell
-values to compute totals/subtotals, which is exactly the class of bug
-SIP-216 fixed (summing per-group averages, averaging per-group medians, etc.
-produces silently wrong totals). #42761 subsequently restored the one piece
-of that control's functionality that was cleanly separable from the
-correctness bug, the "show as % of row/column/total" display option,
-redesigned as a decoupled, post-hoc-only `showValuesAs` control.
-
-A user has since noticed that several of the other pre-#41184 options never
-came back. Checking today's metric aggregate list (`AVG, COUNT,
-COUNT_DISTINCT, MAX, MIN, SUM`, see
-`superset-frontend/packages/superset-ui-core/src/query/types/Metric.ts`),
-most of these have a reasonable equivalent already: `Count Unique Values`
-maps to `COUNT_DISTINCT`; `Count`/`Average`/`Max`/`Min` are already standard
-aggregates; the two "fraction of" variants are already covered by
-`showValuesAs`. But `Median`, `Sample Standard Deviation`, and `Sample
-Variance` have no equivalent today anywhere in Superset, not just in Pivot
-Table, in any chart type, since the aggregate list is shared across the
-whole app.
-
-This is a real, currently-live gap, not a hypothetical one:
-`superset/mcp_service/chart/chart_utils.py`, `schemas.py`, and
-`prompts/create_chart_guided.py` already treat `STDDEV`, `VAR`, `MEDIAN`,
-and `PERCENTILE` as valid aggregate values in their own validation and
-documentation, but those values are never recognized by
-`superset/connectors/sqla/models.py`'s `sqla_aggregations` dict (the actual
-mapping from aggregate name to SQL), so an AI agent using the MCP tool to
-build a chart with `"aggregate": "STDDEV"` today creates a chart that
-**errors at query time** with "Adhoc metric aggregate is invalid." This SIP
-proposes closing that gap for real, at the source, rather than patching
-around it in MCP.
-
-## Proposed change
-
-Add `MEDIAN`, `STDDEV_SAMP`, and `VAR_SAMP` as first-class, system-wide
-metric aggregates, available anywhere a metric aggregate is chosen (every
-chart type, SQL Lab metric picker, MCP), not as a Pivot-Table-specific
-control.
-
-**Why this is safe with respect to SIP-216, and needs no Pivot-Table-specific
-code at all:** Pivot Table's non-additive-totals machinery
-(`superset-frontend/plugins/plugin-chart-pivot-table/src/plugin/utilities.ts`)
-already classifies any metric aggregate not in `ADDITIVE_AGGREGATES = {SUM,
-COUNT, MIN, MAX}` as non-additive, which routes totals/subtotals through the
-correct DB-`GROUPING SETS`-rollup path rather than client-side
-re-aggregation (`AVG` and `COUNT_DISTINCT` already go through this path
-today). `MEDIAN`/`STDDEV_SAMP`/`VAR_SAMP` fall into that bucket
-automatically, with zero changes needed to the additivity logic. So once
-these are valid, buildable SQL aggregates, Pivot Table (and every other
-chart) gets correct behavior for free. This is the version of "restore the
-control" that does not reopen the bug that was just fixed.
-
-**Where the actual change needs to land, and what this PR does:**
-
-1. **Done.** `superset-frontend/packages/superset-ui-core/src/query/types/Metric.ts`,
-   extended the `Aggregate` type.
-2. **Done.** `superset-frontend/src/explore/constants.ts`, added to `AGGREGATES`
-   (drives `AGGREGATES_OPTIONS`, the dropdown in `AdhocMetricEditPopover`).
-3. **Done**, but not consolidated. `superset/connectors/sqla/models.py`
-   (`sqla_aggregations`) and `superset/models/helpers.py`
-   (`ExploreMixin.sqla_aggregations`) are both wired to consult the new
-   `BaseEngineSpec.get_extended_aggregation_func`, in addition to their
-   existing 6-aggregate dict, so neither's original, already-tested behavior
-   changed. They remain two separate dicts, consolidating them into one
-   source of truth is left as a follow-up (see Open questions).
-4. **Done**, and it surfaced a second, smaller bug on top of the one this SIP
-   opened with: MCP's own aggregate names (`STDDEV`, `VAR`) never matched any
-   real Superset aggregate, before or after this PR, they were always going
-   to error regardless of what this SIP does. `superset/mcp_service/chart/*`
-   now accepts the old shorthand as an alias, normalized to the real,
-   unambiguous names (`STDDEV_SAMP`, `VAR_SAMP`) this PR ships, and the guided
-   prompt text points at the correct names going forward. `MEDIAN`/
-   `PERCENTILE` were already spelled correctly in MCP; `PERCENTILE` remains
-   unimplemented (it needs a parameter this schema has no field for) and is
-   unchanged by this PR, out of scope here.
-
-**The part that needs real engineering care, this must not be a blind
-`sa.func.MEDIAN` / `sa.func.STDDEV_SAMP` / `sa.func.VAR_SAMP`:**
-
-`sqla_aggregations` today is a flat, engine-unaware dict (`sa.func.AVG`,
-etc., SQLAlchemy emits whatever function name it is given, with zero
-validation that the target dialect actually has it). Superset already has
-precedent for exactly this class of per-engine capability difference:
-`BaseEngineSpec.supports_grouping_sets` and `_time_grain_expressions`, both
-introduced by #41184 itself. This SIP proposes the same shape, a new
-per-engine-overridable mechanism (for example
-`BaseEngineSpec.get_aggregate_sql(aggregate, column)` with a sensible
-default, overridden per engine spec where the default does not hold),
-rather than a single hardcoded dict.
-
-Verified findings so far (via `sqlglot.transpile`, cross-checked against
-known engine docs; **not** exhaustively tested against live databases, that
-is necessary follow-up work this SIP alone cannot complete):
-
-| Engine | `MEDIAN(x)` | `STDDEV_SAMP(x)` | `VAR_SAMP(x)` |
-|---|---|---|---|
-| Postgres | `PERCENTILE_CONT(0.5) WITHIN GROUP (ORDER BY x)` | native | native |
-| MySQL | no native equivalent, needs explicit "unsupported" handling, not a blind emit | native | MySQL's `VARIANCE()` is an alias for `VAR_POP` (population), not `VAR_SAMP` (sample); a naive dialect-name substitution would silently compute the wrong statistic and needs an explicit, verified expression instead |
-| SQLite | only if the specific build was compiled with the (non-default) `SQLITE_ENABLE_PERCENTILE` extension (added in SQLite 3.43, 2023), cannot be assumed available | not available in core SQLite | not available in core SQLite |
-| BigQuery / Snowflake / DuckDB / Redshift / Oracle / T-SQL / Databricks / Spark | native `MEDIAN(x)` | native | native on BigQuery/Snowflake/Databricks/Spark, where `VARIANCE` is correctly sample variance; T-SQL has no function named `VARIANCE` at all and needs `VAR(x)` instead |
-| Trino / Presto / Hive | `PERCENTILE_CONT` / `approx_percentile` (dialect- and exactness-dependent) | native | `variance` is correctly sample variance per Trino/Presto docs |
-
-This table is deliberately not exhaustive, Superset has roughly 75
-`db_engine_specs` files. The proposed default (`BaseEngineSpec`) should be
-the safe choice (mark unsupported, surface a clear user-facing error) rather
-than an optimistic one, with individual engine specs opting in once
-verified. Ship for the handful of engines above first, extend
-opportunistically.
-
-**`Count Unique Values`, `First`, `Last`, `List Unique Values`, explicitly
-out of scope for this SIP:**
-
- `Count Unique Values` needs no work, it is already `COUNT_DISTINCT`.
- `First`/`Last` have no well-defined, unambiguous meaning as a plain
-  `GROUP BY` aggregate without an explicit ordering; most engines only
-  support this via window functions (`FIRST_VALUE`/`LAST_VALUE` `OVER
-  (ORDER BY ...)`) or do not support it as a simple aggregate at all
-  (Postgres has neither built in). Restoring this properly would mean
-  designing an "order by" sub-control on the metric, a real, separate
-  feature, not a one-line aggregate addition. Proposed as a follow-up SIP if
-  there is demand.
- `List Unique Values` maps to the `STRING_AGG`/`GROUP_CONCAT`/`LISTAGG`/
-  `ARRAY_AGG(DISTINCT ...)` family, real dialect differences, plus an open
-  UX question (unbounded cell content for high-cardinality columns).
-  Proposed as a follow-up SIP.
-
-## New or changed public interfaces
-
- New `Aggregate` values (`MEDIAN`, `STDDEV_SAMP`, `VAR_SAMP`) selectable
-  anywhere the standard metric control appears, every chart type, not just
-  Pivot Table.
- New `BaseEngineSpec` extensibility point for per-engine aggregate SQL
-  generation (exact shape TBD in implementation, likely mirrors
-  `_time_grain_expressions`).
- No REST API surface changes beyond the existing metric aggregate field
-  accepting new values.
-
-## Migration plan and compatibility
-
-No new tables/columns needed for the aggregate addition itself.
-
-Restoring prior chart settings, the way #42761 restored `show_values_as` for
-charts that had it before #41184, is murkier here than it was for that PR
-and needs its own design pass: the old `aggregate_function` was a single
-Pivot-Table-level setting applied uniformly to every metric on the chart,
-not a per-metric property. A chart that had `aggregate_function: Median`
-before #41184, with a metric of `SUM(sales)`, was already silently wrong
-under the old architecture (that is the bug that was fixed); mechanically
-rewriting its metric to `MEDIAN(sales)` on upgrade would change what the
-chart's leaf cells display, not just its totals, which may not match user
-intent. This SIP proposes a best-effort, flagged-for-review migration
-(surface affected charts to admins rather than silently rewriting them)
-rather than a fully automatic one-to-one restoration.
-
-## Rejected alternatives
-
- **Restoring the old `aggregateFunction` Pivot-Table control as-is.**
-  Rejected: this is the literal mechanism SIP-216 removed because it
-  reintroduces incorrect totals for non-additive metrics. Any fix has to go
-  through the metric's own aggregate, not a separate pivot-level override.
- **Routing all metric SQL generation through `sqlglot` expression-building
-  instead of SQLAlchemy's `sa.func`.** More architecturally thorough (would
-  give correct dialect syntax for free across more of the roughly 75 engine
-  specs), but a much larger, more invasive change to a hot path used by
-  every chart query. Noted as a possible future direction, not this SIP's
-  scope; this SIP proposes the smaller, `supports_grouping_sets`-shaped
-  extensibility point instead.
-
-## Open questions
-
- **Resolved for this PR, worth confirming as the community's preferred
-  shape:** implemented as `BaseEngineSpec._extended_aggregations` (a
-  `{aggregate_name: sqla_column -> sqla_column}` dict) plus a
-  `get_extended_aggregation_func` accessor, set on the concrete or shared
-  base engine spec class per engine (e.g. on `PostgresBaseEngineSpec` so
-  Redshift inherits it, but *not* on `PrestoBaseEngineSpec` so Hive/Spark/
-  Databricks don't silently inherit unverified behavior, mirroring how
-  `supports_grouping_sets` is opted into per-concrete-engine there today).
-  Did not route through the `superset/sql/dialects/` sqlglot-based layer;
-  that layer is for SQL Lab parsing, wiring it into chart-metric query
-  building felt like a separate, larger change from this SIP's scope.
- **Still open, not addressed in this PR:** how aggressively should
-  `MEDIAN` degrade on engines without a native or exact equivalent?
-  Trino/Presto/Hive were left unimplemented (unsupported) specifically to
-  avoid silently answering this with an approximate function
-  (`approx_percentile`) that changes the semantics of what a user asked
-  for. If someone wants `MEDIAN` on those engines, this needs a real
-  decision: require explicit opt-in, show a UI warning, or keep it
-  disallowed.
- **Resolved for this PR:** left the two `sqla_aggregations` dicts
-  (`connectors/sqla/models.py` and `models/helpers.py`) unconsolidated,
-  both now separately wired to the same new `get_extended_aggregation_func`
-  hook. Consolidating them into one source of truth is real but unrelated
-  cleanup, not bundled here to keep the diff reviewable.
- **New, from implementation:** only Postgres, MySQL (partial), DuckDB, and
-  Redshift (by inheritance, unverified) ship enabled. BigQuery, Snowflake,
-  Trino, Presto, Hive, Spark, Databricks, Oracle, and T-SQL all have
-  documented (not live-verified) support per the table above but are not
-  yet wired up, each needs the same live-instance verification treatment
-  before being enabled, this PR intentionally didn't guess.
@@ -67,7 +67,7 @@ const communityLinks = [
      'Join our monthly virtual meetups and register for any upcoming events on Meetup',
  },
  {
-    url: 'https://superset.apache.org/inTheWild/',
+    url: 'https://github.com/apache/superset/blob/master/RESOURCES/INTHEWILD.md',
    title: 'Organizations',
    description:
      'A list of some of the organizations using Superset in production.',
@@ -93,6 +93,12 @@
        "lifecycle": "development",
        "description": "Enable semantic layers and show semantic views alongside datasets"
      },
+      {
+        "name": "SOFT_DELETE",
+        "default": true,
+        "lifecycle": "development",
+        "description": "Temporary rollout / kill-switch gate for soft delete (off = legacy hard delete). An emergency stop, not a clean rollback: flipping ON->OFF resurrects already-soft-deleted rows. Retained through this release as the move-back lever; removed (along with its two gate points \u2014 BaseDAO.delete routing and the do_orm_execute visibility listener) once post-flip confidence is established."
+      },
      {
        "name": "TABLE_V2_TIME_COMPARISON_ENABLED",
        "default": false,
@@ -104,6 +110,12 @@
        "default": false,
        "lifecycle": "development",
        "description": "Enables the tagging system for organizing assets"
+      },
+      {
+        "name": "VERSION_HISTORY",
+        "default": true,
+        "lifecycle": "development",
+        "description": "Enables the version history panel on Explore and Dashboard pages. History only accrues while ``ENABLE_VERSIONING_CAPTURE`` is also on; with capture off the panel renders but stays empty, so the two ship with matching defaults and should be changed together."
      }
    ],
    "testing": [
@@ -120,12 +132,6 @@
        "lifecycle": "testing",
        "description": "Enables filter functionality in Alerts and Reports"
      },
-      {
-        "name": "ALERT_REPORTS_RETRY",
-        "default": false,
-        "lifecycle": "testing",
-        "description": "Enables automatic retry functionality for failed report executions"
-      },
      {
        "name": "ALERT_REPORT_SLACK_V2",
        "default": true,
@@ -227,12 +233,6 @@
        "lifecycle": "testing",
        "description": "Apply RLS rules to SQL Lab queries. Requires query parsing/manipulation. May break queries or allow RLS bypass. Use with care!"
      },
-      {
-        "name": "SOFT_DELETE",
-        "default": true,
-        "lifecycle": "testing",
-        "description": "Temporary rollout / kill-switch gate for soft delete (off = legacy hard delete). An emergency stop, not a clean rollback: flipping ON->OFF resurrects already-soft-deleted rows. Retained through this release as the move-back lever; removed (along with its two gate points \u2014 BaseDAO.delete routing and the do_orm_execute visibility listener) once post-flip confidence is established."
-      },
      {
        "name": "SSH_TUNNELING",
        "default": false,
@@ -245,12 +245,6 @@
        "default": false,
        "lifecycle": "testing",
        "description": "Use analogous colors in charts"
-      },
-      {
-        "name": "VERSION_HISTORY",
-        "default": true,
-        "lifecycle": "testing",
-        "description": "Enables the version history panel on Explore and Dashboard pages. History only accrues while ``ENABLE_VERSIONING_CAPTURE`` is also on; with capture off the panel renders empty or stale history, so the two ship with matching defaults and should be changed together."
      }
    ],
    "stable": [
@@ -1,51 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!-- Generator: Adobe Illustrator 26.2.1, SVG Export Plug-In . SVG Version: 6.00 Build 0)  -->
-<svg version="1.1" id="Layer_1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px"
-	 viewBox="0 0 238 55" style="enable-background:new 0 0 238 55;" xml:space="preserve">
-<path d="M234.9,34.8c-0.9-1.3-2.2-2.2-3.6-2.8c-0.4-0.2-1.2-0.4-2.5-0.8c-1-0.3-1.9-0.6-2.8-1.1c-0.6-0.3-1.1-0.8-1.5-1.4
-	c-0.3-0.6-0.5-1.3-0.5-1.9c0-1,0.4-2,1.1-2.7c0.7-0.7,1.7-1.1,2.8-1.1c1.1-0.1,2.1,0.3,2.9,1c0.8,0.8,1.2,1.8,1.2,2.9h3.6
-	c0-2-0.7-3.9-2.1-5.3c-1.5-1.3-3.4-2-5.4-1.9c-2,0-4,0.7-5.5,2.1c-1.5,1.3-2.3,3.2-2.3,5.2c-0.1,1.5,0.4,3.1,1.3,4.3
-	c0.9,1.1,2.8,2.1,5.8,3.1c1.4,0.4,2.7,1.2,3.8,2.1c0.7,0.8,1.1,1.9,1.1,3c0,1.2-0.5,2.3-1.3,3.1c-0.9,0.8-2.1,1.3-3.3,1.2
-	c-1.4,0-2.6-0.6-3.5-1.6c-1-1.1-1.5-2.6-1.4-4.1V38h-3.5c-0.1,2.4,0.8,4.7,2.4,6.5c1.5,1.6,3.7,2.5,6,2.4c2.2,0.1,4.4-0.7,6.1-2.2
-	c1.6-1.4,2.5-3.5,2.4-5.6C236.2,37.6,235.8,36.1,234.9,34.8z"/>
-<path d="M117,31.4c0.3-2.4,1.5-4.7,3.3-6.4c1.8-1.6,4.1-2.4,6.5-2.4c2.4-0.1,4.8,0.7,6.7,2.2c1.9,1.8,3.1,4.1,3.6,6.6L117,31.4z
-	 M140.9,34.1c0-4.3-1.3-7.9-3.8-10.6s-6.1-4.2-9.8-4.1c-3.7-0.1-7.4,1.3-10,3.9s-4,6.2-3.9,9.9c-0.1,3.7,1.4,7.2,4,9.8
-	c2.5,2.7,6.1,4.1,9.8,4.1c2.7,0.1,5.4-0.8,7.7-2.3c2.3-1.7,4.1-4,5.2-6.7h-3.8c-0.8,1.7-2.1,3.2-3.7,4.2c-1.6,1-3.5,1.6-5.4,1.5
-	c-2.6,0.1-5.1-0.9-7-2.6c-1.9-1.8-3-4.3-3.1-6.9h24L140.9,34.1z"/>
-<path d="M175.1,19.6c-1.9,0-3.7,0.4-5.4,1.2c-1.6,0.8-3,2-4,3.5c-0.9-1.5-2.2-2.6-3.8-3.4c-1.7-0.8-3.6-1.3-5.5-1.3
-	c-1.6,0-3.2,0.3-4.7,0.9c-1.4,0.6-2.6,1.5-3.6,2.6v-2.9h-3.4v26.2h3.3V33.6c0-1.6,0-3.2,0.2-4.8c0.2-0.9,0.4-1.7,0.9-2.4
-	c0.6-1.1,1.6-2,2.8-2.6c1.3-0.6,2.7-1,4.1-0.9c2.6,0,4.5,0.7,5.7,2.2c1.2,1.4,1.9,3.7,1.9,6.7v14.7h3.3V33.6c0-1.6,0-3.2,0.3-4.8
-	c0.2-0.9,0.5-1.7,0.9-2.4c0.6-1.1,1.6-2,2.7-2.6c1.2-0.6,2.6-1,4-0.9c2.6,0,4.5,0.7,5.7,2.2s1.7,3.9,1.7,7.4v13.9h3.3V33.1
-	c0-4.7-0.8-8.2-2.5-10.3S178.7,19.6,175.1,19.6z"/>
-<path d="M193.1,31.4c0.3-2.4,1.5-4.7,3.3-6.4c1.8-1.6,4.1-2.4,6.5-2.4c2.4-0.1,4.9,0.7,6.8,2.2c1.9,1.8,3.1,4.1,3.5,6.6L193.1,31.4z
-	 M216.9,34.1c0-4.3-1.3-7.9-3.8-10.6s-6.1-4.2-9.8-4.1c-3.7-0.1-7.4,1.3-10,3.9s-4,6.2-3.9,9.9c-0.1,3.7,1.4,7.2,4,9.8
-	c2.5,2.7,6.1,4.2,9.8,4.1c2.7,0,5.4-0.8,7.7-2.3c2.3-1.7,4.1-4,5.2-6.7h-3.8c-0.8,1.7-2.1,3.2-3.8,4.2c-1.6,1-3.5,1.5-5.4,1.5
-	c-2.6,0.1-5.2-0.9-7.1-2.6c-1.9-1.8-3-4.3-3.1-6.9h24L216.9,34.1L216.9,34.1z"/>
-<path d="M108.4,20.7c-1.1,0.7-2,1.5-2.7,2.6v-3.1h-3.2v26.2h3.5V30.6c0-2.4,0.5-4.1,1.4-5.2c0.9-1.1,2.4-1.7,4.6-1.9v-3.7
-	C110.6,19.8,109.4,20.1,108.4,20.7z"/>
-<path d="M74.6,31.4c0.3-2.4,1.5-4.7,3.3-6.4c1.8-1.6,4.1-2.4,6.5-2.4c2.4-0.1,4.8,0.7,6.7,2.2c1.9,1.8,3.1,4.1,3.5,6.6L74.6,31.4z
-	 M98.5,34.1c0-4.3-1.3-7.9-3.8-10.6s-6.1-4.2-9.8-4.1c-3.7-0.1-7.4,1.3-10,3.9s-4,6.2-3.9,9.9c-0.1,3.7,1.4,7.2,4,9.8
-	c2.5,2.7,6.1,4.1,9.8,4.1c2.7,0,5.4-0.8,7.7-2.3c2.3-1.7,4.1-4,5.1-6.7h-3.8c-0.8,1.7-2.1,3.2-3.7,4.2s-3.5,1.5-5.4,1.5
-	c-2.6,0.1-5.1-0.9-7-2.6c-1.9-1.8-3-4.3-3.1-6.9h24L98.5,34.1z"/>
-<path d="M47.4,11.7c-1.7-4-4.2-8.4-8.5-10.1C34.2,0,29.1,1,25.4,4.2c-2.7,2.4-4.3,6.1-4.8,11L20.4,16c-0.1,1.3-0.3,2.6-0.3,3.8
-	c-0.8-3.5-0.5-5.9-0.7-9.7c-0.8,0.4-1.2,1.2-1.2,2.1c0,0.2-1-0.4-1.2-0.3c-0.8,0.4-1.6-1-2-1.5c-0.2,0.4-0.4,0.7-0.7,1.1
-	C14,11,13.5,11,13,10.5c-0.4,1-1.6,0.5-2.7,0.5c0.6,1,0.8,2-0.1,2.4c0.1,0.1,0.9,0.3,0.9,0.5c-0.3,0.4-1.3,0-1.8-0.1v0.8
-	c-1.4-0.8-3.7-2.3-2.9,0.9c-1,0.2-0.5,0-0.5,0.9c-0.4,0.1-0.4,0.1-0.4,0.6c-1.2-0.6-2.2,4.9-2.1,6.5c0.9,0.2,1,0.5,1.5,1.4
-	c-0.7,0.3-1.1,1-1.6,1.3L4,26.6c-0.6,0.3-1.1,0.7-1.5,1.3c0.2-0.3,0.6,0.4,0.5,0.3L2.6,28c0.1,0.4,0.3,0.8,0.4,1.2
-	c-0.8,0.3-0.6,0.6-1.1,1.3c0.2,0,0.5,0.1,0.7,0.1c-0.4,0-0.5,1.9-0.4,2.2c0.2-0.4,0.6-0.9,0.8-1.4l0.5,0.5l-0.7,0.6
-	c1.8,0.5-0.2,1.7,0.6,3.1C3.6,34.8,4,34.7,4,33.8l0.4,0.3c-0.2,0.3-1.4,2.6-0.3,2.6c0.1,0,0.1,3.8,0.3,4.8C4.6,41.3,4.8,41,5,40.6
-	c0,0.6,0.3,0.8,0.1,1.5c1.8-0.5,1.1,0.5,0.4,1.4c0.6-0.1,1.2-0.3,1.8-0.5c0.8-0.3,0.1,1.1,0.4,1.1c0.3,0,1.2-1.8,1.4-2.1v0.6
-	c0.4-0.2,1.8-2,2-2c0.2,0.3,0.3,0.7,0.2,1.1c1.6-2,3-4.2,4-6.6c0.1,0.1,0.2,0.2,0.4,0.2c-0.2,0-4.1,7.7-4.1,8.1l0.9-0.2
-	c-0.3,0.6-0.5,1.2-0.6,1.8c1.6-0.2,0.9,1.2,0.9,2.5c1.3-0.8,3.2-1.3,2.5,0.9c0.4-0.2,0.9-0.4,1.3-0.6c-1.1,0.4,0.5,2.6,0.7,3.2
-	c0.2,0.7,2.3,0.2,3,0.4c0.7-1.1,1,0.2,1.2,1.3s1.4-0.6,1.9-0.4c0.4,0.1-0.3,2.7,1.2,1.6c0.6-0.5,0.8,0.4,1.7-0.5
-	c0,0,2.7,0.4,2.6,0.4c0.5-2.6,2.5-0.1,2.2-2.4h0.6c-0.1-2,2,0.9,2-2c0-0.7-1.6-1.5,0.4-0.9c-0.2-0.9,0.2-1.1-0.8-1.3
-	c-0.1-0.2-0.1-0.4,0.1-0.5c0.9,0,2.5,1.7,3.1,0.9c0.2-0.2-0.8-2-0.9-2.5c0.5,0.1,1.1-0.1,1.6,0c-0.9-0.5-0.3-0.6-1.4-0.9
-	c0.9-1.7,2.6-0.1,3.4-1.4c-1.7,0.3-2.6-3.3-1.5-3.6c-0.9-0.8-1.6-1-2.3-1.9c-1.8-2.3,1.7,0.4,2.3,0.9c0-0.4,0.2-0.9,0.2-1.3l0.9,0.8
-	c0-0.2,0.1-0.4,0.1-0.6c0.8,0.7,1.9,1,2.9,0.9c-0.2-0.5,0-0.6-0.2-1.1c0.8,0.2,1.3,0,2.2,0.1c-0.6-1.8,1.5-1.7,2.9-2.1
-	c2.3-0.7-1.4-1-1.6-1.2c-0.4-0.4,0.5-0.9,0.6-0.9s-0.8-1.1-0.6-0.8c-0.3-1-2.6-0.3-0.6-1.6c-0.9-0.2-2.1-0.4-2.1-1.6
-	c0.7-0.1,1.5-0.2,2.2-0.4c-0.5-0.4-0.9-1.1-1.5-1.4l0.5-0.2c-2.8-0.5,0.3-2.7,1-4c-1.9,0.4-2-1.1-3.7-1.3l0.8-0.7
-	c-0.9,0-1.9-0.1-2.8-0.3c0.2-1,0.9-1.9,1.9-2.2c-3.1-1.5-2.4-3.8-5.6-4.7l0.7-0.7c-0.9-1.3-1.6-0.4-2.6-0.7
-	c-2.1-0.6-1.9,2.3-1.9-1.1c0,0.4-0.5-0.4-0.6-0.6c-0.8,0.5-3.4,2.6-3.9,2.1C26.1,12,26,12.2,25.5,13c-0.3,0.3-1.3,0.9-1.1,0.5
-	c-0.6,0.9-0.6,4.3-1.3,6.6c0-1.2,0.2-2.4,0.3-3.6l0.1-0.9c0.4-4.1,1.7-7.1,3.8-8.9c2.8-2.4,6.7-3.1,10.3-2c3.4,1.2,5.5,5.4,7,9.1
-	L57,46.5h2.7l13.2-34.7h-3.5L58.5,41.2L47.4,11.7z"/>
-</svg>
@@ -1,30 +1,14 @@
 {
  // This file is not used in compilation. It is here just for a nice editor experience.
-  // "extends": "@docusaurus/tsconfig",
-  // First compilerOptions section comes from above commented @docusaurus/tsconfig
-  // We moved them here to help with TS v7 migration so whenever Docusaurus readily supports TS v7,
-  // re-install @docusaurus/tsconfig and remove said section.
-  // Commented options are overriden in the next section.
+  "extends": "@docusaurus/tsconfig",
  "compilerOptions": {
-    "allowJs": true,
-    // "esModuleInterop": true,
-    // "jsx": "preserve",
-    "target": "ES2022",
-    "lib": ["ES2022", "DOM"],
-    // "moduleResolution": "bundler",
-    "module": "esnext",
-    "noEmit": true,
-    // "paths": {
-    //   "@site/*": ["./*"]
-    // },
-    // "skipLibCheck": true,
-
+    "baseUrl": ".",
    "ignoreDeprecations": "6.0",
    "skipLibCheck": true,
    "noImplicitAny": false,
    "strict": false,
    "jsx": "react-jsx",
-    "moduleResolution": "bundler",
+    "moduleResolution": "node",
    "resolveJsonModule": true,
    "esModuleInterop": true,
    "types": ["@docusaurus/module-type-aliases"],
@@ -39,10 +23,9 @@
      // Runtime resolution uses webpack alias pointing to actual source (see src/webpack.extend.ts)
      // Using /ui path matches the established pattern used throughout the Superset codebase
      "@apache-superset/core/components": ["./src/types/apache-superset-core"],
-      "@site/*": ["./*"],
-      "*": ["./src/*", "./node_modules/*"]
+      "*": ["src/*", "node_modules/*"]
    }
  },
-  "include": ["./src/**/*.ts", "./src/**/*.tsx", "./src/**/*.d.ts"],
-  "exclude": ["./node_modules", "../superset-frontend/**/*", "src/shims/**"]
+  "include": ["src/**/*.ts", "src/**/*.tsx", "src/**/*.d.ts"],
+  "exclude": ["node_modules", "../superset-frontend/**/*", "src/shims/**"]
 }
@@ -29,7 +29,7 @@ maintainers:
  - name: craig-rueda
    email: craig@craigrueda.com
    url: https://github.com/craig-rueda
-version: 0.22.7 # See [README](https://github.com/apache/superset/blob/master/helm/superset/README.md#versioning) for version details.
+version: 0.22.6 # See [README](https://github.com/apache/superset/blob/master/helm/superset/README.md#versioning) for version details.
 dependencies:
  - name: postgresql
    version: 16.7.27
@@ -23,7 +23,7 @@ NOTE: This file is generated by helm-docs: https://github.com/norwoodj/helm-docs

 # superset

-![Version: 0.22.7](https://img.shields.io/badge/Version-0.22.7-informational?style=flat-square)
+![Version: 0.22.6](https://img.shields.io/badge/Version-0.22.6-informational?style=flat-square)

 Apache Superset is a modern, enterprise-ready business intelligence web application

--- a/Show More
+++ b/Show More