chore(ci): correct setup-python pin comment to match v6.2.0

The pinned SHA a309ff8 resolves to tag v6.2.0, but the inline comment
read "# v6", which zizmor flags as a ref-version-mismatch. Update the
comment to the precise version, matching the rest of the workflows that
use full semver in their pin comments.

Resolves code-scanning alert #2550

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

.github/CODEOWNERS

@@ -1,5 +1,7 @@
 # Notify all committers of DB migration changes, per SIP-59
 
+# https://github.com/apache/superset/issues/13351
+
 /superset/migrations/ @mistercrunch @michael-s-molina @betodealmeida @eschutho @sadpandajoe
 
 # Notify some committers of changes in the components
@@ -10,35 +12,33 @@
 
 # Notify Helm Chart maintainers about changes in it
 
-/helm/superset/ @dpgaspar @villebro @nytai @michael-s-molina @mistercrunch @rusackas @Antonio-RiveroMartnez @hainenber
+/helm/superset/ @craig-rueda @dpgaspar @villebro @nytai @michael-s-molina @mistercrunch @rusackas @Antonio-RiveroMartnez
 
 # Notify E2E test maintainers of changes
 
-/superset-frontend/playwright/ @sadpandajoe @geido @eschutho @rusackas @mistercrunch
-/superset-frontend/cypress-base/ @sadpandajoe @geido @eschutho @rusackas @mistercrunch
+/superset-frontend/cypress-base/ @sadpandajoe @geido @eschutho @rusackas @betodealmeida @mistercrunch
 
 # Notify PMC members of changes to GitHub Actions
 
-/.github/ @villebro @geido @eschutho @rusackas @betodealmeida @nytai @mistercrunch @kgabryje @sha174n @dpgaspar @sadpandajoe @hainenber
+/.github/ @villebro @geido @eschutho @rusackas @betodealmeida @nytai @mistercrunch @craig-rueda @kgabryje @dpgaspar @sadpandajoe @hainenber
 
 # Notify PMC members of changes to CI-executed scripts (supply-chain risk:
 # scripts/ files run directly in CI workflows and can execute arbitrary code)
 
-/scripts/ @villebro @geido @eschutho @rusackas @betodealmeida @nytai @mistercrunch @kgabryje @dpgaspar @sha174n @sadpandajoe @hainenber
+/scripts/ @villebro @geido @eschutho @rusackas @betodealmeida @nytai @mistercrunch @craig-rueda @kgabryje @dpgaspar @sadpandajoe @hainenber
 
 # Notify PMC members of changes to required GitHub Actions
 
-/.asf.yaml @villebro @geido @eschutho @rusackas @betodealmeida @nytai @mistercrunch @kgabryje @dpgaspar @sha174n @Antonio-RiveroMartnez
+/.asf.yaml @villebro @geido @eschutho @rusackas @betodealmeida @nytai @mistercrunch @craig-rueda @kgabryje @dpgaspar @Antonio-RiveroMartnez
 
 # Maps are a finicky contribution process we care about
 
 **/*.geojson @villebro @rusackas
-**/*.ipynb @villebro @rusackas
 /superset-frontend/plugins/legacy-plugin-chart-country-map/ @villebro @rusackas
 
 # Notify translation maintainers of changes to translations
 
-/superset/translations/ @sfirke @rusackas @villebro @sadpandajoe @hainenber
+/superset/translations/ @sfirke @rusackas
 
 # Notify PMC members of changes to extension-related files
 

.github/actions/setup-backend/action.yml

@@ -42,7 +42,7 @@ runs:
         fi
         echo "python-version=$RESOLVED_VERSION" >> "$GITHUB_OUTPUT"
     - name: Set up Python ${{ steps.set-python-version.outputs.python-version }}
-      uses: actions/setup-python@a309ff8b426b58ec0e2a45f0f869d46889d02405 # v6.2.0
+      uses: actions/setup-python@a309ff8b426b58ec0e2a45f0f869d46889d02405 # v6
       with:
         python-version: ${{ steps.set-python-version.outputs.python-version }}
         cache: ${{ inputs.cache }}

.github/actions/setup-supersetbot/action.yml

@@ -17,7 +17,6 @@ runs:
     - name: Install supersetbot from npm
       if: ${{ inputs.from-npm == 'true' }}
       shell: bash
-      # zizmor: ignore[adhoc-packages] - supersetbot is a first-party Apache CLI (apache-superset/supersetbot) installed globally as a tool; a global CLI install has no application manifest/lockfile context
       run: npm install -g supersetbot
 
     - name: "Checkout ${{ github.ref }} ( ${{ github.sha }} )"
@@ -32,7 +31,6 @@ runs:
       if: ${{ inputs.from-npm == 'false' }}
       shell: bash
       working-directory: supersetbot
-      # zizmor: ignore[adhoc-packages] - installs the locally packed supersetbot tarball built from the trusted apache-superset/supersetbot checkout; no lockfile applies to a global CLI install
       run: |
         # simple trick to install globally with dependencies
         npm pack

.github/dependabot.yml

@@ -10,7 +10,11 @@ updates:
 
   - package-ecosystem: "npm"
     ignore:
+      - dependency-name: "react-error-boundary"
       - dependency-name: "@rjsf/*"
+      # remark-gfm v4+ requires react-markdown v9+, which needs React 18
+      - dependency-name: "remark-gfm"
+      - dependency-name: "react-markdown"
       # TODO: remove below entries until React >= 19.0.0
       - dependency-name: "react-icons"
       # JSDOM v30 doesn't play well with Jest v30
@@ -28,13 +32,6 @@ updates:
       # and confirm the issue https://github.com/apache/superset/issues/39600 is fixed
       - dependency-name: "react-checkbox-tree"
         update-types: ["version-update:semver-major"]
-      # Babel 8 (7.x -> 8.x) is blocked on the surrounding ecosystem: @emotion/babel-plugin
-      # (NodePath#hoist), babel-plugin-jsx-remove-data-test-id (t.jSXOpeningElement), and
-      # ts-jest all rely on Babel APIs removed in v8 and have not shipped Babel 8 support.
-      # Ignore the coordinated major bump until the ecosystem catches up; it must be done
-      # as a single manual upgrade anyway. TODO: remove when Babel 8 support is viable.
-      - dependency-name: "@babel/*"
-        update-types: ["version-update:semver-major"]
     directory: "/superset-frontend/"
     schedule:
       interval: "daily"
@@ -74,6 +71,8 @@ updates:
 
   - package-ecosystem: "npm"
     directory: "/docs/"
+    ignore:
+      - dependency-name: "react-error-boundary"
     schedule:
       interval: "daily"
     open-pull-requests-limit: 10
@@ -370,6 +369,11 @@ updates:
 
   - package-ecosystem: "npm"
     directory: "/superset-frontend/packages/superset-ui-core/"
+    ignore:
+      # not until React >= 18.0.0
+      - dependency-name: "react-markdown"
+      - dependency-name: "remark-gfm"
+      - dependency-name: "react-error-boundary"
     schedule:
       interval: "daily"
     labels:

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

@@ -40,7 +40,7 @@ jobs:
         uses: ./.github/actions/setup-supersetbot/
 
       - name: Set up Python ${{ inputs.python-version }}
-        uses: actions/setup-python@ece7cb06caefa5fff74198d8649806c4678c61a1 # v6.3.0
+        uses: actions/setup-python@a309ff8b426b58ec0e2a45f0f869d46889d02405 # v6.2.0
         with:
           python-version: "3.10"
 

.github/workflows/codeql-analysis.yml

@@ -64,7 +64,7 @@ jobs:
 
       # Initializes the CodeQL tools for scanning.
       - name: Initialize CodeQL
-        uses: github/codeql-action/init@8aad20d150bbac5944a9f9d289da16a4b0d87c1e # v4.36.2
+        uses: github/codeql-action/init@8aad20d150bbac5944a9f9d289da16a4b0d87c1e # v4
         with:
           languages: ${{ matrix.language }}
           # If you wish to specify custom queries, you can do so here or in a config file.
@@ -75,6 +75,6 @@ jobs:
           # queries: security-extended,security-and-quality
 
       - name: Perform CodeQL Analysis
-        uses: github/codeql-action/analyze@8aad20d150bbac5944a9f9d289da16a4b0d87c1e # v4.36.2
+        uses: github/codeql-action/analyze@8aad20d150bbac5944a9f9d289da16a4b0d87c1e # v4
         with:
           category: "/language:${{matrix.language}}"

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

@@ -37,7 +37,7 @@ jobs:
           persist-credentials: false
           submodules: recursive
       - name: Setup Java
-        uses: actions/setup-java@1bcf9fb12cf4aa7d266a90ae39939e61372fe520 # v5.4.0
+        uses: actions/setup-java@ad2b38190b15e4d6bdf0c97fb4fca8412226d287 # v5.3.0
         with:
           distribution: "temurin"
           java-version: "11"

.github/workflows/github-action-validator.yml

@@ -37,13 +37,10 @@ jobs:
           node-version: "20"
 
       - name: Install Dependencies
-        # Versions are pinned to avoid ad-hoc, unpinned package installs.
-        # Bump deliberately when upgrading.
-        # zizmor: ignore[adhoc-packages] - @action-validator is a global CLI tool installed to validate the repo's workflows; a global CLI install has no application manifest/lockfile context, and the versions are pinned above
-        run: npm install -g @action-validator/core@0.6.0 @action-validator/cli@0.6.0
+        run: npm install -g @action-validator/core @action-validator/cli --save-dev
 
       - name: Run Script
         run: bash .github/workflows/github-action-validator.sh
 
       - name: Check for security issues on GHA workflows
-        uses: zizmorcore/zizmor-action@192e21d79ab29983730a13d1382995c2307fbcaa # v0.5.7
+        uses: zizmorcore/zizmor-action@5f14fd08f7cf1cb1609c1e344975f152c7ee938d # v0.5.6

.github/workflows/license-check.yml

@@ -23,7 +23,7 @@ jobs:
           persist-credentials: false
           submodules: recursive
       - name: Setup Java
-        uses: actions/setup-java@1bcf9fb12cf4aa7d266a90ae39939e61372fe520 # v5.4.0
+        uses: actions/setup-java@ad2b38190b15e4d6bdf0c97fb4fca8412226d287 # v5.3.0
         with:
           distribution: "temurin"
           java-version: "11"

.github/workflows/pre-commit.yml

@@ -32,18 +32,19 @@ jobs:
         with:
           persist-credentials: false
           submodules: recursive
-
       - name: Setup Python
         uses: ./.github/actions/setup-backend/
         with:
           python-version: ${{ matrix.python-version }}
-
-      - name: Setup Go
-        uses: actions/setup-go@924ae3a1cded613372ab5595356fb5720e22ba16 # v6.5.0
-
-      - name: Install helm-docs
-        run: go install github.com/norwoodj/helm-docs/cmd/helm-docs@v1.14.2
-
+      - name: Enable brew and helm-docs
+        # Add brew to the path - see https://github.com/actions/runner-images/issues/6283
+        run: |
+          echo "/home/linuxbrew/.linuxbrew/bin:/home/linuxbrew/.linuxbrew/sbin" >> $GITHUB_PATH
+          eval "$(/home/linuxbrew/.linuxbrew/bin/brew shellenv)"
+          echo "HOMEBREW_PREFIX=$HOMEBREW_PREFIX" >>"${GITHUB_ENV}"
+          echo "HOMEBREW_CELLAR=$HOMEBREW_CELLAR" >>"${GITHUB_ENV}"
+          echo "HOMEBREW_REPOSITORY=$HOMEBREW_REPOSITORY" >>"${GITHUB_ENV}"
+          brew install norwoodj/tap/helm-docs
       - name: Setup Node.js
         uses: actions/setup-node@48b55a011bda9f5d6aeb4c2d9c7362e8dae4041e # v6
         with:
@@ -62,7 +63,7 @@ jobs:
           yarn install --immutable
 
       - name: Cache pre-commit environments
-        uses: actions/cache@55cc8345863c7cc4c66a329aec7e433d2d1c52a9 # v6.1.0
+        uses: actions/cache@27d5ce7f107fe9357f9df03efb73ab90386fccae # v5
         with:
           path: ~/.cache/pre-commit
           key: pre-commit-v2-${{ runner.os }}-py${{ matrix.python-version }}-${{ hashFiles('.pre-commit-config.yaml') }}

.github/workflows/release.yml

@@ -56,7 +56,7 @@ jobs:
 
       - name: Cache npm
         if: env.HAS_TAGS
-        uses: actions/cache@55cc8345863c7cc4c66a329aec7e433d2d1c52a9 # v6.1.0
+        uses: actions/cache@27d5ce7f107fe9357f9df03efb73ab90386fccae # v5
         with:
           path: ~/.npm # npm cache files are stored in `~/.npm` on Linux/macOS
           key: ${{ runner.OS }}-node-${{ hashFiles('**/package-lock.json') }}
@@ -70,7 +70,7 @@ jobs:
         run: echo "dir=$(npm config get cache)" >> $GITHUB_OUTPUT
       - name: Cache npm
         if: env.HAS_TAGS
-        uses: actions/cache@55cc8345863c7cc4c66a329aec7e433d2d1c52a9 # v6.1.0
+        uses: actions/cache@27d5ce7f107fe9357f9df03efb73ab90386fccae # v5
         id: npm-cache # use this to check for `cache-hit` (`steps.npm-cache.outputs.cache-hit != 'true'`)
         with:
           path: ${{ steps.npm-cache-dir-path.outputs.dir }}

.github/workflows/scheduled-docker-image-refresh.yml

@@ -1,177 +0,0 @@
-name: Scheduled Docker image refresh
-
-# Re-runs the Docker image build against the latest published release on a
-# weekly cadence. The code being built doesn't change — but the base image
-# layers (python:*-slim-trixie and its OS packages) DO get upstream
-# security patches between Superset releases, and those patches don't
-# reach our published images unless we rebuild.
-#
-# Without this workflow, `apache/superset:<latest>` lags behind upstream
-# Debian/Python base patches by whatever interval falls between Superset
-# releases (typically 3–6 weeks). With it, the lag drops to at most one
-# week regardless of release cadence.
-#
-# This is a security-hygiene cron, not a release. It overwrites the
-# existing tags for the most recent release (e.g. `apache/superset:5.0.0`
-# and `apache/superset:latest`) with bit-for-bit-equivalent contents
-# layered on a refreshed base. Image digests change; everything users
-# actually pin against (image content, code, deps) does not.
-
-on:
-  schedule:
-    # Mondays at 06:00 UTC — gives the weekend for upstream patches to
-    # settle and surfaces failures at the start of the work week so a
-    # human can react.
-    - cron: "0 6 * * 1"
-
-  # Manual trigger so operators can force a refresh on demand (e.g.
-  # immediately after a high-severity base-image CVE drops).
-  workflow_dispatch: {}
-
-permissions:
-  contents: read
-
-# Serialize with itself and with the release publisher (tag-release.yml) —
-# both push to the same Docker Hub tags, so a race could end with stale
-# layers winning. Both workflows must declare this group for the lock to work.
-concurrency:
-  group: docker-publish-latest-release
-  cancel-in-progress: false
-
-jobs:
-  config:
-    runs-on: ubuntu-24.04
-    outputs:
-      has-secrets: ${{ steps.check.outputs.has-secrets }}
-      latest-release: ${{ steps.latest.outputs.tag }}
-      force-latest: ${{ steps.latest.outputs.force-latest }}
-    steps:
-      - name: Check for Docker Hub secrets
-        id: check
-        shell: bash
-        run: |
-          if [ -n "${DOCKERHUB_USER}" ]; then
-            echo "has-secrets=1" >> "$GITHUB_OUTPUT"
-          fi
-        env:
-          DOCKERHUB_USER: ${{ (secrets.DOCKERHUB_USER != '' && secrets.DOCKERHUB_TOKEN != '') || '' }}
-
-      - name: Look up latest published release
-        id: latest
-        shell: bash
-        env:
-          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-          REPOSITORY: ${{ github.repository }}
-        run: |
-          # `releases/latest` returns the latest non-prerelease, non-draft
-          # release — which is exactly what `apache/superset:latest`
-          # should reflect.
-          TAG=$(gh api "repos/${REPOSITORY}/releases/latest" --jq .tag_name)
-          if [ -z "$TAG" ] || [ "$TAG" = "null" ]; then
-            echo "::error::Could not determine latest release tag"
-            exit 1
-          fi
-          echo "Latest release: $TAG"
-          echo "tag=$TAG" >> "$GITHUB_OUTPUT"
-
-          # Only move `:latest` when the release flagged "latest" is also the
-          # highest semver release. This guards against a mis-click leaving an
-          # older maintenance release (e.g. a 5.x patch shipped after 6.0 GA)
-          # marked latest, which would otherwise roll `:latest` back a major
-          # version on the next cron run. If it isn't the newest, we still
-          # refresh that release's own version tag but leave `:latest` alone.
-          HIGHEST=$(gh api --paginate "repos/${REPOSITORY}/releases" \
-            --jq '.[] | select(.draft|not) | select(.prerelease|not) | .tag_name' \
-            | sed 's/^v//' | sort -V | tail -n1)
-          if [ "${TAG#v}" = "$HIGHEST" ]; then
-            echo "force-latest=1" >> "$GITHUB_OUTPUT"
-          else
-            echo "::warning::Latest-flagged release $TAG is not the highest semver ($HIGHEST); refreshing its version tag but leaving :latest untouched"
-          fi
-
-  docker-rebuild:
-    needs: config
-    if: needs.config.outputs.has-secrets == '1'
-    name: docker-rebuild
-    runs-on: ubuntu-24.04
-    strategy:
-      # Mirror the same matrix the release publisher uses so every variant
-      # operators consume from Docker Hub gets the refreshed base.
-      matrix:
-        build_preset: ["dev", "lean", "py310", "websocket", "dockerize", "py311", "py312"]
-      fail-fast: false
-    steps:
-      - name: "Checkout release tag: ${{ needs.config.outputs.latest-release }}"
-        uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
-        with:
-          ref: ${{ needs.config.outputs.latest-release }}
-          fetch-depth: 0
-          persist-credentials: false
-
-      - name: Setup Docker Environment
-        uses: ./.github/actions/setup-docker
-        with:
-          dockerhub-user: ${{ secrets.DOCKERHUB_USER }}
-          dockerhub-token: ${{ secrets.DOCKERHUB_TOKEN }}
-          install-docker-compose: "false"
-          build: "true"
-
-      - name: Use Node.js 20
-        uses: actions/setup-node@48b55a011bda9f5d6aeb4c2d9c7362e8dae4041e # v6
-        with:
-          node-version: 20
-
-      - name: Setup supersetbot
-        uses: ./.github/actions/setup-supersetbot/
-
-      - name: Rebuild and push
-        env:
-          DOCKERHUB_USER: ${{ secrets.DOCKERHUB_USER }}
-          DOCKERHUB_TOKEN: ${{ secrets.DOCKERHUB_TOKEN }}
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-          BUILD_PRESET: ${{ matrix.build_preset }}
-          LATEST_RELEASE: ${{ needs.config.outputs.latest-release }}
-          FORCE_LATEST_FLAG: ${{ needs.config.outputs.force-latest == '1' && '--force-latest' || '' }}
-        run: |
-          # Reuses the same supersetbot invocation as the release
-          # publisher (`tag-release.yml`), so the resulting tags are
-          # identical to what a manual release dispatch would produce —
-          # just with a freshly-pulled base image layer underneath.
-          # `--force-latest` is only passed when the config job confirmed the
-          # fetched release is the newest one (see FORCE_LATEST_FLAG above).
-          supersetbot docker \
-            --push \
-            --preset "$BUILD_PRESET" \
-            --context release \
-            --context-ref "$LATEST_RELEASE" \
-            $FORCE_LATEST_FLAG \
-            --platform "linux/arm64" \
-            --platform "linux/amd64"
-
-  # The whole point of this cron is catching base-image CVEs, so a silent
-  # failure is the expensive case — a red X in the Actions tab nobody is
-  # watching on a Monday. File a tracked issue when any rebuild leg fails so
-  # a missed security refresh surfaces instead of sitting unnoticed.
-  notify-on-failure:
-    needs: [config, docker-rebuild]
-    if: failure() && needs.config.outputs.has-secrets == '1'
-    runs-on: ubuntu-24.04
-    permissions:
-      contents: read
-      issues: write
-    steps:
-      - name: Open a tracking issue
-        env:
-          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-          REPOSITORY: ${{ github.repository }}
-          LATEST_RELEASE: ${{ needs.config.outputs.latest-release }}
-          RUN_URL: ${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}
-        run: |
-          gh issue create \
-            --repo "$REPOSITORY" \
-            --title "Scheduled Docker image refresh failed for ${LATEST_RELEASE}" \
-            --label "infra:container" \
-            --label "bug" \
-            --body "The weekly Docker base-image refresh failed for release \`${LATEST_RELEASE}\`. Published images may be missing upstream base-layer security patches until this is resolved.
-
-          Failed run: ${RUN_URL}"

.github/workflows/showtime-cleanup.yml

@@ -24,14 +24,13 @@ jobs:
 
     permissions:
       contents: read
-      issues: write        # delete orphaned showtime label definitions (label CRUD is the issues API)
       pull-requests: write
 
     steps:
       - name: Install Superset Showtime
         run: pip install superset-showtime
 
-      - name: Cleanup expired environments and orphaned labels
+      - name: Cleanup expired environments
         run: |
-          echo "Cleaning up environments respecting TTL labels, and pruning orphaned 🎪 labels"
-          python -m showtime cleanup --respect-ttl --force
+          echo "Cleaning up environments respecting TTL labels"
+          python -m showtime cleanup --respect-ttl

.github/workflows/showtime-trigger.yml

@@ -2,8 +2,7 @@ name: 🎪 Superset Showtime
 
 # Ultra-simple: just sync on any PR state change
 on:
-  # zizmor: ignore[dangerous-triggers] - required to react to PR label changes; PR code is
-  # only checked out and built after the maintainer-authorization gate (write/admin actors)
+  # zizmor: ignore[dangerous-triggers] - required to react to PR label changes; this workflow does not check out or execute PR-provided code
   pull_request_target:
     types: [labeled, unlabeled, synchronize, closed]
 
@@ -157,10 +156,6 @@ jobs:
         with:
           ref: ${{ steps.check.outputs.target_sha }}
           persist-credentials: false
-          # Building fork PR code is Showtime's purpose: deploys are gated on the
-          # maintainer-authorization step above (write/admin actors only), so this
-          # checkout is an explicit, authorized opt-in rather than an automatic one.
-          allow-unsafe-pr-checkout: true
 
       - name: Setup Docker Environment (only if build needed)
         if: steps.auth.outputs.authorized == 'true' && steps.check.outputs.build_needed == 'true'

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

@@ -71,7 +71,7 @@ jobs:
           node-version-file: "./docs/.nvmrc"
       - name: Setup Python
         uses: ./.github/actions/setup-backend/
-      - uses: actions/setup-java@1bcf9fb12cf4aa7d266a90ae39939e61372fe520 # v5.4.0
+      - uses: actions/setup-java@ad2b38190b15e4d6bdf0c97fb4fca8412226d287 # v5.3.0
         with:
           distribution: "zulu"
           java-version: "21"

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

@@ -26,7 +26,7 @@ jobs:
           fetch-depth: 0
 
       - name: Set up Helm
-        uses: azure/setup-helm@9bc31f4ebc9c6b171d7bfbaa5d006ae7abdb4310 # v5.0.1
+        uses: azure/setup-helm@dda3372f752e03dde6b3237bc9431cdc2f7a02a2 # v5.0.0
         with:
           version: v3.16.4
 

.github/workflows/superset-helm-release.yml

@@ -42,7 +42,7 @@ jobs:
           git config user.email "$GITHUB_ACTOR@users.noreply.github.com"
 
       - name: Install Helm
-        uses: azure/setup-helm@9bc31f4ebc9c6b171d7bfbaa5d006ae7abdb4310 # v5.0.1
+        uses: azure/setup-helm@dda3372f752e03dde6b3237bc9431cdc2f7a02a2 # v5.0.0
         with:
           version: v3.5.4
 

.github/workflows/superset-websocket.yml

@@ -28,10 +28,6 @@ jobs:
         uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
         with:
           persist-credentials: false
-      - name: Setup Node.js
-        uses: actions/setup-node@48b55a011bda9f5d6aeb4c2d9c7362e8dae4041e # v6.4.0
-        with:
-          node-version-file: './superset-websocket/.nvmrc'
       - name: Install dependencies
         working-directory: ./superset-websocket
         run: npm ci

.github/workflows/tag-release.yml

@@ -24,12 +24,6 @@ on:
 permissions:
   contents: read
 
-# Serialize with the scheduled Docker image refresh — both workflows push
-# to the same Docker Hub tags and must not race on apache/superset:latest.
-concurrency:
-  group: docker-publish-latest-release
-  cancel-in-progress: false
-
 jobs:
   config:
     runs-on: ubuntu-24.04

Dockerfile

@@ -120,7 +120,7 @@ RUN useradd --user-group -d ${SUPERSET_HOME} -m --no-log-init --shell /bin/bash
 # Some bash scripts needed throughout the layers
 COPY --chmod=755 docker/*.sh /app/docker/
 
-RUN pip install --no-cache-dir --upgrade uv
+COPY --from=ghcr.io/astral-sh/uv:latest /uv /usr/local/bin/uv
 
 # Using uv as it's faster/simpler than pip
 RUN uv venv /app/.venv
@@ -141,7 +141,7 @@ RUN --mount=type=cache,target=/root/.cache/uv \
 
 COPY superset/translations/ /app/translations_mo/
 RUN if [ "${BUILD_TRANSLATIONS}" = "true" ]; then \
-        pybabel compile --use-fuzzy -d /app/translations_mo || true; \
+        pybabel compile -d /app/translations_mo | true; \
     fi; \
     rm -f /app/translations_mo/*/*/*.[po,json]
 

README.md

@@ -247,13 +247,16 @@ Understanding the Superset Points of View
 
 - [Superset API](https://superset.apache.org/docs/rest-api)
 
-<!--
-  The OSS Insight "Repo Activity" widget (https://next.ossinsight.io/) was
-  intentionally removed. This README is rendered on the ASF-hosted website
-  (superset.apache.org), so its contents are subject to ASF's third-party
-  content and CSP rules. OSS Insight has no Data Processing Agreement (DPA)
-  with the ASF, so we cannot embed its images/widgets here. Do not re-add it.
--->
+## Repo Activity
+
+<a href="https://next.ossinsight.io/widgets/official/compose-last-28-days-stats?repo_id=39464018" target="_blank" align="center">
+  <picture>
+    <source media="(prefers-color-scheme: dark)" srcset="https://next.ossinsight.io/widgets/official/compose-last-28-days-stats/thumbnail.png?repo_id=39464018&image_size=auto&color_scheme=dark" width="655" height="auto" />
+    <img alt="Performance Stats of apache/superset - Last 28 days" src="https://next.ossinsight.io/widgets/official/compose-last-28-days-stats/thumbnail.png?repo_id=39464018&image_size=auto&color_scheme=light" width="655" height="auto" />
+  </picture>
+</a>
+
+<!-- Made with [OSS Insight](https://ossinsight.io/) -->
 
 <!-- telemetry/analytics pixel: -->
 <img referrerpolicy="no-referrer-when-downgrade" src="https://static.scarf.sh/a.png?x-pxid=bc1c90cd-bc04-4e11-8c7b-289fb2839492" />

SIP-DASHBOARD-COMPONENT-CONTRIBUTION-POINT.md

@@ -1,262 +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] Proposal for a dashboard component Extensions contribution point
-
-> **Companion SIP:** Pairs with [`SIP.md`](SIP.md) (first-class iframe component +
-> runtime CSP allowlist). That SIP is the **reference implementation** that proves
-> this contribution point: the iframe's UI becomes an extension-contributed
-> dashboard component, while its security-sensitive CSP backend stays in core.
->
-> **Status:** Draft — POC tracked in `feat/csp-runtime-allowlist-iframe`.
-
-## Motivation
-
-Adding a new dashboard layout component to Superset today is a **core-only,
-high-friction** operation. The iframe component in the companion SIP had to touch
-~12 files: a type constant, the `componentLookup` map, the builder palette, and
-**seven hardcoded behavior maps** keyed by component-type string
-(`isValidChild`, `componentIsResizable`, `newComponentFactory`,
-`shouldWrapChildInRow`, `getDetailedComponentWidth`, `isDashboardEmpty`, plus the
-prop bundle injected by `DashboardComponent.tsx`). Component types are a **closed
-enum** baked into core.
-
-There is a legacy escape hatch — the `DashboardComponentsRegistry` /
-`DYNAMIC_TYPE` path (`src/visualizations/dashboardComponents/`) — but it is an
-**antique that should be deprecated**:
-
-- It is disconnected from the modern VS Code-style Extensions framework
-  (`@apache-superset/core`, `ENABLE_EXTENSIONS`), which already has contribution
-  points for `commands`, `menus`, `views`, `editors`, and `chat`.
-- Components registered through it are **second-class**: `DynamicComponent`
-  renders them in a generic wrapper that only passes `dashboardData`. They do not
-  receive the first-class layout lifecycle (edit mode, meta editing, resize, DnD)
-  and cannot declare their own layout behavior.
-
-We want a **single, modern way** to contribute a first-class dashboard layout
-component — via the Extensions framework — and to deprecate the legacy registry.
-The iframe component is the ideal pilot because it is self-contained.
-
-## Proposed Change
-
-### 1. A `dashboardComponents` contribution point
-
-Add `dashboardComponents` to the Extensions `Contributions` interface
-(`packages/superset-core/src/contributions/index.ts`), alongside `views`,
-`commands`, etc., with a public registration API mirroring the existing ones
-(`registerDashboardComponent` returning a `Disposable`), exposed on
-`window.superset.dashboardComponents` and wired into `ExtensionsLoader`.
-
-### 2. The Dashboard Component Contract (the heart of this SIP)
-
-The contract has two halves. Getting this right is the real work — it becomes a
-**public API Superset must support indefinitely**.
-
-**(a) Declarative behavior metadata** — replaces the seven hardcoded util maps:
-
-```ts
-interface DashboardComponentContribution {
-  id: string;                 // unique type key, namespaced, e.g. "my-org.iframe"
-  name: string;               // palette label
-  description?: string;
-  icon: string;               // contributed icon id or known icon name
-  resizable?: boolean;        // -> componentIsResizable
-  defaultMeta?: {             // -> newComponentFactory
-    width?: number;
-    height?: number;
-    [key: string]: unknown;
-  };
-  nesting?: {                 // -> isValidChild / shouldWrapChildInRow
-    validParents?: string[];  // e.g. [GRID, ROW, COLUMN, TAB]
-    wrapInRow?: boolean;
-    minWidth?: number;        // -> getDetailedComponentWidth
-  };
-  isUserContent?: boolean;    // -> isDashboardEmpty
-  loadComponent: () => Promise<{ default: ComponentType<DashboardComponentProps> }>;
-}
-```
-
-**(b) Runtime props contract** — a small, stable surface. Crucially, **the host
-owns the chrome** (the `Draggable` + `ResizableContainer` + `HoverMenu`/delete
-wrapper that every current `componentLookup` component re-implements today). The
-extension component renders only its *content* and, optionally, an *editor*:
-
-```ts
-interface DashboardComponentProps {
-  id: string;
-  meta: Record<string, unknown>;
-  editMode: boolean;
-  updateMeta: (patch: Record<string, unknown>) => void; // wraps updateComponents
-  // resize/drag/delete handled by the host wrapper, NOT the component
-}
-```
-
-This is a strict improvement over the status quo: the iframe component in the
-companion PR hand-rolls the Draggable/Resizable/HoverMenu wrapper; under this
-contract that boilerplate moves into the host once, and contributed components
-shrink to "render content + edit meta."
-
-### 3. Registry-driven core
-
-Refactor `componentLookup` and the seven behavior maps to consult a registry,
-with the **built-in leaf components seeded into it** at startup. Structural
-container components (Chart, Tabs, Row, Column, Header) *are* the layout engine
-and stay bespoke; the contribution point targets **leaf/content components**
-(today: Markdown, Divider, Iframe; tomorrow: anything). `DashboardComponent.tsx`
-resolves contributed types through the registry and renders them inside the
-shared host chrome.
-
-### 4. Deprecate `DashboardComponentsRegistry` / `DYNAMIC_TYPE`
-
-Mark the legacy registry and `DYNAMIC_TYPE` deprecated. Provide a shim so existing
-dynamic components keep working, with a migration note pointing at the new
-contribution point. Removal happens in a later major per Superset's deprecation
-policy.
-
-### 5. Graceful fallback for unknown types
-
-A saved dashboard layout stores component **type strings** in its position JSON.
-If a dashboard references a type whose extension is disabled/uninstalled, the host
-must render a non-destructive placeholder ("This component requires the *X*
-extension") and **preserve the meta on save** so re-enabling the extension
-restores it. The layout engine already tolerates unknown types defensively
-(`componentLookup[type]` → null; `isValidChild` → false); this SIP makes that an
-intentional, user-visible contract rather than silent breakage.
-
-### 6. Backend: APIs yes, security policy no
-
-The Extensions framework **already** lets a component contribute a backend REST
-API: the `@api` decorator (`superset-core/.../rest_api/decorators.py`) detects
-extension context and registers the route via `appbuilder.add_api()` at entrypoint
-import, serving it under `/extensions/{publisher}/{name}/...` and auto-creating
-the endpoint's FAB permission. **No new work is required for an extension to ship
-an API.**
-
-What an extension **cannot** do today, and what this SIP explicitly leaves to
-core:
-
-- **Role policy for a permission.** Endpoint permissions are auto-created, but
-  whether a permission is *Admin-only* (e.g. via
-  `SupersetSecurityManager.ADMIN_ONLY_VIEW_MENUS`) is decided in core at
-  `sync_role_definitions` time. The manifest's `permissions: list[str]` field is
-  currently **dormant** (never read), and the `ContributionProcessorRegistry` that
-  would process it is scaffolding that is not wired into the load pipeline.
-- **Security-sensitive request hooks** (e.g. rewriting CSP/Talisman headers).
-
-This is exactly why the companion CSP feature keeps its backend in core: the
-component *UI* is extension-shaped, but punching holes in the CSP and gating it
-admin-only are core security responsibilities.
-
-A **future, optional** extension of this SIP could finish wiring
-`ContributionProcessorRegistry` + a manifest permission-policy schema so
-extensions can declare role policy — but that is itself a security-review-worthy
-change and is out of scope here.
-
-## New or Changed Public Interfaces
-
-- **New contribution point** `dashboardComponents` on the `Contributions`
-  interface; new `registerDashboardComponent(...) -> Disposable` API; new
-  `window.superset.dashboardComponents` namespace.
-- **New public types** `DashboardComponentContribution` and
-  `DashboardComponentProps` (the contract) — these become long-term public API.
-- **Changed (internal → registry-driven)** `componentLookup` and the seven
-  behavior util maps; `DashboardComponent.tsx` resolution path; the host gains a
-  shared component-chrome wrapper.
-- **Deprecated** `DashboardComponentsRegistry`, `DYNAMIC_TYPE`,
-  `NewDynamicComponent`, `setupDashboardComponents`.
-
-## New dependencies
-
-None. Reuses the existing Extensions framework (module federation, manifest
-schema, `@api` decorator) and the existing functional-registry utilities.
-
-## Migration Plan and Compatibility
-
-- **No DB migration.** This is a frontend/framework change plus the (already
-  supported) extension API path.
-- **Layout JSON is unchanged** — component types remain type strings. The new
-  fallback behavior makes *unknown* types degrade gracefully instead of rendering
-  nothing.
-- **Backwards compatible:** built-in components are seeded into the registry, so
-  existing dashboards render identically. Legacy `DYNAMIC_TYPE` components keep
-  working via a deprecation shim.
-- **Rollout:** the contribution point is only active under `ENABLE_EXTENSIONS`;
-  with it off, behavior is identical to today.
-
-## Rejected Alternatives
-
-- **Keep / extend `DashboardComponentsRegistry`.** It is disconnected from the
-  modern Extensions framework and produces second-class components. Deprecating it
-  in favor of one contribution model is the goal, not a side effect.
-- **Require all built-in components to become extensions.** Chart/Tabs/Row/Column
-  are the layout engine; extracting them is high-risk and low-value. The
-  contribution point *adds* leaf components; it does not mandate extraction.
-- **Let the extension component own its own DnD/resize chrome** (as
-  `componentLookup` components do today). Rejected: it bloats the contract,
-  duplicates host logic, and makes the public API fragile. The host owns chrome.
-- **One combined SIP with the CSP feature.** Rejected: the framework change and
-  the security-sensitive feature are distinct discussions with different
-  reviewers and risk profiles, even though they share a POC branch.
-- **Move the CSP permission/role policy into the extension.** Not supported today
-  (dormant manifest `permissions`, unwired contribution processor) and
-  undesirable: admin-only gating and CSP-header rewriting are core security
-  responsibilities.
-
-## Implementation Status (POC)
-
-Implemented on the POC branch (`@apache-superset/core` mirrors the `chat`
-contribution-point pattern from #41000/#41205):
-
-- [x] `DashboardComponentDefinition` + `DashboardComponentProps` contract types
-      (`packages/superset-core/src/dashboardComponents`), added to the
-      `Contributions` interface and the package's subpath exports
-- [x] `dashboardComponents` contribution point: host `DashboardComponentsProvider`
-      registry + public `registerDashboardComponent`/`getDashboardComponents` API
-      (`src/core/dashboardComponents`), exposed on `window.superset` via
-      `ExtensionsStartup` + `Namespaces`
-- [x] Shared host component-chrome wrapper `DashboardExtensionComponent`
-      (owns Draggable/Resizable/HoverMenu/Delete; reads `resizable` from the
-      definition) behind the new `EXTENSION_TYPE`
-- [x] `componentLookup` + builder palette resolve the registry; the seven
-      behavior maps carry `EXTENSION_TYPE` leaf behavior
-- [x] Unknown-type graceful fallback (placeholder + meta preserved on save)
-- [x] Deprecation notices on `DashboardComponentsRegistry` / `DYNAMIC_TYPE`
-      (legacy path still functions)
-- [x] Reference component: the built-in iframe is now delivered **through** the
-      contribution point (`src/dashboard/extensions/iframe`), registered at
-      startup exactly as a third-party extension would; its CSP backend remains
-      in core per the companion SIP
-- [x] Tests: registry lifecycle (register/get/replace/dispose), host-wrapper
-      resolution + fallback + `updateMeta`, iframe content + CSP UX
-
-- [x] Per-component behavior policy honored by the layout engine: `resizable`,
-      `minWidth`, `isUserContent`, `validParents`, and `wrapInRow` are seeded onto
-      instance `meta` at creation and read by `componentIsResizable`,
-      `getDetailedComponentWidth`, `isDashboardEmpty`, `isValidChild`, and
-      `shouldWrapChildInRow` (the pure layout utils stay registry-free; behavior
-      round-trips in the saved layout)
-- [x] Developer docs: `extension-points/dashboard-components.md` + a
-      `contribution-types.md` section + sidebar entry, with an example extension
-
-Remaining (follow-up, not POC-blocking):
-
-- [ ] Manifest `contributions.dashboardComponents` declarative validation in the
-      Python/TS manifest schema (runtime side-effect registration works today,
-      matching how `chat` does it)
-- [ ] Remove the legacy `DashboardComponentsRegistry`/`DYNAMIC_TYPE` (major)

SIP.md

@@ -1,232 +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] Proposal for a first-class iframe dashboard component with a runtime CSP allowlist
-
-> **Companion SIP:** This proposal pairs with
-> [`SIP-DASHBOARD-COMPONENT-CONTRIBUTION-POINT.md`](SIP-DASHBOARD-COMPONENT-CONTRIBUTION-POINT.md),
-> which proposes the Extensions contribution point that would let this iframe
-> component (and others) be shipped as an extension. The two are deliberately
-> separate discussions: **this** SIP covers the security-sensitive feature
-> (runtime CSP override + permissions); the companion covers the framework
-> change. They share one POC branch so the end-to-end story is demonstrable.
-
-> **Status:** Draft — tracking the implementation in `feat/csp-runtime-allowlist-iframe`.
-> This document follows the SIP issue template and is kept in sync with the branch
-> as the implementation evolves. See SIP-0
-> (<https://github.com/apache/superset/issues/5602>) for the SIP process.
-
-## Motivation
-
-Superset ships a Talisman/Content-Security-Policy (CSP) configuration that, by
-design, prevents users from embedding arbitrary external content in a dashboard.
-The default policy declares `default-src 'self'` and **no** `frame-src`
-directive, so an `<iframe>` pointing at any third-party origin is blocked by the
-browser.
-
-This is correct and secure default behavior, but it creates real friction:
-
-- There is **no first-class "iframe" dashboard component**. Users historically
-  smuggled iframes through Markdown, which is both a footgun and blocked by CSP.
-- When an embed *is* legitimately needed (an internal tool, a status page, a
-  partner widget), the only way to allow it is to **edit `TALISMAN_CONFIG` and
-  restart every Superset process**. That is a deploy-time, ops-team operation —
-  far too heavyweight for "let me embed this one dashboard from our other
-  internal app."
-- There is no in-product signal telling a user *why* their embed is blank, and
-  no path to fix it.
-
-We want to (a) make embedding a real, supported component, and (b) give trusted
-Admins a controlled, audited way to widen the CSP at runtime — without
-abandoning the secure-by-default posture that operators rely on.
-
-## Proposed Change
-
-The change has five parts.
-
-### 1. A first-class `IFRAME` dashboard layout component
-
-A new grid component (`IFRAME_TYPE`) modeled on the existing Markdown/Divider
-components. In edit mode the user pastes a URL; in view mode the component
-renders a sandboxed `<iframe>`. The component is registered through the same
-surface as every other layout element (type constant, `componentLookup`, drag
-palette, nesting/resize/width/wrap util maps).
-
-The iframe is rendered with a restrictive `sandbox` attribute
-(`allow-scripts allow-same-origin allow-popups allow-forms`).
-
-### 2. Domain flagging
-
-When the runtime-allowlist feature is enabled, the component compares the
-embedded URL's **origin** against the current allowlist (fetched from the new
-API). If the origin is not yet allowed, it shows an inline warning explaining
-that the domain is blocked by the CSP.
-
-### 3. "Enable domain in CSP" button
-
-If the current user holds the new permission (Admins by default), the warning
-includes an **Enable domain in CSP** button. Clicking it `POST`s the origin to
-the allowlist API and re-checks. Users without the permission instead see "ask
-an administrator."
-
-### 4. Permission gating
-
-Mutating the allowlist requires `can write on CSPAllowlist`. The `CSPAllowlist`
-view-menu is registered in `SupersetSecurityManager.ADMIN_ONLY_VIEW_MENUS`, so
-the capability is reserved for Admins (or a custom role explicitly granted it),
-consistent with how other trusted, security-sensitive operations are scoped.
-
-### 5. Runtime CSP override ("punched holes")
-
-A new `csp_allowlist` metadata table stores allowlist entries. An `after_request`
-hook — registered **before** flask-talisman so that, because Flask runs
-`after_request` callbacks in reverse registration order, it runs **after**
-Talisman has set the header — merges the operator-curated entries into the
-response CSP header. Entries are cached in-process with a short TTL to avoid a DB
-hit per response; a write through the API invalidates the cache in the handling
-worker, and other workers converge when their cached copy expires.
-
-The entire runtime-override path is inert unless the `CSP_RUNTIME_ALLOWLIST`
-feature flag is enabled, so the static, deploy-time policy remains the default
-and operators opt in explicitly.
-
-```
-Browser ──> Flask request
-                 │
-         Talisman after_request  (sets "Content-Security-Policy: default-src 'self'; …")
-                 │
-   merge_runtime_csp_allowlist   (if flag on: appends allowlist origins to frame-src, …)
-                 │
-            Response ──> Browser  ("…; frame-src 'self' https://embed.example")
-```
-
-#### Design decisions (resolved)
-
-- **Scope: global.** Allowlist entries apply server-wide. CSP is a single
-  per-response header; a global allowlist keeps the merge context-free and
-  avoids per-dashboard request plumbing. (Per-dashboard scoping is a possible
-  future extension.)
-- **Operator control: feature-flagged kill-switch.** The runtime override only
-  functions when `CSP_RUNTIME_ALLOWLIST` is on (default **off**). Operators who
-  want a purely static policy simply leave it off and the table is never
-  consulted.
-
-## New or Changed Public Interfaces
-
-### REST API
-
-- `GET /api/v1/csp_allowlist/` — list entries
-- `GET /api/v1/csp_allowlist/<id>` — get one
-- `POST /api/v1/csp_allowlist/` — create (validates origin + directive)
-- `PUT /api/v1/csp_allowlist/<id>` — update
-- `DELETE /api/v1/csp_allowlist/<id>` — delete
-- `DELETE /api/v1/csp_allowlist/?q=!(...)` — bulk delete
-
-All write methods require `can write on CSPAllowlist` (Admin-only by default).
-Origins are validated server-side: bare `scheme://host[:port]` only — no
-wildcards, paths, query strings, fragments, or credentials. Only a fixed set of
-directives may be widened (`frame-src`, `child-src`, `img-src`, `connect-src`,
-`media-src`, `font-src`); notably **not** `script-src`.
-
-### Model
-
-- `CSPAllowlistEntry` (`superset/models/csp.py`, table `csp_allowlist`):
-  `id`, `uuid`, `domain`, `directive` (default `frame-src`), `description`,
-  audit columns. Unique on `(domain, directive)`.
-
-### Feature flag
-
-- `CSP_RUNTIME_ALLOWLIST` (default `False`) — gates the entire runtime-override
-  path, backend and frontend.
-
-### Config
-
-- `CSP_RUNTIME_ALLOWLIST_CACHE_TTL` (default `30` seconds) — in-process cache TTL
-  for the allowlist; also settable via env var.
-
-### Frontend
-
-- New `IFRAME` dashboard layout component and its registration across the
-  dashboard util maps.
-- New `FeatureFlag.CspRuntimeAllowlist` enum member.
-
-### Security model
-
-- New `CSPAllowlist` view-menu added to `ADMIN_ONLY_VIEW_MENUS`.
-
-## New dependencies
-
-None. The implementation uses existing libraries (flask-talisman,
-Flask-AppBuilder, marshmallow, SQLAlchemy on the backend; existing
-`@superset-ui/core` components on the frontend).
-
-## Migration Plan and Compatibility
-
-- One Alembic migration adds the `csp_allowlist` table
-  (`4a50792bd265`, down-revision `3a8e6f2c1b95`). The table is empty on creation.
-- Fully backward compatible: with the feature flag off (the default), behavior is
-  identical to today — the static CSP is authoritative and the new table is never
-  read. No existing dashboards, URLs, or policies change.
-- Rollback: dropping the table and disabling the flag fully reverts the feature.
-
-### Security review notes
-
-This feature deliberately relocates a *capability* (widening the CSP) from a
-purely deploy-time operator control into a runtime, permission-gated, audited
-operation. The mitigations that keep it within Superset's trust model:
-
-- **Off by default** behind a feature flag the operator owns.
-- **Admin-only** write permission (a fully trusted principal per `SECURITY.md`).
-- **Strict origin validation** server-side — no wildcards, no `script-src`.
-- **Audit trail** via the audit mixin (`created_by` / `changed_by`).
-- The iframe is **sandboxed** and the merge can only *widen* a directive to a
-  specific origin, never relax nonce/`strict-dynamic` protections on
-  `script-src`.
-
-## Rejected Alternatives
-
-- **Dynamically reconfiguring flask-talisman at runtime.** Talisman is configured
-  once at app init. Rather than mutate its internals, we add our own
-  `after_request` hook that post-processes the header it already sets. This is
-  simpler, avoids depending on Talisman internals, and rides the same per-request
-  header machinery Talisman already uses for its nonce.
-- **Per-dashboard allowlist scoping.** More precise, but CSP is a per-response
-  header; per-dashboard scoping adds request-context complexity for marginal
-  benefit in the common case. Left as a possible future extension.
-- **"Always on" runtime override (no kill-switch).** Simpler, but moves a
-  security control fully into the app with no operator opt-out. Rejected in favor
-  of the feature-flag kill-switch.
-- **Shared/Redis-backed allowlist cache with cross-worker invalidation.**
-  Correct but heavier. A short-TTL in-process cache is good enough: writes take
-  effect immediately in the handling worker and within the TTL elsewhere, with no
-  new infrastructure dependency.
-
-## Implementation Status
-
-- [x] Feature flag `CSP_RUNTIME_ALLOWLIST` + `CSP_RUNTIME_ALLOWLIST_CACHE_TTL`
-- [x] `CSPAllowlistEntry` model + Alembic migration
-- [x] DAO, marshmallow schemas (with origin/directive validation), REST API
-- [x] Admin-only permission (`CSPAllowlist` view-menu)
-- [x] `after_request` CSP merge hook + in-process TTL cache + invalidation
-- [x] `IFRAME` dashboard component + registration across util maps
-- [x] Domain flagging + permission-gated "Enable domain in CSP" button
-- [x] Tests: backend unit (validation + merge + hook), backend integration (API),
-      frontend unit (util + component)
-- [ ] Docs (`docs/`) + `UPDATING.md` entry
-- [ ] Community/security review feedback

UPDATING.md

@@ -24,84 +24,10 @@ assists people when migrating to a new version.
 
 ## Next
 
-- [39925](https://github.com/apache/superset/pull/39925): URL prefixing for `SUPERSET_APP_ROOT` subdirectory deployments is now handled automatically by helpers in `src/utils/navigationUtils` (`openInNewTab`, `redirect`, `getShareableUrl`, `<AppLink>`). Direct imports of `ensureAppRoot` / `makeUrl` from `src/utils/pathUtils` are forbidden outside `navigationUtils.ts` (enforced by a static-invariant test); contributors writing new code should use the focused helpers instead. No runtime behaviour change for existing callers — all 19 prior call sites have been migrated and four pre-existing double-prefix and missing-prefix bugs are fixed as part of the migration.
-
-- [39925](https://github.com/apache/superset/pull/39925): `SupersetClient.getUrl()` now strips a single leading application-root segment from the supplied `endpoint` before building the request URL, so a caller that accidentally pre-prefixes its endpoint (for example by wrapping it with `ensureAppRoot` before passing it to the client) no longer produces a doubled `/superset/superset/...` URL under subdirectory deployment. The strip is **single-pass** — a genuine `/superset/superset/<slug>` route is preserved, not collapsed — and **silent** (no console warning); the static-invariant test remains the primary signal for pre-prefixing at the call site, and this runtime strip is a safety net beneath it. Code that intentionally targeted a literal `/<app_root>/<app_root>/...` endpoint through `getUrl` (a configuration that has no legitimate use under the prefixing model) would have its first redundant segment removed.
-
-- **Breaking — `Superset` view class route prefix removed.** The `Superset` view in `superset/views/core.py` now declares `route_base = ""`, overriding Flask-AppBuilder's auto-derived `/superset` prefix. Routes that previously lived at `/superset/welcome/`, `/superset/dashboard/<id>/`, `/superset/dashboard/p/<key>/`, `/superset/explore/`, etc. now respond at `/welcome/`, `/dashboard/<id>/`, `/dashboard/p/<key>/`, `/explore/`, etc. Under subdirectory deployment (`SUPERSET_APP_ROOT=/superset`) the URLs are unchanged from end-user perspective — `AppRootMiddleware` re-applies the prefix via `SCRIPT_NAME`. Under root deployments, any external integration or bookmark that hard-codes `/superset/<endpoint>/` paths must be updated to drop the prefix. This fixes the doubled `/superset/superset/...` URLs that `url_for` emitted for these endpoints under subdirectory deployment and the related 404s on the routes themselves.
-
-- **Breaking — Three sibling view classes route prefix removed.** Following the same rationale as the `Superset` class above, `ExplorePermalinkView` (`superset/views/explore.py`), `TagModelView`, and `TaggedObjectsModelView` (`superset/views/tags.py`, `superset/views/all_entities.py`) now mount at the application root rather than a hard-coded `/superset/...`. The user-visible URLs `/superset/explore/p/<key>/`, `/superset/tags/`, and `/superset/all_entities/` are unchanged under subdirectory deployment; under root deployments these views now serve `/explore/p/<key>/`, `/tags/`, and `/all_entities/`, so any external integration or bookmark must drop the `/superset/` prefix. `Dashboard.url` and `Dashboard.get_url` likewise return `/dashboard/<id>/` instead of the prior `/superset/dashboard/<id>/` literal so downstream consumers (DashboardList row hrefs, MCP service `dashboard_url`) emit a single, deployment-correct prefix.
-
-- **Legacy `/superset/*` path support.** A new outermost WSGI middleware `LegacyPrefixRedirectMiddleware` (`superset/middleware/legacy_prefix_redirect.py`) 308-redirects every enumerated legacy `/superset/<canonical>` path to its post-`route_base=""` canonical location (e.g. `/superset/welcome/` → `/welcome/` under root; → `/superset/welcome/` under `SUPERSET_APP_ROOT=/superset`, because the canonical resolves through `AppRootMiddleware`). Bookmarks, email links, and external integrations survive the route-base collapse for one release cycle. POST against a GET-only canonical returns 410 Gone instead of 308 (308 would 405 on retry). The shim is removed at EOL `5.0.0`, matching the `@deprecated(eol_version="5.0.0")` gate on `Superset.explore` and `Superset.explore_json`.
-
-- **PWA web app manifest served dynamically.** The PWA manifest is now served at `/pwa-manifest.json` (under `APPLICATION_ROOT`) by a new `PwaManifestView` (`superset/views/pwa_manifest.py`) instead of the static file at `/static/assets/pwa-manifest.json`. The legacy static source at `superset-frontend/src/pwa-manifest.json` has been removed (along with its `webpack.config.js` `CopyPlugin` rule). The new endpoint resolves `APPLICATION_ROOT` and `STATIC_ASSETS_PREFIX` at request time so PWA install works under subdirectory deployments and split static-prefix / app-root deployments (where `STATIC_ASSETS_PREFIX` points to a CDN host while the Superset backend stays under `APPLICATION_ROOT`). The `<link rel="manifest">` href in `superset/templates/superset/spa.html` was updated correspondingly (using a new `application_root_rstrip` template global). Operators with a forked `spa.html` should switch any manifest `<link>` to `{{ application_root_rstrip }}/pwa-manifest.json`.
-
-- **Hard re-bookmark break — `/superset/sql/<database_id>/`.** SQL Lab moved to its own blueprint at `/sqllab/`. The legacy `/superset/sql/<id>/` shape changed to a query-string form (`/sqllab/?dbid=<id>`); no 1:1 path mapping exists, so `LegacyPrefixRedirectMiddleware` does **not** redirect this route — it passes through and surfaces a 404. Users with bookmarks to `/superset/sql/<id>/` must update them to `/sqllab/?dbid=<id>`.
-
-- **`SqlaTable.sql_url` query-string format.** `SqlaTable.sql_url` now URL-encodes `table_name` and joins it as a query parameter rather than concatenating a second `?`. Previously, with `Database.sql_url` returning `/sqllab/?dbid=<id>`, the concatenation produced `/sqllab/?dbid=<id>?table_name=<raw>` — a malformed second `?` that broke the query parser. External code that parsed the legacy `<base>?table_name=<raw>` shape now sees properly percent-encoded values (e.g. `/` → `%2F`, ` ` → `+` or `%20`); decode with `urllib.parse.parse_qsl`.
-
-- **New config flag `EMBEDDED_DISABLE_PERMALINK_ORIGIN_REWRITE` (default `False`).** Share/permalink URLs now substitute `window.location.origin` for the backend-supplied origin so a proxied or subdirectory-deployed Superset never hands the user an unreachable internal hostname. Operators whose reverse proxy correctly forwards `X-Forwarded-Host` *and* who want permalinks to carry the backend's literal origin can opt out by setting `EMBEDDED_DISABLE_PERMALINK_ORIGIN_REWRITE = True` in `superset_config.py`. Default `False` (rewrite is on); flipping the default would regress the dominant proxied/subdir deployment to an unreachable host.
-
-- [41651](https://github.com/apache/superset/pull/41651): **New do-not-translate standard for translation catalogs.** Strings that must stay identical to the source — icon names (e.g. `bolt`), enum/option values (`step-after`), SQL keywords, API field names (`error_message`), code constants, and example placeholders — are now marked with a `#. do-not-translate` extracted comment. The list lives in the `superset/translations/do-not-translate.txt` registry; `scripts/translations/apply_do_not_translate.py` stamps the marker onto `messages.pot` during `babel_update.sh`, and `pybabel update` propagates it to every `.po`, so the status is consistent across all languages. The AI backfill (`backfill_po.py`) and translators leave these entries untranslated (source fallback). The legacy per-catalog convention (a `# Не переводить` translator comment in the `ru` catalog) is still honored for back-compat but is superseded by this standard; contributors adding new machine-read strings should add the msgid to the registry rather than annotating individual catalogs.
-
-### SQL Lab denies large-object and information_schema access by default
-
-`DISALLOWED_SQL_FUNCTIONS` and `DISALLOWED_SQL_TABLES` now ship with additional default entries, so SQL Lab and chart-data queries that reference them are rejected where they were previously allowed:
-
-- PostgreSQL large-object routines (`lo_from_bytea`, `lo_export`, `lo_import`, `lo_put`, `lo_create`, `lo_creat`, `lowrite`, `lo_get`, `loread`, `lo_unlink`), which read and write bytes on the database server's filesystem.
-- The SQL-standard `information_schema` views (`tables`, `columns`, `routines`, `views`, the privilege/grant views, etc.), which expose table, column, privilege, and view-definition metadata across the whole database.
-
-Deployments that legitimately query these (for example tooling that introspects `information_schema`) can restore the previous behavior by overriding `DISALLOWED_SQL_FUNCTIONS` / `DISALLOWED_SQL_TABLES` in `superset_config.py` to drop the entries they need.
-
-Because the denylist now resolves the effective schema through the query-aware path, PostgreSQL queries that change the `search_path` (e.g. `SET search_path = ...`) are rejected on the SQL Lab execution and cost-estimate paths whenever any `DISALLOWED_SQL_TABLES` entry is configured (the default for PostgreSQL), matching the behavior previously applied only when `RLS_IN_SQLLAB` was enabled.
-
-### SQL parser input length cap (SQL_MAX_PARSE_LENGTH)
-
-The SQL parser now rejects scripts whose UTF-8 byte length exceeds the new
-`SQL_MAX_PARSE_LENGTH` config option (default `1_000_000` bytes) before they are
-handed to sqlglot, which bounds parser memory and CPU usage. A single query
-larger than the cap (for example a very large `IN (...)` list or a big
-virtual-dataset SQL) raises a parse error in SQL Lab and dashboard-generated
-queries. Deployments that legitimately run queries above this size should raise
-the value, and `SQL_MAX_PARSE_LENGTH = None` disables the check entirely.
-
-### Guest-token RLS rules reject unknown fields
-
-The `rls` rules passed to `POST /api/v1/security/guest_token/` are now validated strictly: a rule may only contain `dataset` and `clause`. Previously unknown fields were silently dropped, so a mistyped or legacy scope key (most commonly `datasource` instead of `dataset`) produced a rule with no `dataset`, which is treated as a *global* rule applied to every dataset the embedded resource can reach. Such a request now returns HTTP 400 identifying the offending field instead of issuing a token with an unintended global rule. Integrators that were sending extra fields in RLS rules must remove them; valid dataset-scoped (`{"dataset": 41, "clause": "..."}`) and global (`{"clause": "..."}`) rules are unaffected.
-
-### MCP service requires `MCP_JWT_AUDIENCE` when JWT auth is enabled
-
-When the MCP service has JWT auth enabled (`MCP_AUTH_ENABLED = True`), an audience must be configured via `MCP_JWT_AUDIENCE` so issued tokens are bound to this service. The service now fails to start with a clear configuration error when the audience is unset, instead of starting with audience validation skipped. Deployments that enable MCP JWT auth must set `MCP_JWT_AUDIENCE` to the audience value their identity provider issues for the MCP service. API-key-only MCP deployments (JWT auth disabled) are unaffected.
-
-### Swagger UI is opt-in (off by default)
-
-`FAB_API_SWAGGER_UI` now defaults to `False` and is driven by the `SUPERSET_ENABLE_SWAGGER_UI` environment variable. The interactive Swagger UI / OpenAPI documentation endpoints (e.g. `/swagger/v1`) are therefore no longer exposed by default. To enable them, set `SUPERSET_ENABLE_SWAGGER_UI=true` (the bundled Docker development environment sets this) or override `FAB_API_SWAGGER_UI = True` in `superset_config.py`.
-
-### Build details (git SHA / build number) are admin-only by default
-
-The git SHA and build number surfaced in the "About" section, the bootstrap payload, and the public `/version` endpoint are now only included for admin users by default; the release version string is still shown to everyone. To expose the build details to all users (the previous behavior), set the `SUPERSET_EXPOSE_BUILD_DETAILS` environment variable (or `EXPOSE_BUILD_DETAILS_TO_USERS = True` in `superset_config.py`).
-
-### Helm chart adopts Kubernetes recommended labels (breaking upgrade)
-
-The Helm chart now labels and selects workloads using the [Kubernetes recommended labels](https://kubernetes.io/docs/concepts/overview/working-with-objects/common-labels/) (`app.kubernetes.io/*`) instead of the legacy `app`/`release` labels. Because a Deployment's `spec.selector.matchLabels` is immutable, `helm upgrade` against an existing release will fail with a `field is immutable` error.
-
-To upgrade, delete the affected workloads (which selector labels changed) before upgrading, then run the upgrade so they are recreated with the new labels:
-
-```bash
-kubectl delete deployment,statefulset -l release=<release-name> -n <namespace>
-helm upgrade <release-name> superset/superset
-```
-
-Alternatively, perform a fresh install. This is a one-time migration; subsequent upgrades are unaffected.
-
 ### Pivot table First/Last aggregations follow data order
 
 The pivot table chart's `First` and `Last` aggregations now return the first and last value in data (query result) order, instead of effectively returning the minimum and maximum. Existing pivot tables that use these aggregations for totals/subtotals may show different values after upgrading. For deterministic results, ensure the underlying query has a stable sort order.
 
-### `FetchRetryOptions` callback parameters widened to allow `null`
-
-The `error` and `response` parameters of the `retryDelay` and `retryOn` callbacks in `FetchRetryOptions` (exported from `@superset-ui/core`) are now typed `Error | null` and `Response | null` to match the actual call-site signature provided by `fetch-retry`. Because these parameter types are contravariant, consumers who typed their callbacks with the non-nullable `(attempt: number, error: Error, response: Response) => number` will get a TypeScript compile error. Widen your callback signatures to accept `Error | null` / `Response | null`.
-
 ### `thumbnail_url` removed from dashboard list API response
 
 The `thumbnail_url` field has been removed from `GET /api/v1/dashboard/` list responses. External consumers relying on this field must now construct the thumbnail URL client-side using `id` and `changed_on_utc`:
@@ -112,20 +38,6 @@ The `thumbnail_url` field has been removed from `GET /api/v1/dashboard/` list re
 
 The thumbnail endpoint redirects to the current digest URL regardless of whether the supplied digest is exact. If the image is not yet cached, that digest URL may return `202` and trigger async generation. Using `changed_on_utc` as the digest is sufficient for cache-busting purposes.
 
-### Tagging fix for `create_all`-bootstrapped schemas
-
-Only affects deployments whose metadata schema was created with SQLAlchemy's `create_all` (rather than `superset db upgrade`) on a foreign-key-enforcing backend — PostgreSQL, or MySQL with `FOREIGN_KEY_CHECKS=1`. Such schemas carry three invalid foreign keys on `tagged_object.object_id` that break tagging (`TAGGING_SYSTEM = True`) with a `ForeignKeyViolation`. Schemas built via `superset db upgrade` are unaffected.
-
-This release stops the ORM from emitting these constraints, but it cannot drop ones already present in your schema. If affected, drop them manually (names vary by backend, so look them up first):
-
-```sql
--- PostgreSQL: names are typically tagged_object_object_id_fkey, _fkey1, _fkey2
-ALTER TABLE tagged_object DROP CONSTRAINT <constraint_name>;
-
--- MySQL: find names via `SHOW CREATE TABLE tagged_object;`
-ALTER TABLE tagged_object DROP FOREIGN KEY <constraint_name>;
-```
-
 ### Webhook alerts/reports block private/internal hosts by default
 
 Webhook alert/report dispatch (`WebhookNotification.send`) now validates the target URL's host against the same private/internal-IP block applied to dataset import URLs. If the resolved host is in a loopback, link-local, private (RFC-1918), shared-CGNAT, or multicast range, the webhook is rejected with `NotificationParamException`.
@@ -135,7 +47,6 @@ Deployments that intentionally point webhooks at internal targets (chatops bridg
 ### Impala cancel_query blocks private/internal hosts by default
 
 The Impala engine spec's `cancel_query` issues an HTTP request from the Superset backend to the host configured on the Impala database connection. That host is now validated before the request: if it resolves to a private/internal IP range, the cancel call is refused and a warning is logged. Operators whose Impala cluster runs on an internal network can opt out by setting `IMPALA_CANCEL_QUERY_ALLOW_INTERNAL_HOSTS = True` in `superset_config.py`. This mirrors the dataset-import and webhook opt-out flags.
-
 ### Map chart renderer and OpenStreetMap migration behavior
 
 The MapLibre migration for deck.gl charts preserves saved non-Mapbox styles on
@@ -173,11 +84,6 @@ Operators can tune or disable the policy via config:
 ### Data uploads bounded by UPLOAD_MAX_FILE_SIZE_BYTES
 
 Single data-file uploads (CSV, Excel, columnar) are now bounded by the `UPLOAD_MAX_FILE_SIZE_BYTES` config option, which defaults to `100 * 1024 * 1024` (100 MB). Files larger than this are rejected with a `413` before their contents are buffered into memory. Set `UPLOAD_MAX_FILE_SIZE_BYTES = None` to disable the check and restore unbounded uploads.
-### Currency symbol position follows the locale when unset
-
-When a chart's currency control leaves the **Prefix or suffix** field empty, the currency symbol position is now derived from the deployment locale's own convention via `Intl.NumberFormat` instead of always defaulting to a suffix. For example, under the default `en-US` locale `USD`, `GBP`, and `EUR` render as a prefix (`$ 1,000`), while eurozone locales such as `fr-FR` render `EUR` as a suffix (`1 000 €`). An explicit Prefix/Suffix selection is always honored and is unaffected.
-
-Charts that relied on the previous always-suffix default for an unset position will render the symbol on the locale-appropriate side instead; set the position explicitly on the metric's currency control to pin it.
 
 ### Duration formatter precision
 
@@ -243,18 +149,6 @@ Runbook to adopt:
 2. Set that value on the tunnel's `server_host_key` (via the database/SSH tunnel API or UI payload).
 3. Optionally set `SSH_TUNNEL_STRICT_HOST_KEY_CHECKING = True` in `superset_config.py` to require host-key verification on all tunnels.
 
-### SMTP server certificate validation enabled by default
-
-`SMTP_SSL_SERVER_AUTH` now defaults to `True` (previously `False`). With this default, STARTTLS/SSL connections to the configured SMTP server validate the server's TLS certificate against the system trusted CA store. This makes outbound email (alerts and reports) verify the mail server's identity out of the box.
-
-If your SMTP server presents a self-signed certificate, or a certificate that is not trusted by the system CA store, email delivery may now fail with a certificate verification error. To restore the previous behavior of skipping certificate validation, set the following in `superset_config.py`:
-
-```python
-SMTP_SSL_SERVER_AUTH = False
-```
-
-The recommended fix is to add the SMTP server's certificate (or its issuing CA) to the system trust store rather than disabling validation.
-
 ### Dataset import validates catalog against the target connection
 
 Importing a dataset now validates the `catalog` field against the target database connection. When the connection has multi-catalog disabled (`allow_multi_catalog` off) and the dataset's catalog is not the connection's default catalog, the import fails instead of silently persisting the non-default catalog. This matches the validation already enforced on the dataset update path and prevents imported datasets from querying an unintended database.
@@ -304,80 +198,6 @@ Schedule the cutover in a quiet window. Runtime reads use only the single config
 
 The migration is transactional (all-or-nothing) and idempotent — it can be safely re-run or resumed. Note that AES-GCM, unlike AES-CBC, does not support querying directly over encrypted columns; audit any code that filters on an encrypted column before switching. See the SIP at `docs/sip/authenticated-encryption-at-rest.md` for details.
 
-### 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 `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.
-
-**Flag-independent parts of this work** (active even with `SOFT_DELETE` off): the restore endpoint and deleted-state filter (above); the database-deletion guard counting soft-deleted datasets; the `get_or_create_dataset` soft-deleted-twin pre-check; the combined datasource listing (`GET /api/v1/datasource/...`) always excluding soft-deleted datasets; and the two uniqueness-validation changes documented at the end of this section. Everything else — the soft DELETE itself and the visibility filtering — is flag-gated.
-
-With the flag enabled: `DELETE /api/v1/dataset/<id>` no longer hard-deletes the dataset (the bulk-delete endpoint behaves the same way). The row is marked with a `deleted_at` timestamp and hidden from all list, detail, and lookup endpoints. Datasets in this state are excluded from default queries and from relationship loads (e.g. `database.tables`).
-
-**No cascade in v1.** Soft-delete does not propagate to dependent charts or dashboards: they remain visible. Loading a chart whose dataset is soft-deleted surfaces a "datasource not found" error at chart-load time. Restore the dataset to recover.
-
-**Database deletion is blocked by soft-deleted datasets.** Superset already refuses to delete a database that still has datasets (`DatabaseDeleteDatasetsExistFailedError`); that check now explicitly counts soft-deleted datasets too (it bypasses the visibility filter), since the soft-deleted `tables` rows still reference the database via `database_id` and must not be orphaned. Consequence: because dataset `DELETE` is soft and v1 ships no hard-delete/purge, **a database that has ever had datasets cannot be deleted through the API once those datasets are soft-deleted** — the rows remain and keep blocking the delete. Until a purge capability lands, operators who must remove such a database have to hard-delete the underlying `tables` rows out-of-band first. This is a deliberate trade-off (no orphaned rows / restorable datasets) and is expected to be resolved by the planned purge work.
-
-**Side-effect change for operators.** Because the row is no longer physically deleted, FAB `ab_view_menu` / permission-view rows tied to the dataset are also preserved. Downstream automation that relied on `DELETE /api/v1/dataset/<id>` cleaning up those rows must now react to the new `POST /api/v1/dataset/<uuid>/restore` lifecycle, or call the eventual hard-delete endpoint.
-
-**New endpoint** — `POST /api/v1/dataset/<uuid>/restore` clears `deleted_at` and returns the dataset to active state. Requires `can_write on Dataset` and ownership of the row (or admin). Soft-deleted datasets can also be surfaced in the list endpoint via the new `dataset_deleted_state` rison filter: `include` returns both live and soft-deleted rows, `only` returns just the soft-deleted ones. Any other value is ignored. For non-admin users, soft-deleted rows are limited to datasets they own — the same audience that can restore them.
-
-**Permissions migration:** existing role grants of `can_write on Dataset` cover the new restore endpoint automatically; no role migration is required.
-
-**Schema migration:** the migration adds a nullable `deleted_at` column and an index on it (`ix_tables_deleted_at`) to the `tables` table. The column add is instant; the index build runs inline (no `CONCURRENTLY`) and may briefly block writes on the `tables` table (INSERT/UPDATE/DELETE are queued while the index builds; reads are unaffected) on large Postgres deployments. MySQL InnoDB builds the index online (no blocking). Production deployments with many thousands of datasets should run this migration during a maintenance window.
-
-**Rollback note:** if the application code is rolled back after datasets have been soft-deleted, the older code path's visibility filter no longer applies and previously hidden rows become visible to the older code. Pair the rollback with a data decision (restore the rows, hard-delete them, or also downgrade the migration) rather than assuming the old hard-delete semantics still hold. **Downgrading the migration destroys the deletion markers**: `downgrade()` drops the `deleted_at` column, so any not-yet-restored soft-deleted datasets silently become live, active datasets with no record they were ever deleted. Reconcile the trash (restore or hard-delete each row) *before* downgrading, and disable the `SOFT_DELETE` flag first so no new soft deletes land mid-rollback.
-
-**SQL Lab / dataset-creation flows:** creating a dataset over a table whose dataset sits in the trash is refused. The SQL Lab "save as dataset" flow (`get_or_create_dataset`) and file uploads return a **422 naming the hidden twin and the restore endpoint**; the plain create, update, and duplicate paths currently fail with the generic "already exists" 422. In all cases the remediation is the same: restore the hidden dataset (or use a different table name). Perm-string maintenance also covers hidden rows: renaming a database rewrites `perm`/`schema_perm`/`catalog_perm` on soft-deleted datasets and their charts, so a later restore does not resurrect stale permission strings.
-
-**Importer behavior:** importing a dataset YAML whose UUID matches an existing **soft-deleted** dataset is treated as an implicit restore-with-update — **and this happens even when `overwrite` is not set**. This is a deliberate asymmetry with active rows: an active dataset imported without `overwrite=true` is returned unchanged, but a soft-deleted UUID match is restored *and* has the upload's contents applied regardless of the `overwrite` argument, on the reasoning that re-importing a deleted dataset's exact UUID is an explicit request to bring it back. The restore preserves the original PK, the chart back-reference, `table_columns`, and `sql_metrics`. Non-owners get `ImportFailedError`. Callers without `can_write` get `ImportFailedError` instead of silently receiving the soft-deleted row.
-
-**Uniqueness-validation changes that apply regardless of the feature flag:** two dataset uniqueness checks were tightened alongside this work and are active even with `SOFT_DELETE` off. (1) Create/update uniqueness treats a dataset whose `catalog` is `NULL` as belonging to the database's default catalog, so a legacy twin pair (`catalog=NULL` vs. `catalog=<default>`, same database/schema/name) that older versions allowed now fails validation with "already exists" when either row is edited — resolve by renaming or removing one of the twins. (2) Duplicating a dataset now checks name collisions scoped to the target (database, catalog, schema) instead of globally by name alone: duplicates into other databases that were previously blocked are now allowed.
-
-### Soft delete and restore for charts
-
-**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.
-
-With the flag enabled: `DELETE /api/v1/chart/<id>` no longer hard-deletes the chart (the bulk-delete endpoint behaves the same way). The row is marked with a `deleted_at` timestamp and hidden from all list, detail, and lookup endpoints. Charts in this state are excluded from default queries and from relationship loads (e.g. `dashboard.slices`).
-
-**Operational notes:** a report schedule whose target chart is soft-deleted now fails its runs with an explicit error ("The chart this report targets was deleted...") until the chart is restored or the report re-pointed — chart deletion is blocked while a report references the chart, but a validate/commit race or a flag toggle can still produce this state. Dashboards **preserve** their membership rows for soft-deleted charts: saving a dashboard does not sever a trashed member, and restoring the chart re-attaches it to its dashboards.
-
-**New endpoint** — `POST /api/v1/chart/<uuid>/restore` clears `deleted_at` and returns the chart to active state. Requires `can_write on Chart` and ownership of the row (or admin). Soft-deleted charts can also be surfaced in the list endpoint via the new `chart_deleted_state` rison filter: `include` returns both live and soft-deleted rows, `only` returns just the soft-deleted ones. Any other value is ignored. For non-admin users, soft-deleted rows are limited to charts they own — the same audience that can restore them.
-
-**Permissions migration:** existing role grants of `can_write on Chart` cover the new restore endpoint automatically; no role migration is required.
-
-**Schema migration:** the migration adds a nullable `deleted_at` column and an index on it (`ix_slices_deleted_at`) to the `slices` table. The column add is instant; the index build runs inline (no `CONCURRENTLY`) and may briefly block writes on the `slices` table (INSERT/UPDATE/DELETE are queued while the index builds; reads are unaffected) on large Postgres deployments. MySQL InnoDB builds the index online (no blocking).
-
-**Rollback note:** if the application code is rolled back after charts have been soft-deleted, the older code path's visibility filter no longer applies and previously hidden rows become visible to the older code. Pair the rollback with a data decision (restore the rows, hard-delete them, or also downgrade the migration) rather than assuming the old hard-delete semantics still hold. **Downgrading the migration destroys the deletion markers**: `downgrade()` drops the `deleted_at` column, so any not-yet-restored soft-deleted charts silently become live, active charts with no record they were ever deleted. Reconcile the trash (restore or hard-delete each row) *before* downgrading, and disable the `SOFT_DELETE` flag first so no new soft deletes land mid-rollback.
-
-**Importer behavior:** importing a chart YAML whose UUID matches an existing **soft-deleted** chart is treated as an implicit restore-with-update — **and this happens even when `overwrite` is not set**. This is a deliberate asymmetry with active rows: an active chart imported without `overwrite=true` is returned unchanged, but a soft-deleted UUID match is restored *and* has the upload's contents applied regardless of the `overwrite` argument, on the reasoning that re-importing a deleted chart's exact UUID is an explicit request to bring it back. The restore preserves the original PK and all out-of-archive references (`dashboard_slices` junctions, `report.chart_id`, tag rows). The operation is permission-gated: non-owners get `ImportFailedError`, and callers without `can_write` get `ImportFailedError` instead of silently receiving the soft-deleted row.
-
-- [39914](https://github.com/apache/superset/pull/39914) `ALERT_REPORT_SLACK_V2` now defaults to `True` and the legacy Slack v1 integration (`Slack` recipient type, `files.upload` API) is deprecated for removal in the next major. Slack blocked new apps from `files.upload` in May 2024 and fully retired the method for all apps on November 12, 2025; because the v1 path sends files through `files.upload`, v1 file-bearing sends now fail at the API level — only text-only `chat_postMessage` still works via the legacy path. Grant your Slack bot the `channels:read` and `groups:read` scopes so existing `Slack` recipients can be auto-upgraded to `SlackV2` on next send. Operators who explicitly override the flag to `False`, or whose Slack bot is missing those scopes, will see deprecation warnings while text-only sends continue through the legacy path.
-
-### Soft delete and restore for dashboards
-
-**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.
-
-With the flag enabled: `DELETE /api/v1/dashboard/<id>` no longer hard-deletes the dashboard (the bulk-delete endpoint behaves the same way). The row is marked with a `deleted_at` timestamp and hidden from the dashboard API's list, detail, and lookup endpoints, which return 404 for soft-deleted dashboards. The embedded-dashboard iframe URL (`/embedded/<uuid>`) keeps rendering because it reads only `embedded.allowed_domains` and `embedded.dashboard_id` (the FK column) without dereferencing the parent dashboard; the frontend's subsequent dashboard-API fetch is what sees the 404 and surfaces "dashboard not found" to the user.
-
-**New endpoint** — `POST /api/v1/dashboard/<uuid>/restore` clears `deleted_at` and returns the dashboard to active state. Requires `can_write on Dashboard` and ownership of the row (or admin). Soft-deleted dashboards can also be surfaced in the list endpoint via the new `dashboard_deleted_state` rison filter: `include` returns both live and soft-deleted rows, `only` returns just the soft-deleted ones. Any other value is ignored. For non-admin users, soft-deleted rows are limited to dashboards they own — the same audience that can restore them.
-
-**Permissions migration:** existing role grants of `can_write on Dashboard` cover the new restore endpoint automatically; no role migration is required.
-
-**Schema migration:** the migration adds a nullable `deleted_at` column and an index on it (`ix_dashboards_deleted_at`) to the `dashboards` table, and **replaces the full unique constraint on `slug`** with a partial unique index (`ix_dashboards_active_slug`) enforcing slug uniqueness only among active (non-soft-deleted) rows. The column add is instant. On Postgres the constraint swap briefly blocks reads and writes during `ALTER TABLE ... DROP CONSTRAINT` (acquires `ACCESS EXCLUSIVE`), then blocks writes only during `CREATE UNIQUE INDEX` (acquires `ShareLock`); reads pass through during the index build. Both windows are sub-second on a typical `dashboards` table. MySQL InnoDB builds the functional index online (no blocking).
-
-**Rollback note:** the downgrade restores the original full unique constraint on `slug`. If the partial-index window allowed slug reuse (a soft-deleted row and an active row holding the same slug), `ALTER TABLE ... ADD CONSTRAINT idx_unique_slug UNIQUE (slug)` will abort with a unique-constraint violation. Before downgrading, hard-delete the soft-deleted duplicates (or rename one side) so each slug appears at most once across all rows. Rolling back the application code while leaving the new migration in place is also possible but exposes soft-deleted rows to the older code path; pair the rollback with a data decision (restore, hard-delete, or migrate-down).
-
-The partial-index replacement is dialect-dependent: PostgreSQL uses a native `WHERE deleted_at IS NULL` partial index; MySQL 8.0.13+ uses a functional index over `(CASE WHEN deleted_at IS NULL THEN slug END)` (8.0.13 is the first release with functional key parts). **MySQL <8.0.13, MariaDB, and SQLite keep the original full unique constraint** (functional indexes / column-level UNIQUE recreation aren't supported cleanly — MariaDB is excluded even at 10.x because its `CASE`-expression index semantics differ), so on those backends a soft-deleted dashboard continues to reserve its slug for the lifetime of the row.
-
-**Slug semantics:** on PostgreSQL and MySQL 8.0.13+, the slug of a soft-deleted dashboard is **free for reuse**. A new active dashboard can claim it immediately. Restoring a soft-deleted dashboard whose slug has since been claimed returns **422 with a clean error** (`DashboardSlugConflictError`) — rename one of the dashboards and retry; the restore is not silently rejected by a database-level constraint violation.
-
-**Importer behavior:** importing a dashboard YAML whose UUID matches an existing **soft-deleted** dashboard is treated as an implicit restore-with-update — **and this happens even when `overwrite` is not set**. This is a deliberate asymmetry with active rows: an active dashboard imported without `overwrite=true` is returned unchanged (the import never mutates it), but a soft-deleted UUID match is restored *and* has the upload's contents applied regardless of the `overwrite` argument, on the reasoning that re-importing a deleted dashboard's exact UUID is an explicit request to bring it back. The restore preserves the original PK and all pre-deletion relationship rows (`dashboard_slices` junctions, role grants, owners, tags) — including role grants that were implicitly revoked by the deletion. Callers whose imports must never mutate existing state should treat bundles that may contain previously deleted UUIDs accordingly. The operation is permission-gated: it requires `can_write` and ownership of the deleted row (or admin) — non-owners get `ImportFailedError`, and callers without `can_write` get `ImportFailedError` instead of silently receiving the soft-deleted row.
-
 ### Granular Export Controls
 
 A new feature flag `GRANULAR_EXPORT_CONTROLS` introduces three fine-grained permissions that replace the legacy `can_csv` permission:
@@ -667,29 +487,6 @@ See `superset/mcp_service/PRODUCTION.md` for deployment guides.
   }
   ```
 
-### Composite primary keys on many-to-many association tables
-
-Eight M:N association tables move from a synthetic `id INTEGER PRIMARY KEY` to a composite `PRIMARY KEY (fk1, fk2)` on their two foreign-key columns. The surrogate `id` is dropped, and the redundant `UNIQUE (fk1, fk2)` on the two tables that carried one is removed (now subsumed by the PK).
-
-| Table | Composite PK |
-|---|---|
-| `dashboard_roles` | `(dashboard_id, role_id)` |
-| `dashboard_slices` | `(dashboard_id, slice_id)` |
-| `dashboard_user` | `(user_id, dashboard_id)` |
-| `report_schedule_user` | `(user_id, report_schedule_id)` |
-| `rls_filter_roles` | `(role_id, rls_filter_id)` |
-| `rls_filter_tables` | `(table_id, rls_filter_id)` |
-| `slice_user` | `(user_id, slice_id)` |
-| `sqlatable_user` | `(user_id, table_id)` |
-
-**Before upgrading:**
-
-- The migration **deletes** two classes of pre-existing rows the composite PK cannot accommodate: duplicate `(fk1, fk2)` pairs (it keeps the lowest `id` and removes the rest) and rows with `NULL` in either FK column. Both are meaningless for `secondary=` association tables, but export the affected rows first if you need an audit record.
-- External tooling (BI tools, backup scripts) that references the surrogate `id` on these tables will break; no application code references it.
-- Downgrade restores the `id` column (and the original `UNIQUE` on the two tables that had it) but leaves the FK columns `NOT NULL` (intentional — a `NULL` FK in a junction row is meaningless).
-
-For large `dashboard_slices` / `report_schedule_user` tables, see the operator runbook in [#39859](https://github.com/apache/superset/pull/39859) — pre-flight inventory queries, per-dialect lock-window sizing, and the duplicate / NULL-FK roll-up — to plan the maintenance window.
-
 ## 6.0.0
 - [33055](https://github.com/apache/superset/pull/33055): Upgrades Flask-AppBuilder to 5.0.0. The AUTH_OID authentication type has been deprecated and is no longer available as an option in Flask-AppBuilder. OpenID (OID) is considered a deprecated authentication protocol - if you are using AUTH_OID, you will need to migrate to an alternative authentication method such as OAuth, LDAP, or database authentication before upgrading.
 - [34871](https://github.com/apache/superset/pull/34871): Fixed Jest test hanging issue from Ant Design v5 upgrade. MessageChannel is now mocked in test environment to prevent rc-overflow from causing Jest to hang. Test environment only - no production impact.

docker/.env

@@ -70,8 +70,6 @@ SUPERSET_LOG_LEVEL=info
 
 SUPERSET_APP_ROOT="/"
 SUPERSET_ENV=development
-# Swagger UI is opt-in (off by default); enable it for local development.
-SUPERSET_ENABLE_SWAGGER_UI=true
 SUPERSET_LOAD_EXAMPLES=yes
 CYPRESS_CONFIG=false
 SUPERSET_PORT=8088

docs/.nvmrc

@@ -1 +0,0 @@
-../superset-frontend/.nvmrc

docs/.nvmrc

@@ -0,0 +1 @@
+v24.16.0

docs/admin_docs/configuration/alerts-reports.mdx

@@ -81,21 +81,6 @@ SLACK_CACHE_TIMEOUT = int(timedelta(days=2).total_seconds())
 SLACK_API_RATE_LIMIT_RETRY_COUNT = 5
 ```
 
-#### Slack Enterprise Grid (org-scoped tokens)
-
-On a Slack Enterprise Grid org, an org-scoped token spans multiple workspaces, so
-workspace-scoped methods such as `conversations.list` require a `team_id` to
-indicate which workspace to target. Set `SLACK_TEAM_ID` to your workspace (team)
-ID so Superset can list channels and deliver reports:
-
-```python
-# The workspace (team) ID to target, e.g. "T01234567"
-SLACK_TEAM_ID = "T01234567"
-```
-
-This defaults to `None` and only needs to be set when using an org-scoped token;
-it is accepted but ignored for standard workspace-level tokens.
-
 ### Webhook integration
 
 Superset can send alert and report notifications to any HTTP endpoint — useful for chat platforms, incident management tools, or custom automation.
@@ -175,7 +160,7 @@ When enabled, Superset rejects webhook configurations that use `http://` URLs.
 
 #### Retry Behavior
 
-Superset automatically retries webhook deliveries on `429 Too Many Requests` and `5xx` server errors using exponential backoff. Retries are bounded to roughly 120 seconds of cumulative wall-clock time (worst case ~210 seconds, because the bound is checked against the time elapsed before each attempt, so the final request can begin just under the limit and still run its full request timeout), after which the delivery is abandoned.
+Superset automatically retries webhook deliveries on `429 Too Many Requests` and `5xx` server errors using exponential backoff.
 
 ### Kubernetes-specific
 

docs/admin_docs/configuration/aws-iam.mdx

@@ -1,7 +1,25 @@
+{/*
+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.
+*/}
+
 ---
 title: AWS IAM Authentication
 sidebar_label: AWS IAM Authentication
-version: 1
 sidebar_position: 15
 ---
 

docs/admin_docs/configuration/configuring-superset.mdx

@@ -549,24 +549,6 @@ CELERY_BEAT_SCHEDULE = {
 
 Adjust `retention_period_days` to control how long query rows are kept. Companion opt-in tasks (`prune_logs`, `prune_tasks`) exist for pruning the logs and tasks tables; see the commented-out examples in `superset/config.py`. Without enabling these tasks, the metadata database will grow unbounded over time.
 
-## Dashboard Layout Size Limit
-
-Each dashboard stores its layout (the position, size, and nesting of every chart, row, and tab) as a JSON blob in the metadata database. Superset caps the length of this serialized blob with `SUPERSET_DASHBOARD_POSITION_DATA_LIMIT`, which defaults to `65535`:
-
-```python
-SUPERSET_DASHBOARD_POSITION_DATA_LIMIT = 65535
-```
-
-This is a Python-level cap (65535 is 2¹⁶ − 1), independent of the database column capacity — the `position_json` column is a `MEDIUMTEXT`, which holds far more. When the serialized layout reaches this limit, the editor blocks the save and reports the current length, the limit, and this setting's name. A warning is shown once the layout passes 90% of the limit.
-
-Large dashboards — for example, many charts spread across nested tabs — can exceed the default. Because the underlying column comfortably stores larger values, you can safely raise the limit:
-
-```python
-SUPERSET_DASHBOARD_POSITION_DATA_LIMIT = 131072  # double the default
-```
-
-Alternatively, split a very large dashboard into several smaller ones. Note that this check is enforced when saving layout edits in the UI; a dashboard imported from a ZIP with an oversized layout will load and render, but cannot be edited and re-saved until the limit is raised.
-
 :::resources
 - [Blog: Feature Flags in Apache Superset](https://preset.io/blog/feature-flags-in-apache-superset-and-preset/)
 :::

docs/admin_docs/installation/docker-compose.mdx

@@ -223,9 +223,8 @@ compose based installation, edit the `x-superset-image:` line in your `docker-co
 `docker-compose-non-dev.yml` files, replacing `apachesuperset.docker.scarf.sh/apache/superset` with
 `apache/superset` to pull the image directly from Docker Hub.
 
-To disable the Scarf telemetry pixel, set the `SCARF_ANALYTICS` environment variable to `false` in
-your `docker/.env` file. This is read at runtime, so it disables the pixel on the pre-built image
-without rebuilding the frontend.
+To disable the Scarf telemetry pixel, set the `SCARF_ANALYTICS` environment variable to `False` in
+your terminal and/or in your `docker/.env` file.
 :::
 
 ## 3. Log in to Superset

docs/admin_docs/installation/kubernetes.mdx

@@ -136,17 +136,7 @@ init:
 :::note
 Superset uses [Scarf Gateway](https://about.scarf.sh/scarf-gateway) to collect telemetry data.  Knowing the installation counts for different Superset versions informs the  project's decisions about patching and long-term support. Scarf purges personally identifiable information (PII) and provides only aggregated statistics.
 
-There are two independent telemetry channels:
-
-- **Image pulls** (Scarf Gateway): to opt out, edit the `repository:` line in your `helm/superset/values.yaml` file, replacing `apachesuperset.docker.scarf.sh/apache/superset` with `apache/superset` to pull the image directly from Docker Hub.
-- **The analytics pixel** rendered in the UI: to opt out, set the `SCARF_ANALYTICS` environment variable to `false` on the Superset containers via `extraEnv` in your `values.yaml`:
-
-  ```yaml
-  extraEnv:
-    SCARF_ANALYTICS: "false"
-  ```
-
-  This is read at runtime, so it takes effect on the pre-built images without rebuilding the frontend.
+To opt-out of this data collection in your Helm-based installation, edit the `repository:` line in your `helm/superset/values.yaml` file, replacing `apachesuperset.docker.scarf.sh/apache/superset` with `apache/superset` to pull the image directly from Docker Hub.
 :::
 
 ### Dependencies

docs/admin_docs/security/securing_superset.mdx

@@ -161,7 +161,6 @@ Here's the documentation section how how to set up Talisman: https://superset.ap
 
   - [ ] Regularly update to the latest major or minor versions of Superset. Those versions receive up-to-date security patches.
   - [ ] Rotate the `SUPERSET_SECRET_KEY` periodically (e.g., quarterly) and after any potential security incident.
-  - [ ] Rotate the other security-critical secrets (guest-token and async-query JWT secrets, SMTP and database credentials) on the cadence in Appendix C, and after any potential security incident.
   - [ ] Conduct quarterly access reviews for all users.
   - [ ] Assuming logging and monitoring is in place, review security monitoring alerts weekly.
 
@@ -174,24 +173,6 @@ Rotating the `SUPERSET_SECRET_KEY` is a critical security procedure. It is manda
 The procedure for safely rotating the SECRET_KEY must be followed precisely to avoid locking yourself out of your instance. The official Apache Superset documentation maintains the correct, up-to-date procedure. Please follow the official guide here:
 https://superset.apache.org/admin-docs/configuration/configuring-superset/#rotating-to-a-newer-secret_key
 
-### **Appendix C: Secrets Register and Rotation Schedule**
-
-`SUPERSET_SECRET_KEY` is not the only security-critical secret in a Superset deployment. Maintain an inventory of all such secrets, store each in a secrets manager (not in `superset_config.py` or version control), assign an owner, and rotate them on a defined cadence as well as after any suspected compromise.
-
-| Secret | Purpose | Risk if leaked | Suggested rotation |
-|---|---|---|---|
-| `SUPERSET_SECRET_KEY` | Signs session cookies; key material for encrypting stored DB credentials (Fernet/AES) | Forged sessions (auth bypass / privilege escalation); decryption of exfiltrated metadata-DB secrets | Quarterly + post-incident |
-| `GUEST_TOKEN_JWT_SECRET` | Signs embedded-dashboard guest tokens | Forged guest tokens → unauthorized dashboard/data access | Quarterly + post-incident |
-| `GLOBAL_ASYNC_QUERIES_JWT_SECRET` | Signs the async-query channel JWT | Forged async-query tokens | Quarterly + post-incident |
-| SMTP password | Outbound email for alerts & reports | Email relay abuse / spoofing | Per organizational policy + post-incident |
-| Database connection passwords | Access to analytical databases and the metadata DB | Direct database access | Per organizational policy + post-incident |
-
-Notes:
-
-- 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.
-
 :::resources
 - [Blog: Running Apache Superset on the Open Internet](https://preset.io/blog/running-apache-superset-on-the-open-internet-a-report-from-the-fireline/)
 - [Blog: How Security Vulnerabilities are Reported & Handled in Apache Superset](https://preset.io/blog/how-security-vulnerabilities-are-reported-and-handled-in-apache-superset/)

docs/developer_docs/contributing/howtos.md

@@ -332,39 +332,15 @@ cd superset-frontend
 npm run build-translation
 
 # Backend
-pybabel compile --use-fuzzy -d superset/translations
+pybabel compile -d superset/translations
 ```
 
-`--use-fuzzy` includes `#, fuzzy` entries in the compiled `.mo` files. Superset
-serves fuzzy translations on purpose: the frontend build (`po2json --fuzzy`)
-already includes them, `flask fab babel-compile` (used by the release images)
-compiles with `-f`, and the production `Dockerfile` compiles with `--use-fuzzy`
-as well. This keeps machine-generated (and other draft) translations visible in
-the UI rather than falling back to English while they await review.
-
 ### Backfilling missing translations with AI
 
 For languages with many untranslated strings, the repo includes a script that
 uses Claude AI to generate draft translations for any missing entries. All
 AI-generated strings are marked `#, fuzzy` and tagged with an attribution
-comment so that human reviewers know they need to be checked.
-
-Note that `#, fuzzy` marks a translation as *needing review*, not as *withheld*:
-both the frontend and backend builds serve fuzzy entries (see [Applying
-translations](#applying-translations) above), so an AI-generated string is shown
-in the UI as soon as it is built and deployed. Reviewers should verify each
-entry and remove the `#, fuzzy` flag to promote it to a confirmed translation.
-
-The script never touches entries that must stay literal — icon names, enum
-values, SQL keywords, API field names, and example placeholders. These are
-registered in `superset/translations/do-not-translate.txt`;
-`scripts/translations/apply_do_not_translate.py` stamps them in `messages.pot`
-with a `#. do-not-translate` extracted comment (run automatically
-from `babel_update.sh`), which `pybabel update` then propagates to every
-catalog. To mark a new string do-not-translate, add its msgid to the registry.
-The backfill also honors that marker and any legacy do-not-translate translator
-comment (e.g. the `ru` catalog's `# Не переводить`), leaving such entries
-untranslated so they fall back to the source token.
+comment so that human reviewers know they need to be checked before merging.
 
 #### Prerequisites
 

docs/developer_docs/extensions/contribution-types.md

@@ -34,14 +34,15 @@ Frontend contribution types allow extensions to extend Superset's user interface
 
 Extensions can add new views or panels to the host application, such as custom SQL Lab panels, dashboards, or other UI components. Contribution areas are uniquely identified (e.g., `sqllab.panels` for SQL Lab panels), enabling seamless integration into specific parts of the application.
 
-```typescript
+```tsx
+import React from 'react';
 import { views } from '@apache-superset/core';
 import MyPanel from './MyPanel';
 
 views.registerView(
   { id: 'my-extension.main', name: 'My Panel Name' },
   'sqllab.panels',
-  MyPanel,
+  () => <MyPanel />,
 );
 ```
 
@@ -111,45 +112,6 @@ editors.registerEditor(
 
 See [Editors Extension Point](./extension-points/editors.md) for implementation details.
 
-### Chat
-
-Extensions can add a chat interface to Superset by registering a trigger component and a panel component. The host owns the layout, open/close state, and display mode — the extension only provides the UI. The panel can be displayed as a floating overlay or docked as a resizable sidebar beside the page content, and the user's preference is persisted across reloads.
-
-```tsx
-import { chat } from '@apache-superset/core';
-import ChatTrigger from './ChatTrigger';
-import ChatPanel from './ChatPanel';
-
-chat.registerChat(
-  { id: 'my-org.my-chat', name: 'My Chat' },
-  ChatTrigger,
-  ChatPanel,
-);
-```
-
-See [Chat](./extension-points/chat.md) for implementation details.
-
-### Dashboard Components
-
-Extensions can add first-class layout components to the dashboard builder — elements that live in the grid alongside charts, Markdown, and tabs. The host owns the drag/resize/delete chrome, so the extension only provides the component that renders the element's content. The built-in iframe component is implemented through this contribution point.
-
-```tsx
-import { dashboardComponents } from '@apache-superset/core';
-import WeatherWidget from './WeatherWidget';
-
-dashboardComponents.registerDashboardComponent(
-  {
-    id: 'my-org.weather',
-    name: 'Weather widget',
-    icon: 'CloudOutlined',
-    defaultMeta: { width: 4, height: 50 },
-  },
-  WeatherWidget,
-);
-```
-
-See [Dashboard Components](./extension-points/dashboard-components.md) for implementation details.
-
 ## Backend
 
 Backend contribution types allow extensions to extend Superset's server-side capabilities. Backend contributions are registered at startup via classes and functions imported from the auto-discovered `entrypoint.py` file.

docs/developer_docs/extensions/extension-points/chat.md

@@ -1,141 +0,0 @@
----
-title: Chat
-sidebar_position: 3
----
-
-<!--
-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.
--->
-
-# Chat Contributions
-
-Extensions can add a chat interface to Superset by registering a trigger and a panel. The host owns the layout, open/close state, and display mode — the extension only needs to provide the UI components.
-
-## Overview
-
-A chat registration consists of two React components:
-
-| Component | Role |
-|-----------|------|
-| **Trigger** | Always-visible entry point (e.g., a floating button). Rendered in the bottom-right corner in floating mode, or as a fixed overlay in panel mode. |
-| **Panel** | The chat UI itself (message list, input, etc.). Mounted by the host in the active display mode. |
-
-## Display Modes
-
-The host supports two display modes, switchable by the user or the extension at runtime:
-
-| Mode | Behavior |
-|------|----------|
-| `floating` | Panel floats above page content, anchored to the bottom-right corner. |
-| `panel` | Panel is docked to the right side of the application as a resizable sidebar, sitting beside the page content. |
-
-The user's last selected mode and open/closed state are persisted across page reloads.
-
-## Registering a Chat
-
-Call `chat.registerChat` from your extension's entry point with a descriptor, a trigger factory, and a panel factory:
-
-```tsx
-import { chat } from '@apache-superset/core';
-import ChatTrigger from './ChatTrigger';
-import ChatPanel from './ChatPanel';
-
-chat.registerChat(
-  { id: 'my-org.my-chat', name: 'My Chat' },
-  ChatTrigger,
-  ChatPanel,
-);
-```
-
-Only one chat registration is active at a time. If a second extension calls `registerChat`, it replaces the first and a warning is logged.
-
-## Opening and Closing the Chat
-
-The trigger component is responsible for toggling the panel. Use `chat.isOpen()`, `chat.open()`, and `chat.close()` to control visibility:
-
-```tsx
-import { chat } from '@apache-superset/core';
-
-export default function ChatTrigger() {
-  return (
-    <button onClick={() => (chat.isOpen() ? chat.close() : chat.open())}>
-      💬
-    </button>
-  );
-}
-```
-
-You can also subscribe to open/close events from any component:
-
-```tsx
-useEffect(() => {
-  const { dispose } = chat.onDidOpen(() => console.log('chat opened'));
-  return dispose;
-}, []);
-```
-
-## Changing the Display Mode
-
-Call `chat.setDisplayMode` to switch between `'floating'` and `'panel'` modes. In your panel component, subscribe to `onDidChangeDisplayMode` to react to changes (including those triggered by the user):
-
-```tsx
-import { useState, useEffect } from 'react';
-import { chat } from '@apache-superset/core';
-
-export default function ChatPanel() {
-  const [mode, setMode] = useState(chat.getDisplayMode());
-
-  useEffect(() => {
-    const { dispose } = chat.onDidChangeDisplayMode(m => setMode(m));
-    return dispose;
-  }, []);
-
-  return (
-    <div style={{ height: mode === 'panel' ? '100%' : '80vh' }}>
-      <button onClick={() => chat.setDisplayMode(mode === 'panel' ? 'floating' : 'panel')}>
-        {mode === 'panel' ? 'Float' : 'Dock'}
-      </button>
-      {/* message list and input */}
-    </div>
-  );
-}
-```
-
-## Chat API Reference
-
-All methods are available on the `chat` namespace from `@apache-superset/core`:
-
-| Method / Event | Description |
-|----------------|-------------|
-| `registerChat(descriptor, trigger, panel)` | Register a chat extension. Returns a `Disposable` to unregister. |
-| `open()` | Open the chat panel. No-op if already open or no registration. |
-| `close()` | Close the chat panel. |
-| `isOpen()` | Returns `true` if the panel is currently open. |
-| `getDisplayMode()` | Returns the current display mode (`'floating'` or `'panel'`). |
-| `setDisplayMode(mode)` | Switch between `'floating'` and `'panel'` mode. |
-| `onDidOpen(listener)` | Subscribe to panel open events. Returns a `Disposable`. |
-| `onDidClose(listener)` | Subscribe to panel close events. Returns a `Disposable`. |
-| `onDidChangeDisplayMode(listener)` | Subscribe to display mode changes. Returns a `Disposable`. |
-| `onDidRegisterChat(listener)` | Subscribe to registration events. |
-| `onDidUnregisterChat(listener)` | Subscribe to unregistration events. |
-| `onDidResizePanel(listener)` | Subscribe to panel resize events (panel mode only). Not all hosts provide a resizer — do not rely on this firing. Returns a `Disposable`. |
-
-## Next Steps
-
-- **[Contribution Types](../contribution-types.md)** — Explore other contribution types
-- **[Development](../development.md)** — Set up your development environment

docs/developer_docs/extensions/extension-points/dashboard-components.md

@@ -1,155 +0,0 @@
----
-title: Dashboard Components
-sidebar_position: 4
----
-
-<!--
-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 Component Contributions
-
-Extensions can add first-class **layout components** to the dashboard builder —
-elements that sit in the grid alongside charts, Markdown, and tabs. The built-in
-iframe component is itself implemented through this contribution point.
-
-The host owns the surrounding **chrome** (the drag handle, the resize container,
-and the delete affordance), so your component only renders its content and, in
-edit mode, its own editor affordances. This keeps the contract small and stable.
-
-> This supersedes the legacy `DashboardComponentsRegistry` / `DYNAMIC_TYPE`
-> mechanism, which is deprecated.
-
-## Overview
-
-A dashboard component contribution is:
-
-| Part | Role |
-|------|------|
-| **Definition** | A descriptor declaring the component's id, palette label, icon, and layout behavior (resizable, default size, nesting). |
-| **Component** | A React component that renders the element's content and receives the [`DashboardComponentProps`](#component-contract) contract. |
-
-## The Component Contract
-
-Your component receives a small, stable set of props. It never deals with drag,
-resize, or delete — the host renders it inside that chrome.
-
-```ts
-interface DashboardComponentProps {
-  /** The layout item id of this instance. */
-  id: string;
-  /** This instance's persisted meta (round-trips in the saved layout). */
-  meta: Record<string, unknown>;
-  /** Whether the dashboard is in edit mode. */
-  editMode: boolean;
-  /** Shallow-merge a patch into this instance's persisted meta. */
-  updateMeta: (patch: Record<string, unknown>) => void;
-}
-```
-
-Persist any per-instance state in `meta` via `updateMeta`. It is saved with the
-dashboard and rehydrated on load.
-
-## Registering a Dashboard Component
-
-Call `dashboardComponents.registerDashboardComponent` from your extension's entry
-point with a definition and your component:
-
-```tsx
-import { dashboardComponents } from '@apache-superset/core';
-import WeatherWidget from './WeatherWidget';
-
-dashboardComponents.registerDashboardComponent(
-  {
-    id: 'my-org.weather',
-    name: 'Weather widget',
-    description: 'Shows the current weather for a city',
-    icon: 'CloudOutlined',
-    resizable: true,
-    defaultMeta: { width: 4, height: 50, city: 'Lisbon' },
-  },
-  WeatherWidget,
-);
-```
-
-```tsx
-// WeatherWidget.tsx
-import type { dashboardComponents } from '@apache-superset/core';
-
-type Props = dashboardComponents.DashboardComponentProps;
-
-export default function WeatherWidget({ meta, editMode, updateMeta }: Props) {
-  const city = (meta.city as string) ?? '';
-  return editMode ? (
-    <input
-      value={city}
-      onChange={e => updateMeta({ city: e.target.value })}
-      placeholder="City"
-    />
-  ) : (
-    <Forecast city={city} />
-  );
-}
-```
-
-The component appears in the dashboard builder's **Layout elements** palette and
-can be dragged onto the grid like any built-in element.
-
-## Definition Reference
-
-| Field | Type | Description |
-|-------|------|-------------|
-| `id` | `string` | Namespaced unique id, e.g. `my-org.weather`. Selects the component for each instance. |
-| `name` | `string` | Label shown in the builder palette. |
-| `description` | `string` | Optional longer description. |
-| `icon` | `string` | A known Superset icon name (e.g. `CloudOutlined`). Falls back to a generic icon. |
-| `resizable` | `boolean` | Whether instances can be resized. Defaults to `true`. |
-| `defaultMeta` | `object` | `meta` seeded onto a new instance (e.g. `width`, `height`, and your own keys). |
-| `isUserContent` | `boolean` | Whether an instance counts as content for "is this dashboard empty?" detection. Defaults to `true`. |
-| `minWidth` | `number` | Minimum width in grid columns. Defaults to `1`. |
-| `validParents` | `string[]` | Restrict which container types may hold the component (e.g. `['GRID', 'TAB']`). Defaults to standard content-leaf placement (grid, row, column, tab). |
-| `wrapInRow` | `boolean` | Whether a drop into the grid or a tab auto-wraps the component in a row. Defaults to `true`. |
-
-The layout-relevant behavior fields are seeded onto each instance's `meta` at
-creation, so the dashboard honors them — and they round-trip in the saved layout
-even if the extension later becomes unavailable.
-
-## Graceful Degradation
-
-If a saved dashboard references a component whose extension is disabled or not
-yet loaded, the host renders a non-destructive placeholder in its place and
-preserves the instance's `meta` on save. Re-enabling the extension restores the
-component.
-
-## Dashboard Components API Reference
-
-All methods are available on the `dashboardComponents` namespace from
-`@apache-superset/core`:
-
-| Method / Event | Description |
-|----------------|-------------|
-| `registerDashboardComponent(definition, component)` | Register a component. Returns a `Disposable` to unregister. Registering the same id again replaces the previous registration. |
-| `getDashboardComponent(id)` | Returns the registered component for `id`, or `undefined`. |
-| `getDashboardComponents()` | Returns all registered components. |
-| `onDidRegisterDashboardComponent(listener)` | Subscribe to registration events. Returns a `Disposable`. |
-| `onDidUnregisterDashboardComponent(listener)` | Subscribe to unregistration events. Returns a `Disposable`. |
-
-## Next Steps
-
-- **[Contribution Types](../contribution-types.md)** — Explore other contribution types
-- **[Development](../development.md)** — Set up your development environment

docs/developer_docs/sidebars.js

@@ -47,9 +47,6 @@ module.exports = {
           collapsed: true,
           items: [
             'extensions/extension-points/sqllab',
-            'extensions/extension-points/editors',
-            'extensions/extension-points/chat',
-            'extensions/extension-points/dashboard-components',
           ],
         },
         'extensions/development',

docs/docs/faq.mdx

@@ -321,8 +321,8 @@ This can be used, for example, to convert UTC time to local time.
 Superset uses [Scarf](https://about.scarf.sh/) by default to collect basic telemetry data upon installing and/or running Superset. This data helps the maintainers of Superset better understand which versions of Superset are being used, in order to prioritize patch/minor releases and security fixes.
 We use the [Scarf Gateway](https://docs.scarf.sh/gateway/) to sit in front of container registries, the [scarf-js](https://about.scarf.sh/package-sdks) package to track `npm` installations, and a Scarf pixel to gather anonymous analytics on Superset page views.
 Scarf purges PII and provides aggregated statistics. Superset users can easily opt out of analytics in various ways documented [here](https://docs.scarf.sh/gateway/#do-not-track) and [here](https://docs.scarf.sh/package-analytics/#as-a-user-of-a-package-using-scarf-js-how-can-i-opt-out-of-analytics).
-You can also opt out of the analytics pixel by setting the `SCARF_ANALYTICS` environment variable to `false`. This is read at runtime, so setting it on the Superset container (for example via `extraEnv` in the Helm chart, or `docker/.env` for Docker Compose) disables the pixel on the pre-built images without rebuilding the frontend. Note that this only disables the page-view pixel; the Scarf Gateway (container registry) and `scarf-js` (`npm`) channels are opted out separately, as described above.
-Additional opt-out instructions are available on the [Docker Compose](/admin-docs/installation/docker-compose) and [Kubernetes](/admin-docs/installation/kubernetes) installation pages.
+Superset maintainers can also opt out of telemetry data collection by setting the `SCARF_ANALYTICS` environment variable to `false` in the Superset container (or anywhere Superset/webpack are run).
+Additional opt-out instructions for Docker users are available on the [Docker Installation](/admin-docs/installation/docker-compose) page.
 
 ## Does Superset have an archive panel or trash bin from which a user can recover deleted assets?
 

docs/docs/index.mdx

@@ -254,13 +254,16 @@ Understanding the Superset Points of View
 
 - [Superset API](/developer-docs/api)
 
-<!--
-  The OSS Insight "Repo Activity" widget (https://next.ossinsight.io/) was
-  intentionally removed. This page is rendered on the ASF-hosted website
-  (superset.apache.org), so its contents are subject to ASF's third-party
-  content and CSP rules. OSS Insight has no Data Processing Agreement (DPA)
-  with the ASF, so we cannot embed its images/widgets here. Do not re-add it.
--->
+## Repo Activity
+
+<a href="https://next.ossinsight.io/widgets/official/compose-last-28-days-stats?repo_id=39464018" target="_blank" align="center">
+  <picture>
+    <source media="(prefers-color-scheme: dark)" srcset="https://next.ossinsight.io/widgets/official/compose-last-28-days-stats/thumbnail.png?repo_id=39464018&image_size=auto&color_scheme=dark" width="655" height="auto" />
+    <img alt="Performance Stats of apache/superset - Last 28 days" src="https://next.ossinsight.io/widgets/official/compose-last-28-days-stats/thumbnail.png?repo_id=39464018&image_size=auto&color_scheme=light" width="655" height="auto" />
+  </picture>
+</a>
+
+<!-- Made with [OSS Insight](https://ossinsight.io/) -->
 
 <!-- telemetry/analytics pixel: -->
 <img referrerpolicy="no-referrer-when-downgrade" src="https://static.scarf.sh/a.png?x-pxid=bc1c90cd-bc04-4e11-8c7b-289fb2839492" />

docs/docusaurus.config.ts

@@ -749,7 +749,7 @@ const config: Config = {
           showReadingTime: true,
           // Please change this to your repo.
           editUrl:
-            'https://github.com/apache/superset/tree/master/docs',
+            'https://github.com/facebook/docusaurus/edit/main/website/blog/',
         },
         theme: {
           customCss: require.resolve('./src/styles/custom.css'),

docs/package.json

@@ -58,15 +58,26 @@
     "@fontsource/inter": "^5.2.8",
     "@mdx-js/react": "^3.1.1",
     "@saucelabs/theme-github-codeblock": "^0.3.0",
-    "@storybook/addon-docs": "^10.4.5",
+    "@storybook/addon-docs": "^8.6.18",
+    "@storybook/blocks": "^8.6.15",
+    "@storybook/channels": "^8.6.18",
+    "@storybook/client-logger": "^8.6.18",
+    "@storybook/components": "^8.6.18",
+    "@storybook/core": "^8.6.18",
+    "@storybook/core-events": "^8.6.18",
+    "@storybook/csf": "^0.1.13",
+    "@storybook/docs-tools": "^8.6.18",
+    "@storybook/preview-api": "^8.6.18",
+    "@storybook/theming": "^8.6.15",
     "@superset-ui/core": "^0.20.4",
-    "@swc/core": "^1.15.43",
-    "antd": "^6.5.0",
-    "baseline-browser-mapping": "^2.10.40",
+    "@swc/core": "^1.15.41",
+    "antd": "^6.4.4",
+    "baseline-browser-mapping": "^2.10.37",
     "caniuse-lite": "^1.0.30001799",
-    "docusaurus-plugin-openapi-docs": "^5.1.0",
-    "docusaurus-theme-openapi-docs": "^5.1.0",
-    "js-yaml": "^5.2.0",
+    "docusaurus-plugin-openapi-docs": "^5.0.2",
+    "docusaurus-theme-openapi-docs": "^5.0.2",
+    "js-yaml": "^4.2.0",
+    "js-yaml-loader": "^1.2.2",
     "json-bigint": "^1.0.0",
     "prism-react-renderer": "^2.4.1",
     "react": "^18.3.1",
@@ -77,8 +88,8 @@
     "react-table": "^7.8.0",
     "remark-import-partial": "^0.0.2",
     "reselect": "^5.2.0",
-    "storybook": "^10.4.5",
-    "swagger-ui-react": "^5.32.8",
+    "storybook": "^8.6.18",
+    "swagger-ui-react": "^5.32.6",
     "swc-loader": "^0.2.7",
     "tinycolor2": "^1.4.2",
     "unist-util-visit": "^5.1.0"
@@ -95,11 +106,11 @@
     "eslint-config-prettier": "^10.1.8",
     "eslint-plugin-prettier": "^5.5.6",
     "eslint-plugin-react": "^7.37.5",
-    "globals": "^17.7.0",
-    "prettier": "^3.9.1",
+    "globals": "^17.6.0",
+    "prettier": "^3.8.4",
     "typescript": "~6.0.3",
-    "typescript-eslint": "^8.62.0",
-    "webpack": "^5.108.2"
+    "typescript-eslint": "^8.61.1",
+    "webpack": "^5.107.2"
   },
   "browserslist": {
     "production": [
@@ -117,16 +128,13 @@
     "react-redux": "^9.2.0",
     "@reduxjs/toolkit": "^2.5.0",
     "baseline-browser-mapping": "^2.9.19",
+    "swagger-client": "3.37.3",
     "lodash": "4.18.1",
     "lodash-es": "4.18.1",
     "yaml": "1.10.3",
     "uuid": "11.1.1",
     "serialize-javascript": "7.0.5",
-    "d3-color": "3.1.0",
-    "ws": "^8.21.0",
-    "@docusaurus/core/@docusaurus/utils/gray-matter/js-yaml": "^3.15.0",
-    "@docusaurus/core/**/js-yaml": "^4.3.0",
-    "docusaurus-plugin-openapi-docs/**/js-yaml": "^4.3.0"
+    "d3-color": "3.1.0"
   },
   "packageManager": "yarn@1.22.22+sha1.ac34549e6aa8e7ead463a7407e1c7390f61a6610"
 }

docs/src/components/databases/types.ts

@@ -176,7 +176,7 @@ export interface DatabaseInfo {
   expressions_in_orderby?: boolean;
 
   // Platform features
-  limit_method?: number;
+  limit_method?: string;
   limit_clause?: boolean;
   max_column_name?: number;
   supports_file_upload?: boolean;

docs/src/pages/inTheWild.tsx

@@ -19,7 +19,6 @@
 
 import Layout from '@theme/Layout';
 import { Avatar, Card, Col, Collapse, Row, Typography } from 'antd';
-import { load } from 'js-yaml';
 import BlurredSection from '../components/BlurredSection';
 import SectionHeader from '../components/SectionHeader';
 import DataSet from '../../../RESOURCES/INTHEWILD.yaml';
@@ -37,7 +36,7 @@ interface DataSetType {
   categories: Record<string, Organization[]>;
 }
 
-const typedDataSet = load(DataSet) as DataSetType;
+const typedDataSet = DataSet as DataSetType;
 
 const ContributorAvatars = ({ contributors }: { contributors?: string[] }) => {
   if (!contributors?.length) return null;

docs/src/pages/index.tsx

@@ -22,7 +22,6 @@ import Link from '@docusaurus/Link';
 import { Card, Carousel, Flex } from 'antd';
 import styled from '@emotion/styled';
 import GitHubButton from 'react-github-btn';
-import { load } from 'js-yaml';
 import { mq } from '../utils';
 import SectionHeader from '../components/SectionHeader';
 import databaseData from '../data/databases.json';
@@ -61,7 +60,7 @@ interface DataSetType {
   categories: Record<string, Organization[]>;
 }
 
-const typedDataSet = load(DataSet) as DataSetType;
+const typedDataSet = DataSet as DataSetType;
 
 // Extract all organizations with logos for the carousel
 const companiesWithLogos = Object.values(typedDataSet.categories)

docs/src/types/yaml.d.ts

@@ -18,11 +18,11 @@
  */
 
 declare module '*.yaml' {
-  const content: string;
+  const content: unknown;
   export default content;
 }
 
 declare module '*.yml' {
-  const content: string;
+  const content: unknown;
   export default content;
 }

docs/src/webpack.extend.ts

@@ -61,10 +61,10 @@ export default function webpackExtendPlugin(): Plugin<void> {
         );
       });
 
-      // Load YAML file as raw text string
+      // Add YAML loader rule directly to existing rules
       config.module?.rules?.push({
         test: /\.ya?ml$/,
-        type: 'asset/source',
+        use: 'js-yaml-loader',
       });
 
       // Add swc-loader rule for superset-frontend files
@@ -168,6 +168,60 @@ export default function webpackExtendPlugin(): Plugin<void> {
               __dirname,
               '../../superset-frontend/packages/superset-core/src',
             ),
+            // Add proper Storybook aliases
+            '@storybook/blocks': path.resolve(
+              __dirname,
+              '../node_modules/@storybook/blocks',
+            ),
+            '@storybook/components': path.resolve(
+              __dirname,
+              '../node_modules/@storybook/components',
+            ),
+            '@storybook/theming': path.resolve(
+              __dirname,
+              '../node_modules/@storybook/theming',
+            ),
+            '@storybook/client-logger': path.resolve(
+              __dirname,
+              '../node_modules/@storybook/client-logger',
+            ),
+            '@storybook/core-events': path.resolve(
+              __dirname,
+              '../node_modules/@storybook/core-events',
+            ),
+            // Add internal Storybook aliases
+            'storybook/internal/components': path.resolve(
+              __dirname,
+              '../node_modules/@storybook/components',
+            ),
+            'storybook/internal/theming': path.resolve(
+              __dirname,
+              '../node_modules/@storybook/theming',
+            ),
+            'storybook/internal/client-logger': path.resolve(
+              __dirname,
+              '../node_modules/@storybook/client-logger',
+            ),
+            'storybook/internal/csf': path.resolve(
+              __dirname,
+              '../node_modules/@storybook/csf',
+            ),
+            'storybook/internal/preview-api': path.resolve(
+              __dirname,
+              '../node_modules/@storybook/preview-api',
+            ),
+            'storybook/internal/docs-tools': path.resolve(
+              __dirname,
+              '../node_modules/@storybook/docs-tools',
+            ),
+            'storybook/internal/core-events': path.resolve(
+              __dirname,
+              '../node_modules/@storybook/core-events',
+            ),
+            'storybook/internal/channels': path.resolve(
+              __dirname,
+              '../node_modules/@storybook/channels',
+            ),
           },
         },
       };

docs/static/.htaccess

@@ -22,14 +22,7 @@ RewriteRule ^(.*)$ https://superset.apache.org/$1 [R,L]
 RewriteCond %{HTTP_HOST} ^superset.incubator.apache.org$ [NC]
 RewriteRule ^(.*)$ https://superset.apache.org/$1 [R=301,L]
 
-# CSP permissions for superset.apache.org
-# Additional domains required for docs site functionality:
-# - widget.kapa.ai: AI chatbot widget (uses Google reCAPTCHA). Approval here: https://privacy.apache.org/faq/committers.html
-# - *.googleapis.com, *.google.com, *.gstatic.com: Google Calendar embed, kapa.ai reCAPTCHA - all of these loaded with user consent, following policy laid out in https://privacy.apache.org/faq/committers.html
-# - github.com, *.github.com, *.githubusercontent.com: GitHub user-attachment images in docs (apex github.com serves user-attachments/* assets). Discussed/resolved in this thread: https://issues.apache.org/jira/browse/INFRA-25701?filter=-2 (DPA in place with GitHub)
-# - *.algolia.net, *.algolianet.com: Algolia DocSearch. Approved here: https://privacy.apache.org/faq/committers.html
-# See: https://infra.apache.org/tools/csp.html
-SetEnv CSP_PROJECT_DOMAINS "widget.kapa.ai https://*.googleapis.com/ https://*.google.com/ https://*.gstatic.com/ https://github.com/ https://*.github.com/ https://*.githubusercontent.com/ https://*.algolia.net/ https://*.algolianet.com/"
+Header set Content-Security-Policy "default-src data: blob: 'self' *.apache.org widget.kapa.ai *.githubusercontent.com *.scarf.sh *.googleapis.com *.google.com *.run.app *.gstatic.com *.github.com *.algolia.net *.algolianet.com 'unsafe-inline' 'unsafe-eval'; frame-src *; frame-ancestors 'self' *.google.com https://sidebar.bugherd.com; form-action 'self'; worker-src blob:; img-src 'self' blob: data: https:; font-src 'self'; object-src 'none'"
 
 # REDIRECTS
 

docs/static/feature-flags.json

@@ -21,12 +21,6 @@
         "lifecycle": "development",
         "description": "Enables experimental chart plugins"
       },
-      {
-        "name": "CSP_RUNTIME_ALLOWLIST",
-        "default": false,
-        "lifecycle": "development",
-        "description": "Allow users with the \"can write on CSPAllowlist\" permission (Admins by default) to punch holes in the Content Security Policy at runtime, e.g. to allow a new domain to be embedded in a dashboard iframe component. When disabled, the CSP is purely static/deploy-time and the allowlist is ignored."
-      },
       {
         "name": "CSV_UPLOAD_PYARROW_ENGINE",
         "default": false,
@@ -93,12 +87,6 @@
         "lifecycle": "development",
         "description": "Enable semantic layers and show semantic views alongside datasets"
       },
-      {
-        "name": "SOFT_DELETE",
-        "default": false,
-        "lifecycle": "development",
-        "description": "Temporary rollout / kill-switch gate for soft delete (default off = legacy hard delete). An emergency stop, not a clean rollback: flipping ON->OFF resurrects already-soft-deleted rows. Removed (along with its two gate points \u2014 BaseDAO.delete routing and the do_orm_execute visibility listener) once soft delete is stable."
-      },
       {
         "name": "TABLE_V2_TIME_COMPARISON_ENABLED",
         "default": false,
@@ -128,9 +116,9 @@
       },
       {
         "name": "ALERT_REPORT_SLACK_V2",
-        "default": true,
+        "default": false,
         "lifecycle": "testing",
-        "description": "Enables Slack V2 integration for Alerts and Reports. Defaults to True; the legacy Slack v1 path is deprecated and will be removed in the next major release. Operators must grant the Slack bot both the `channels:read` and `groups:read` scopes so existing v1 recipients can be auto-upgraded on their next send. Without those scopes, file uploads fail (Slack retired the `files.upload` endpoint in 2025) and only text-only `chat_postMessage` sends will continue to work via the legacy path."
+        "description": "Enables Slack V2 integration for Alerts and Reports"
       },
       {
         "name": "ALERT_REPORT_WEBHOOK",

docs/tsconfig.json

@@ -30,6 +30,7 @@
   "exclude": [
     "node_modules",
     "../superset-frontend/**/*",
+    "src/webpack.extend.ts",
     "src/shims/**"
   ]
 }

docs/user_docs_versioned_docs/version-6.0.0/configuration/databases.mdx

@@ -519,80 +519,6 @@ For a connection to a SQL endpoint you need to use the HTTP path from the endpoi
 {"connect_args": {"http_path": "/sql/1.0/endpoints/****", "driver_path": "/path/to/odbc/driver"}}
 ```
 
-##### OAuth2 Authentication
-
-Superset supports OAuth2 authentication for Databricks, allowing users to authenticate with their personal Databricks accounts instead of using shared access tokens. This provides better security and audit capabilities.
-
-###### Prerequisites
-
-1. Create an OAuth2 application in your Databricks account:
-   - Go to your Databricks account console
-   - Navigate to **Settings** → **Developer** → **OAuth apps**
-   - Create a new OAuth app with the redirect URI: `http://your-superset-host:port/api/v1/database/oauth2/`
-
-2. Configure OAuth2 in your `superset_config.py`:
-
-```python
-from datetime import timedelta
-
-# OAuth2 configuration for Databricks
-# The authorization endpoint is derived from your Databricks workspace host; the
-# token endpoint must be set explicitly (see notes below).
-DATABASE_OAUTH2_CLIENTS = {
-    "Databricks (legacy)": {
-        "id": "your-databricks-client-id",
-        "secret": "your-databricks-client-secret",
-        "scope": "sql",
-        "token_request_uri": "https://your-workspace-host/oidc/v1/token",
-    },
-    "Databricks": {
-        "id": "your-databricks-client-id",
-        "secret": "your-databricks-client-secret",
-        "scope": "sql",
-        "token_request_uri": "https://your-workspace-host/oidc/v1/token",
-    },
-}
-
-# OAuth2 redirect URI (adjust hostname/port for your setup)
-DATABASE_OAUTH2_REDIRECT_URI = "http://your-superset-host:port/api/v1/database/oauth2/"
-
-# Optional: OAuth2 timeout
-DATABASE_OAUTH2_TIMEOUT = timedelta(seconds=30)
-```
-
-Replace the following placeholders:
-- `your-databricks-client-id`: Your Databricks OAuth2 application client ID
-- `your-databricks-client-secret`: Your Databricks OAuth2 application client secret
-- `your-superset-host:port`: Your Superset instance hostname and port
-
-**Multi-Cloud Provider Support**
-
-Databricks fronts the user-to-machine (U2M) OAuth2 flow on every workspace at
-`https://<workspace-host>/oidc/v1/authorize` and
-`https://<workspace-host>/oidc/v1/token`, regardless of whether the workspace
-runs on AWS, Azure, or GCP. Superset derives the **authorization** endpoint
-directly from your connection's host, so no cloud provider or account/tenant
-identifier needs to be configured.
-
-The **token** endpoint cannot be auto-derived (token exchange has no database
-context to read the host), so you must supply `token_request_uri` in
-`DATABASE_OAUTH2_CLIENTS`, set to `https://<workspace-host>/oidc/v1/token` for
-your workspace.
-
-If you supply a fully-resolved `authorization_request_uri` (and/or
-`token_request_uri`), those values take precedence over the host-derived
-defaults.
-
-###### Usage
-
-Once configured, users can:
-
-1. Connect to Databricks databases normally using access tokens
-2. When querying data, Superset will automatically redirect users to authenticate with Databricks if needed
-3. User-specific OAuth2 tokens will be used for database connections, providing better security and audit trails
-
-This feature works with both "Databricks (legacy)" and "Databricks" engine types and automatically supports all major cloud providers (AWS, Azure, GCP).
-
 #### Denodo
 
 The recommended connector library for Denodo is

docs/user_docs_versioned_docs/version-6.0.0/intro.md

@@ -212,13 +212,16 @@ Understanding the Superset Points of View
 
 - [Superset API](https://superset.apache.org/docs/rest-api)
 
-<!--
-  The OSS Insight "Repo Activity" widget (https://next.ossinsight.io/) was
-  intentionally removed. This page is rendered on the ASF-hosted website
-  (superset.apache.org), so its contents are subject to ASF's third-party
-  content and CSP rules. OSS Insight has no Data Processing Agreement (DPA)
-  with the ASF, so we cannot embed its images/widgets here. Do not re-add it.
--->
+## Repo Activity
+
+<a href="https://next.ossinsight.io/widgets/official/compose-last-28-days-stats?repo_id=39464018" target="_blank" align="center">
+  <picture>
+    <source media="(prefers-color-scheme: dark)" srcset="https://next.ossinsight.io/widgets/official/compose-last-28-days-stats/thumbnail.png?repo_id=39464018&image_size=auto&color_scheme=dark" width="655" height="auto" />
+    <img alt="Performance Stats of apache/superset - Last 28 days" src="https://next.ossinsight.io/widgets/official/compose-last-28-days-stats/thumbnail.png?repo_id=39464018&image_size=auto&color_scheme=light" width="655" height="auto" />
+  </picture>
+</a>
+
+<!-- Made with [OSS Insight](https://ossinsight.io/) -->
 
 <!-- telemetry/analytics pixel: -->
 <img referrerpolicy="no-referrer-when-downgrade" src="https://static.scarf.sh/a.png?x-pxid=bc1c90cd-bc04-4e11-8c7b-289fb2839492" />

docs/user_docs_versioned_docs/version-6.1.0/index.mdx

@@ -254,13 +254,16 @@ Understanding the Superset Points of View
 
 - [Superset API](/developer-docs/api)
 
-<!--
-  The OSS Insight "Repo Activity" widget (https://next.ossinsight.io/) was
-  intentionally removed. This page is rendered on the ASF-hosted website
-  (superset.apache.org), so its contents are subject to ASF's third-party
-  content and CSP rules. OSS Insight has no Data Processing Agreement (DPA)
-  with the ASF, so we cannot embed its images/widgets here. Do not re-add it.
--->
+## Repo Activity
+
+<a href="https://next.ossinsight.io/widgets/official/compose-last-28-days-stats?repo_id=39464018" target="_blank" align="center">
+  <picture>
+    <source media="(prefers-color-scheme: dark)" srcset="https://next.ossinsight.io/widgets/official/compose-last-28-days-stats/thumbnail.png?repo_id=39464018&image_size=auto&color_scheme=dark" width="655" height="auto" />
+    <img alt="Performance Stats of apache/superset - Last 28 days" src="https://next.ossinsight.io/widgets/official/compose-last-28-days-stats/thumbnail.png?repo_id=39464018&image_size=auto&color_scheme=light" width="655" height="auto" />
+  </picture>
+</a>
+
+<!-- Made with [OSS Insight](https://ossinsight.io/) -->
 
 <!-- telemetry/analytics pixel: -->
 <img referrerpolicy="no-referrer-when-downgrade" src="https://static.scarf.sh/a.png?x-pxid=bc1c90cd-bc04-4e11-8c7b-289fb2839492" />

docs/user_docs_versioned_docs/version-6.1.0/intro.md

@@ -246,13 +246,16 @@ Understanding the Superset Points of View
 
 - [Superset API](https://superset.apache.org/docs/rest-api)
 
-<!--
-  The OSS Insight "Repo Activity" widget (https://next.ossinsight.io/) was
-  intentionally removed. This page is rendered on the ASF-hosted website
-  (superset.apache.org), so its contents are subject to ASF's third-party
-  content and CSP rules. OSS Insight has no Data Processing Agreement (DPA)
-  with the ASF, so we cannot embed its images/widgets here. Do not re-add it.
--->
+## Repo Activity
+
+<a href="https://next.ossinsight.io/widgets/official/compose-last-28-days-stats?repo_id=39464018" target="_blank" align="center">
+  <picture>
+    <source media="(prefers-color-scheme: dark)" srcset="https://next.ossinsight.io/widgets/official/compose-last-28-days-stats/thumbnail.png?repo_id=39464018&image_size=auto&color_scheme=dark" width="655" height="auto" />
+    <img alt="Performance Stats of apache/superset - Last 28 days" src="https://next.ossinsight.io/widgets/official/compose-last-28-days-stats/thumbnail.png?repo_id=39464018&image_size=auto&color_scheme=light" width="655" height="auto" />
+  </picture>
+</a>
+
+<!-- Made with [OSS Insight](https://ossinsight.io/) -->
 
 <!-- telemetry/analytics pixel: -->
 <img referrerpolicy="no-referrer-when-downgrade" src="https://static.scarf.sh/a.png?x-pxid=bc1c90cd-bc04-4e11-8c7b-289fb2839492" />

helm/superset/Chart.yaml

@@ -29,7 +29,7 @@ maintainers:
   - name: craig-rueda
     email: craig@craigrueda.com
     url: https://github.com/craig-rueda
-version: 0.19.0 # See [README](https://github.com/apache/superset/blob/master/helm/superset/README.md#versioning) for version details.
+version: 0.17.2 # See [README](https://github.com/apache/superset/blob/master/helm/superset/README.md#versioning) for version details.
 dependencies:
   - name: postgresql
     version: 16.7.27

helm/superset/README.md

@@ -23,7 +23,7 @@ NOTE: This file is generated by helm-docs: https://github.com/norwoodj/helm-docs
 
 # superset
 
-![Version: 0.19.0](https://img.shields.io/badge/Version-0.19.0-informational?style=flat-square)
+![Version: 0.17.2](https://img.shields.io/badge/Version-0.17.2-informational?style=flat-square)
 
 Apache Superset is a modern, enterprise-ready business intelligence web application
 
@@ -46,21 +46,6 @@ It should be a long random bytes or str.
 
 On helm this can be set on `extraSecretEnv.SUPERSET_SECRET_KEY` or `configOverrides.secrets`
 
-## Upgrade Notes
-
-### Kubernetes recommended labels (breaking)
-
-This chart labels and selects workloads using the [Kubernetes recommended labels](https://kubernetes.io/docs/concepts/overview/working-with-objects/common-labels/) (`app.kubernetes.io/*`) instead of the legacy `app`/`release` labels. A Deployment's `spec.selector.matchLabels` is immutable, so `helm upgrade` against a release created before this change fails with a `field is immutable` error.
-
-To upgrade an existing release, delete the affected workloads first (their selector labels changed), then upgrade so they are recreated:
-
-```console
-kubectl delete deployment,statefulset -l release=<release-name> -n <namespace>
-helm upgrade <release-name> superset/superset
-```
-
-Alternatively, perform a fresh install. This is a one-time migration; subsequent upgrades are unaffected.
-
 ## Requirements
 
 | Repository | Name | Version |
@@ -103,7 +88,6 @@ Alternatively, perform a fresh install. This is a one-time migration; subsequent
 | ingress.path | string | `"/"` |  |
 | ingress.pathType | string | `"ImplementationSpecific"` |  |
 | ingress.tls | list | `[]` |  |
-| init.additionalPodSpec | object | `{}` | Custom pod spec to be added to init job |
 | init.adminUser.email | string | `"admin@superset.com"` |  |
 | init.adminUser.firstname | string | `"Superset"` |  |
 | init.adminUser.lastname | string | `"Admin"` |  |
@@ -147,7 +131,6 @@ Alternatively, perform a fresh install. This is a one-time migration; subsequent
 | supersetCeleryBeat.affinity | object | `{}` | Affinity to be added to supersetCeleryBeat deployment |
 | supersetCeleryBeat.command | list | a `celery beat` command | Command |
 | supersetCeleryBeat.containerSecurityContext | object | `{}` |  |
-| supersetCeleryBeat.deploymentAdditionalPodSpec | object | `{}` | Custom pod spec to be added to supersetCeleryBeat deployment |
 | supersetCeleryBeat.deploymentAnnotations | object | `{}` | Annotations to be added to supersetCeleryBeat deployment |
 | supersetCeleryBeat.enabled | bool | `false` | This is only required if you intend to use alerts and reports |
 | supersetCeleryBeat.extraContainers | list | `[]` | Launch additional containers into supersetCeleryBeat pods |
@@ -166,7 +149,6 @@ Alternatively, perform a fresh install. This is a one-time migration; subsequent
 | supersetCeleryFlower.affinity | object | `{}` | Affinity to be added to supersetCeleryFlower deployment |
 | supersetCeleryFlower.command | list | a `celery flower` command | Command |
 | supersetCeleryFlower.containerSecurityContext | object | `{}` |  |
-| supersetCeleryFlower.deploymentAdditionalPodSpec | object | `{}` | Custom pod spec to be added to supersetCeleryFlower deployment |
 | supersetCeleryFlower.deploymentAnnotations | object | `{}` | Annotations to be added to supersetCeleryFlower deployment |
 | supersetCeleryFlower.enabled | bool | `false` | Enables a Celery flower deployment (management UI to monitor celery jobs) WARNING: on superset 1.x, this requires a Superset image that has `flower<1.0.0` installed (which is NOT the case of the default images) flower>=1.0.0 requires Celery 5+ which Superset 1.5 does not support |
 | supersetCeleryFlower.extraContainers | list | `[]` | Launch additional containers into supersetCeleryFlower pods |
@@ -222,14 +204,12 @@ Alternatively, perform a fresh install. This is a one-time migration; subsequent
 | supersetNode.connections.db_user | string | `"superset"` |  |
 | supersetNode.connections.redis_cache_db | string | `"1"` |  |
 | supersetNode.connections.redis_celery_db | string | `"0"` |  |
-| supersetNode.connections.redis_driver | string | `""` |  |
 | supersetNode.connections.redis_host | string | `"{{ .Release.Name }}-redis-headless"` | Change in case of bringing your own redis and then also set redis.enabled:false |
 | supersetNode.connections.redis_port | string | `"6379"` |  |
 | supersetNode.connections.redis_ssl.enabled | bool | `false` |  |
 | supersetNode.connections.redis_ssl.ssl_cert_reqs | string | `"CERT_NONE"` |  |
 | supersetNode.connections.redis_user | string | `""` |  |
 | supersetNode.containerSecurityContext | object | `{}` |  |
-| supersetNode.deploymentAdditionalPodSpec | object | `{}` | Custom pod spec to be added to supersetNode deployment |
 | supersetNode.deploymentAnnotations | object | `{}` | Annotations to be added to supersetNode deployment |
 | supersetNode.deploymentLabels | object | `{}` | Labels to be added to supersetNode deployment |
 | supersetNode.env | object | `{}` |  |
@@ -275,7 +255,6 @@ Alternatively, perform a fresh install. This is a one-time migration; subsequent
 | supersetWebsockets.command | list | `[]` |  |
 | supersetWebsockets.config | object | see `values.yaml` | The config.json to pass to the server, see https://github.com/apache/superset/tree/master/superset-websocket Note that the configuration can also read from environment variables (which will have priority), see https://github.com/apache/superset/blob/master/superset-websocket/src/config.ts for a list of supported variables |
 | supersetWebsockets.containerSecurityContext | object | `{}` |  |
-| supersetWebsockets.deploymentAdditionalPodSpec | object | `{}` | Custom pod spec to be added to supersetWebsockets deployment |
 | supersetWebsockets.deploymentAnnotations | object | `{}` |  |
 | supersetWebsockets.enabled | bool | `false` | This is only required if you intend to use `GLOBAL_ASYNC_QUERIES` in `ws` mode see https://superset.apache.org/docs/contributing/misc#async-chart-queries |
 | supersetWebsockets.extraContainers | list | `[]` | Launch additional containers into supersetWebsockets pods |
@@ -329,7 +308,6 @@ Alternatively, perform a fresh install. This is a one-time migration; subsequent
 | supersetWorker.autoscaling.targetCPUUtilizationPercentage | int | `80` |  |
 | supersetWorker.command | list | a `celery worker` command | Worker startup command |
 | supersetWorker.containerSecurityContext | object | `{}` |  |
-| supersetWorker.deploymentAdditionalPodSpec | object | `{}` | Custom pod spec to be added to supersetWorker deployment |
 | supersetWorker.deploymentAnnotations | object | `{}` | Annotations to be added to supersetWorker deployment |
 | supersetWorker.deploymentLabels | object | `{}` | Labels to be added to supersetWorker deployment |
 | supersetWorker.extraContainers | list | `[]` | Launch additional containers into supersetWorker pod |

helm/superset/README.md.gotmpl

@@ -45,21 +45,6 @@ It should be a long random bytes or str.
 
 On helm this can be set on `extraSecretEnv.SUPERSET_SECRET_KEY` or `configOverrides.secrets`
 
-## Upgrade Notes
-
-### Kubernetes recommended labels (breaking)
-
-This chart labels and selects workloads using the [Kubernetes recommended labels](https://kubernetes.io/docs/concepts/overview/working-with-objects/common-labels/) (`app.kubernetes.io/*`) instead of the legacy `app`/`release` labels. A Deployment's `spec.selector.matchLabels` is immutable, so `helm upgrade` against a release created before this change fails with a `field is immutable` error.
-
-To upgrade an existing release, delete the affected workloads first (their selector labels changed), then upgrade so they are recreated:
-
-```console
-kubectl delete deployment,statefulset -l release=<release-name> -n <namespace>
-helm upgrade <release-name> superset/superset
-```
-
-Alternatively, perform a fresh install. This is a one-time migration; subsequent upgrades are unaffected.
-
 {{ template "chart.requirementsSection" . }}
 
 {{ template "chart.valuesSection" . }}

helm/superset/templates/_helpers.tpl

@@ -61,49 +61,6 @@ Create chart name and version as used by the chart label.
   {{- printf "%s-%s" .Chart.Name .Chart.Version | replace "+" "_" | trunc 63 | trimSuffix "-" -}}
 {{- end -}}
 
-{{/*
-Common labels for all resources - follows Kubernetes recommended labels
-https://kubernetes.io/docs/concepts/overview/working-with-objects/common-labels/
-*/}}
-{{- define "superset.labels" -}}
-helm.sh/chart: {{ include "superset.chart" . }}
-{{ include "superset.selectorLabels" . }}
-{{- if .Chart.AppVersion }}
-app.kubernetes.io/version: {{ .Chart.AppVersion | quote }}
-{{- end }}
-app.kubernetes.io/managed-by: {{ .Release.Service }}
-app.kubernetes.io/part-of: superset
-{{- if .Values.extraLabels }}
-{{ toYaml .Values.extraLabels }}
-{{- end }}
-{{- end -}}
-
-{{/*
-Selector labels - used by selectors and matchLabels
-*/}}
-{{- define "superset.selectorLabels" -}}
-app.kubernetes.io/name: {{ include "superset.name" . }}
-app.kubernetes.io/instance: {{ .Release.Name }}
-{{- end -}}
-
-{{/*
-Component labels - extends superset.labels with component-specific labels
-Usage: {{ include "superset.componentLabels" (dict "component" "web" "root" .) }}
-*/}}
-{{- define "superset.componentLabels" -}}
-{{ include "superset.labels" .root }}
-app.kubernetes.io/component: {{ .component }}
-{{- end -}}
-
-{{/*
-Component selector labels - for matchLabels with component
-Usage: {{ include "superset.componentSelectorLabels" (dict "component" "web" "root" .) }}
-*/}}
-{{- define "superset.componentSelectorLabels" -}}
-{{ include "superset.selectorLabels" .root }}
-app.kubernetes.io/component: {{ .component }}
-{{- end -}}
-
 
 {{- define "superset-config" }}
 import os
@@ -114,9 +71,9 @@ def env(key, default=None):
 
 # Redis Base URL
 {{- if .Values.supersetNode.connections.redis_password }}
-REDIS_BASE_URL=f"{env('REDIS_DRIVER') or env('REDIS_PROTO')}://{env('REDIS_USER', '')}:{env('REDIS_PASSWORD')}@{env('REDIS_HOST')}:{env('REDIS_PORT')}"
+REDIS_BASE_URL=f"{env('REDIS_PROTO')}://{env('REDIS_USER', '')}:{env('REDIS_PASSWORD')}@{env('REDIS_HOST')}:{env('REDIS_PORT')}"
 {{- else }}
-REDIS_BASE_URL=f"{env('REDIS_DRIVER') or env('REDIS_PROTO')}://{env('REDIS_HOST')}:{env('REDIS_PORT')}"
+REDIS_BASE_URL=f"{env('REDIS_PROTO')}://{env('REDIS_HOST')}:{env('REDIS_PORT')}"
 {{- end }}
 
 # Redis URL Params
@@ -151,6 +108,8 @@ else:
     {{ fail (printf "Unsupported database type: %s. Please use 'postgresql' or 'mysql'." .Values.supersetNode.connections.db_type) }}
     {{- end }}
 
+SQLALCHEMY_TRACK_MODIFICATIONS = True
+
 class CeleryConfig:
   imports  = ("superset.sql_lab", )
   broker_url = CELERY_REDIS_URL
@@ -189,32 +148,27 @@ RESULTS_BACKEND = RedisCache(
 
 {{- end }}
 
-{{- define "supersetNode.selectorLabels" -}}
-app.kubernetes.io/name: {{ include "superset.name" . }}
-app.kubernetes.io/instance: {{ .Release.Name }}
-app.kubernetes.io/component: web
-{{- end }}
-
 {{- define "supersetCeleryBeat.selectorLabels" -}}
-app.kubernetes.io/name: {{ include "superset.name" . }}
-app.kubernetes.io/instance: {{ .Release.Name }}
-app.kubernetes.io/component: celerybeat
+app: {{ include "superset.name" . }}-celerybeat
+release: {{ .Release.Name }}
 {{- end }}
 
 {{- define "supersetCeleryFlower.selectorLabels" -}}
-app.kubernetes.io/name: {{ include "superset.name" . }}
-app.kubernetes.io/instance: {{ .Release.Name }}
-app.kubernetes.io/component: flower
+app: {{ include "superset.name" . }}-flower
+release: {{ .Release.Name }}
+{{- end }}
+
+{{- define "supersetNode.selectorLabels" -}}
+app: {{ include "superset.name" . }}
+release: {{ .Release.Name }}
 {{- end }}
 
 {{- define "supersetWebsockets.selectorLabels" -}}
-app.kubernetes.io/name: {{ include "superset.name" . }}
-app.kubernetes.io/instance: {{ .Release.Name }}
-app.kubernetes.io/component: websocket
+app: {{ include "superset.name" . }}-ws
+release: {{ .Release.Name }}
 {{- end }}
 
 {{- define "supersetWorker.selectorLabels" -}}
-app.kubernetes.io/name: {{ include "superset.name" . }}
-app.kubernetes.io/instance: {{ .Release.Name }}
-app.kubernetes.io/component: worker
+app: {{ include "superset.name" . }}-worker
+release: {{ .Release.Name }}
 {{- end }}

helm/superset/templates/configmap-superset.yaml

@@ -24,7 +24,13 @@ metadata:
   name: {{ template "superset.fullname" . }}-extra-config
   namespace: {{ .Release.Namespace }}
   labels:
-    {{- include "superset.labels" . | nindent 4 }}
+    app: {{ template "superset.name" . }}
+    chart: {{ template "superset.chart" . }}
+    release: {{ .Release.Name }}
+    heritage: {{ .Release.Service }}
+    {{- if .Values.extraLabels }}
+      {{- toYaml .Values.extraLabels | nindent 4 }}
+    {{- end }}
 data:
   {{- range $path, $config := .Values.extraConfigs }}
   {{ $path }}: |

helm/superset/templates/deployment-beat.yaml

@@ -24,7 +24,13 @@ metadata:
   name: {{ template "superset.fullname" . }}-celerybeat
   namespace: {{ .Release.Namespace }}
   labels:
-    {{- include "superset.componentLabels" (dict "component" "celerybeat" "root" .) | nindent 4 }}
+    app: {{ template "superset.name" . }}-celerybeat
+    chart: {{ template "superset.chart" . }}
+    release: {{ .Release.Name }}
+    heritage: {{ .Release.Service }}
+    {{- if .Values.extraLabels }}
+      {{- toYaml .Values.extraLabels | nindent 4 }}
+    {{- end }}
   {{- if .Values.supersetCeleryBeat.deploymentAnnotations }}
   annotations: {{- toYaml .Values.supersetCeleryBeat.deploymentAnnotations | nindent 4 }}
   {{- end }}
@@ -53,14 +59,15 @@ spec:
           {{- toYaml .Values.supersetCeleryBeat.podAnnotations | nindent 8 }}
         {{- end }}
       labels:
-        {{- include "supersetCeleryBeat.selectorLabels" . | nindent 8 }}
+        app: "{{ template "superset.name" . }}-celerybeat"
+        release: {{ .Release.Name }}
+        {{- if .Values.extraLabels }}
+          {{- toYaml .Values.extraLabels | nindent 8 }}
+        {{- end }}
         {{- if .Values.supersetCeleryBeat.podLabels }}
           {{- toYaml .Values.supersetCeleryBeat.podLabels | nindent 8 }}
         {{- end }}
     spec:
-      {{- if .Values.supersetCeleryBeat.deploymentAdditionalPodSpec }}
-      {{- tpl (toYaml .Values.supersetCeleryBeat.deploymentAdditionalPodSpec) . | nindent 6 }}
-      {{- end }}
       {{- if or (.Values.serviceAccount.create) (.Values.serviceAccountName) }}
       serviceAccountName: {{ template "superset.serviceAccountName" . }}
       {{- end }}

helm/superset/templates/deployment-flower.yaml

@@ -24,7 +24,13 @@ metadata:
   name: {{ template "superset.fullname" . }}-flower
   namespace: {{ .Release.Namespace }}
   labels:
-    {{- include "superset.componentLabels" (dict "component" "flower" "root" .) | nindent 4 }}
+    app: {{ template "superset.name" . }}-flower
+    chart: {{ template "superset.chart" . }}
+    release: {{ .Release.Name }}
+    heritage: {{ .Release.Service }}
+    {{- if .Values.extraLabels }}
+      {{- toYaml .Values.extraLabels | nindent 4 }}
+    {{- end }}
   {{- if .Values.supersetCeleryFlower.deploymentAnnotations }}
   annotations: {{- toYaml .Values.supersetCeleryFlower.deploymentAnnotations | nindent 4 }}
   {{- end }}
@@ -42,14 +48,15 @@ spec:
           {{- toYaml .Values.supersetCeleryFlower.podAnnotations | nindent 8 }}
         {{- end }}
       labels:
-        {{- include "supersetCeleryFlower.selectorLabels" . | nindent 8 }}
+        app: "{{ template "superset.name" . }}-flower"
+        release: {{ .Release.Name }}
+        {{- if .Values.extraLabels }}
+          {{- toYaml .Values.extraLabels | nindent 8 }}
+        {{- end }}
         {{- if .Values.supersetCeleryFlower.podLabels }}
           {{- toYaml .Values.supersetCeleryFlower.podLabels | nindent 8 }}
         {{- end }}
     spec:
-      {{- if .Values.supersetCeleryFlower.deploymentAdditionalPodSpec }}
-      {{- tpl (toYaml .Values.supersetCeleryFlower.deploymentAdditionalPodSpec) . | nindent 6 }}
-      {{- end }}
       {{- if or (.Values.serviceAccount.create) (.Values.serviceAccountName) }}
       serviceAccountName: {{ template "superset.serviceAccountName" . }}
       {{- end }}

helm/superset/templates/deployment-worker.yaml

@@ -23,9 +23,15 @@ metadata:
   name: {{ template "superset.fullname" . }}-worker
   namespace: {{ .Release.Namespace }}
   labels:
-    {{- include "superset.componentLabels" (dict "component" "worker" "root" .) | nindent 4 }}
-    {{- with .Values.supersetWorker.deploymentLabels }}
-      {{- toYaml . | nindent 4 }}
+    app: {{ template "superset.name" . }}-worker
+    chart: {{ template "superset.chart" . }}
+    release: {{ .Release.Name }}
+    heritage: {{ .Release.Service }}
+    {{- if .Values.extraLabels }}
+      {{- toYaml .Values.extraLabels | nindent 4 }}
+    {{- end }}
+    {{- if .Values.supersetWorker.deploymentLabels }}
+      {{- toYaml .Values.supersetWorker.deploymentLabels | nindent 4 }}
     {{- end }}
   {{- if .Values.supersetWorker.deploymentAnnotations }}
   annotations: {{- toYaml .Values.supersetWorker.deploymentAnnotations | nindent 4 }}
@@ -59,14 +65,15 @@ spec:
           {{- toYaml .Values.supersetWorker.podAnnotations | nindent 8 }}
         {{- end }}
       labels:
-        {{- include "supersetWorker.selectorLabels" . | nindent 8 }}
+        app: {{ template "superset.name" . }}-worker
+        release: {{ .Release.Name }}
+        {{- if .Values.extraLabels }}
+          {{- toYaml .Values.extraLabels | nindent 8 }}
+        {{- end }}
         {{- if .Values.supersetWorker.podLabels }}
           {{- toYaml .Values.supersetWorker.podLabels | nindent 8 }}
         {{- end }}
     spec:
-      {{- if .Values.supersetWorker.deploymentAdditionalPodSpec }}
-      {{- tpl (toYaml .Values.supersetWorker.deploymentAdditionalPodSpec) . | nindent 6 }}
-      {{- end }}
       {{- if or (.Values.serviceAccount.create) (.Values.serviceAccountName) }}
       serviceAccountName: {{ template "superset.serviceAccountName" . }}
       {{- end }}

helm/superset/templates/deployment-ws.yaml

@@ -24,7 +24,13 @@ metadata:
   name: "{{ template "superset.fullname" . }}-ws"
   namespace: {{ .Release.Namespace }}
   labels:
-    {{- include "superset.componentLabels" (dict "component" "websocket" "root" .) | nindent 4 }}
+    app: "{{ template "superset.name" . }}-ws"
+    chart: {{ template "superset.chart" . }}
+    release: {{ .Release.Name }}
+    heritage: {{ .Release.Service }}
+    {{- if .Values.extraLabels }}
+      {{- toYaml .Values.extraLabels | nindent 4 }}
+    {{- end }}
   {{- if .Values.supersetWebsockets.deploymentAnnotations }}
   annotations: {{- toYaml .Values.supersetWebsockets.deploymentAnnotations | nindent 4 }}
   {{- end }}
@@ -45,14 +51,15 @@ spec:
           {{- toYaml .Values.supersetWebsockets.podAnnotations | nindent 8 }}
         {{- end }}
       labels:
-        {{- include "supersetWebsockets.selectorLabels" . | nindent 8 }}
+        app: "{{ template "superset.name" . }}-ws"
+        release: {{ .Release.Name }}
+        {{- if .Values.extraLabels }}
+          {{- toYaml .Values.extraLabels | nindent 8 }}
+        {{- end }}
         {{- if .Values.supersetWebsockets.podLabels }}
           {{- toYaml .Values.supersetWebsockets.podLabels | nindent 8 }}
         {{- end }}
     spec:
-      {{- if .Values.supersetWebsockets.deploymentAdditionalPodSpec }}
-      {{- tpl (toYaml .Values.supersetWebsockets.deploymentAdditionalPodSpec) . | nindent 6 }}
-      {{- end }}
       {{- if or (.Values.serviceAccount.create) (.Values.serviceAccountName) }}
       serviceAccountName: {{ template "superset.serviceAccountName" . }}
       {{- end }}

helm/superset/templates/deployment.yaml

@@ -23,9 +23,15 @@ metadata:
   name: {{ template "superset.fullname" . }}
   namespace: {{ .Release.Namespace }}
   labels:
-    {{- include "superset.componentLabels" (dict "component" "web" "root" .) | nindent 4 }}
-    {{- with .Values.supersetNode.deploymentLabels }}
-      {{- toYaml . | nindent 4 }}
+    app: {{ template "superset.name" . }}
+    chart: {{ template "superset.chart" . }}
+    release: {{ .Release.Name }}
+    heritage: {{ .Release.Service }}
+    {{- if .Values.extraLabels }}
+      {{- toYaml .Values.extraLabels | nindent 4 }}
+    {{- end }}
+    {{- if .Values.supersetNode.deploymentLabels }}
+      {{- toYaml .Values.supersetNode.deploymentLabels | nindent 4 }}
     {{- end }}
   {{- if .Values.supersetNode.deploymentAnnotations }}
   annotations: {{- toYaml .Values.supersetNode.deploymentAnnotations | nindent 4 }}
@@ -61,14 +67,15 @@ spec:
           {{- toYaml .Values.supersetNode.podAnnotations | nindent 8 }}
         {{- end }}
       labels:
-        {{- include "supersetNode.selectorLabels" . | nindent 8 }}
+        app: {{ template "superset.name" . }}
+        release: {{ .Release.Name }}
+        {{- if .Values.extraLabels }}
+          {{- toYaml .Values.extraLabels | nindent 8 }}
+        {{- end }}
         {{- if .Values.supersetNode.podLabels }}
           {{- toYaml .Values.supersetNode.podLabels | nindent 8 }}
         {{- end }}
     spec:
-      {{- if .Values.supersetNode.deploymentAdditionalPodSpec }}
-      {{- tpl (toYaml .Values.supersetNode.deploymentAdditionalPodSpec) . | nindent 6 }}
-      {{- end }}
       {{- if or (.Values.serviceAccount.create) (.Values.serviceAccountName) }}
       serviceAccountName: {{ template "superset.serviceAccountName" . }}
       {{- end }}

helm/superset/templates/hpa-node.yaml

@@ -23,7 +23,13 @@ kind: HorizontalPodAutoscaler
 metadata:
   name: {{ include "superset.fullname" . }}-hpa
   labels:
-    {{- include "superset.labels" . | nindent 4 }}
+    app: {{ template "superset.name" . }}
+    chart: {{ template "superset.chart" . }}
+    release: {{ .Release.Name }}
+    heritage: {{ .Release.Service }}
+    {{- if .Values.extraLabels }}
+      {{- toYaml .Values.extraLabels | nindent 4 }}
+    {{- end }}
 spec:
   scaleTargetRef:
     apiVersion: apps/v1

helm/superset/templates/hpa-worker.yaml

@@ -23,7 +23,13 @@ kind: HorizontalPodAutoscaler
 metadata:
   name: {{ include "superset.fullname" . }}-hpa-worker
   labels:
-    {{- include "superset.labels" . | nindent 4 }}
+    app: {{ template "superset.name" . }}
+    chart: {{ template "superset.chart" . }}
+    release: {{ .Release.Name }}
+    heritage: {{ .Release.Service }}
+    {{- if .Values.extraLabels }}
+      {{- toYaml .Values.extraLabels | nindent 4 }}
+    {{- end }}
 spec:
   scaleTargetRef:
     apiVersion: apps/v1

helm/superset/templates/ingress.yaml

@@ -25,7 +25,13 @@ metadata:
   name: {{ $fullName }}
   namespace: {{ .Release.Namespace }}
   labels:
-    {{- include "superset.componentLabels" (dict "component" "ingress" "root" .) | nindent 4 }}
+    app: {{ template "superset.name" . }}
+    chart: {{ template "superset.chart" . }}
+    release: {{ .Release.Name }}
+    heritage: {{ .Release.Service }}
+    {{- if .Values.extraLabels }}
+      {{- toYaml .Values.extraLabels | nindent 4 }}
+    {{- end }}
   {{- with .Values.ingress.annotations }}
   annotations: {{- toYaml . | nindent 4 }}
   {{- end }}

helm/superset/templates/init-job.yaml

@@ -24,7 +24,13 @@ metadata:
   name: {{ template "superset.fullname" . }}-init-db
   namespace: {{ .Release.Namespace }}
   labels:
-    {{- include "superset.componentLabels" (dict "component" "init" "root" .) | nindent 4 }}
+    app: {{ template "superset.name" . }}
+    chart: {{ template "superset.chart" . }}
+    release: {{ .Release.Name }}
+    heritage: {{ .Release.Service }}
+    {{- if .Values.extraLabels }}
+      {{- toYaml .Values.extraLabels | nindent 4 }}
+    {{- end }}
   {{- if .Values.init.jobAnnotations }}
   annotations: {{- toYaml .Values.init.jobAnnotations | nindent 4 }}
   {{- end }}
@@ -35,19 +41,16 @@ spec:
       {{- if .Values.init.podAnnotations }}
       annotations: {{- toYaml .Values.init.podAnnotations | nindent 8 }}
       {{- end }}
+      {{- if or .Values.extraLabels .Values.init.podLabels }}
       labels:
-        {{- include "superset.componentSelectorLabels" (dict "component" "init" "root" .) | nindent 8 }}
-        job: {{ template "superset.fullname" . }}-init-db
         {{- if .Values.extraLabels }}
           {{- toYaml .Values.extraLabels | nindent 8 }}
         {{- end }}
         {{- if .Values.init.podLabels }}
           {{- toYaml .Values.init.podLabels | nindent 8 }}
         {{- end }}
-    spec:
-      {{- if .Values.init.additionalPodSpec }}
-      {{- tpl (toYaml .Values.init.additionalPodSpec) . | nindent 6 }}
       {{- end }}
+    spec:
       {{- if or (.Values.serviceAccount.create) (.Values.serviceAccountName) }}
       serviceAccountName: {{ template "superset.serviceAccountName" . }}
       {{- end }}

helm/superset/templates/pdb-beat.yaml

@@ -27,7 +27,13 @@ kind: PodDisruptionBudget
 metadata:
   name: {{ include "superset.fullname" $ }}-celerybeat-pdb
   labels:
-    {{- include "superset.componentLabels" (dict "component" "celerybeat" "root" $) | nindent 4 }}
+    app: {{ template "superset.name" $ }}-celerybeat
+    chart: {{ template "superset.chart" $ }}
+    release: {{ $.Release.Name }}
+    heritage: {{ $.Release.Service }}
+    {{- if $.Values.extraLabels }}
+      {{- toYaml $.Values.extraLabels | nindent 4 }}
+    {{- end }}
 spec:
   {{- if .minAvailable }}
   minAvailable: {{ .minAvailable }}

helm/superset/templates/pdb-flower.yaml

@@ -27,7 +27,13 @@ kind: PodDisruptionBudget
 metadata:
   name: {{ include "superset.fullname" $ }}-flower-pdb
   labels:
-    {{- include "superset.componentLabels" (dict "component" "flower" "root" $) | nindent 4 }}
+    app: {{ template "superset.name" $ }}-flower
+    chart: {{ template "superset.chart" $ }}
+    release: {{ $.Release.Name }}
+    heritage: {{ $.Release.Service }}
+    {{- if $.Values.extraLabels }}
+      {{- toYaml $.Values.extraLabels | nindent 4 }}
+    {{- end }}
 spec:
   {{- if .minAvailable }}
   minAvailable: {{ .minAvailable }}

helm/superset/templates/pdb-worker.yaml

@@ -27,7 +27,13 @@ kind: PodDisruptionBudget
 metadata:
   name: {{ include "superset.fullname" $ }}-worker-pdb
   labels:
-    {{- include "superset.componentLabels" (dict "component" "worker" "root" $) | nindent 4 }}
+    app: {{ template "superset.name" $ }}-worker
+    chart: {{ template "superset.chart" $ }}
+    release: {{ $.Release.Name }}
+    heritage: {{ $.Release.Service }}
+    {{- if $.Values.extraLabels }}
+      {{- toYaml $.Values.extraLabels | nindent 4 }}
+    {{- end }}
 spec:
   {{- if .minAvailable }}
   minAvailable: {{ .minAvailable }}

helm/superset/templates/pdb-ws.yaml

@@ -27,7 +27,13 @@ kind: PodDisruptionBudget
 metadata:
   name: {{ include "superset.fullname" $ }}-ws-pdb
   labels:
-    {{- include "superset.componentLabels" (dict "component" "websocket" "root" $) | nindent 4 }}
+    app: {{ template "superset.name" $ }}-ws
+    chart: {{ template "superset.chart" $ }}
+    release: {{ $.Release.Name }}
+    heritage: {{ $.Release.Service }}
+    {{- if $.Values.extraLabels }}
+      {{- toYaml $.Values.extraLabels | nindent 4 }}
+    {{- end }}
 spec:
   {{- if .minAvailable }}
   minAvailable: {{ .minAvailable }}

helm/superset/templates/pdb.yaml

@@ -27,7 +27,13 @@ kind: PodDisruptionBudget
 metadata:
   name: {{ include "superset.fullname" $ }}-pdb
   labels:
-    {{- include "superset.componentLabels" (dict "component" "web" "root" $) | nindent 4 }}
+    app: {{ template "superset.name" $ }}
+    chart: {{ template "superset.chart" $ }}
+    release: {{ $.Release.Name }}
+    heritage: {{ $.Release.Service }}
+    {{- if $.Values.extraLabels }}
+      {{- toYaml $.Values.extraLabels | nindent 4 }}
+    {{- end }}
 spec:
   {{- if .minAvailable }}
   minAvailable: {{ .minAvailable }}

helm/superset/templates/secret-env.yaml

@@ -23,7 +23,13 @@ metadata:
   name: {{ template "superset.fullname" . }}-env
   namespace: {{ .Release.Namespace }}
   labels:
-    {{- include "superset.labels" . | nindent 4 }}
+    app: {{ template "superset.fullname" . }}
+    chart: {{ template "superset.chart" . }}
+    release: "{{ .Release.Name }}"
+    heritage: "{{ .Release.Service }}"
+    {{- if .Values.extraLabels }}
+      {{- toYaml .Values.extraLabels | nindent 4 }}
+    {{- end }}
 type: Opaque
 stringData:
     REDIS_HOST: {{ tpl .Values.supersetNode.connections.redis_host . | quote }}
@@ -33,7 +39,6 @@ stringData:
     {{- end }}
     REDIS_PORT: {{ .Values.supersetNode.connections.redis_port | quote }}
     REDIS_PROTO: {{ if .Values.supersetNode.connections.redis_ssl.enabled }}"rediss"{{ else }}"redis"{{ end }}
-    REDIS_DRIVER: {{ .Values.supersetNode.connections.redis_driver | quote }}
     REDIS_DB: {{ .Values.supersetNode.connections.redis_cache_db | quote }}
     REDIS_CELERY_DB: {{ .Values.supersetNode.connections.redis_celery_db | quote }}
     {{- if .Values.supersetNode.connections.redis_ssl.enabled }}

helm/superset/templates/secret-superset-config.yaml

@@ -23,7 +23,13 @@ metadata:
   name: {{ template "superset.fullname" . }}-config
   namespace: {{ .Release.Namespace }}
   labels:
-    {{- include "superset.labels" . | nindent 4 }}
+    app: {{ template "superset.fullname" . }}
+    chart: {{ template "superset.chart" . }}
+    release: "{{ .Release.Name }}"
+    heritage: "{{ .Release.Service }}"
+    {{- if .Values.extraLabels }}
+      {{- toYaml .Values.extraLabels | nindent 4 }}
+    {{- end }}
 type: Opaque
 stringData:
   superset_config.py: |

helm/superset/templates/secret-ws.yaml

@@ -24,7 +24,13 @@ metadata:
   name: "{{ template "superset.fullname" . }}-ws-config"
   namespace: {{ .Release.Namespace }}
   labels:
-    {{- include "superset.labels" . | nindent 4 }}
+    app: {{ template "superset.fullname" . }}
+    chart: {{ template "superset.chart" . }}
+    release: "{{ .Release.Name }}"
+    heritage: "{{ .Release.Service }}"
+    {{- if .Values.extraLabels }}
+      {{- toYaml .Values.extraLabels | nindent 4 }}
+    {{- end }}
 type: Opaque
 stringData:
   config.json: |

helm/superset/templates/service-flower.yaml

@@ -24,7 +24,13 @@ metadata:
   name: "{{ template "superset.fullname" . }}-flower"
   namespace: {{ .Release.Namespace }}
   labels:
-    {{- include "superset.componentLabels" (dict "component" "flower" "root" .) | nindent 4 }}
+    app: {{ template "superset.name" . }}
+    chart: {{ template "superset.chart" . }}
+    release: {{ .Release.Name }}
+    heritage: {{ .Release.Service }}
+    {{- if .Values.extraLabels }}
+      {{- toYaml .Values.extraLabels | nindent 4 }}
+    {{- end }}
   {{- with .Values.supersetCeleryFlower.service.annotations }}
   annotations: {{- toYaml . | nindent 4 }}
   {{- end }}
@@ -39,7 +45,8 @@ spec:
       nodePort: {{ .Values.supersetCeleryFlower.service.nodePort.http }}
       {{- end }}
   selector:
-    {{- include "supersetCeleryFlower.selectorLabels" . | nindent 4 }}
+    app: {{ template "superset.name" . }}-flower
+    release: {{ .Release.Name }}
   {{- if .Values.supersetCeleryFlower.service.loadBalancerIP }}
   loadBalancerIP: {{ .Values.supersetCeleryFlower.service.loadBalancerIP }}
   {{- end }}

helm/superset/templates/service-ws.yaml

@@ -24,7 +24,13 @@ metadata:
   name: "{{ template "superset.fullname" . }}-ws"
   namespace: {{ .Release.Namespace }}
   labels:
-    {{- include "superset.componentLabels" (dict "component" "websocket" "root" .) | nindent 4 }}
+    app: {{ template "superset.name" . }}
+    chart: {{ template "superset.chart" . }}
+    release: {{ .Release.Name }}
+    heritage: {{ .Release.Service }}
+    {{- if .Values.extraLabels }}
+      {{- toYaml .Values.extraLabels | nindent 4 }}
+    {{- end }}
   {{- with .Values.supersetWebsockets.service.annotations }}
   annotations: {{- toYaml . | nindent 4 }}
   {{- end }}
@@ -39,7 +45,8 @@ spec:
       nodePort: {{ .Values.supersetWebsockets.service.nodePort.http }}
       {{- end }}
   selector:
-    {{- include "supersetWebsockets.selectorLabels" . | nindent 4 }}
+    app: "{{ template "superset.name" . }}-ws"
+    release: {{ .Release.Name }}
   {{- if .Values.supersetWebsockets.service.loadBalancerIP }}
   loadBalancerIP: {{ .Values.supersetWebsockets.service.loadBalancerIP }}
   {{- end }}

helm/superset/templates/service.yaml

@@ -23,7 +23,13 @@ metadata:
   name: {{ template "superset.fullname" . }}
   namespace: {{ .Release.Namespace }}
   labels:
-    {{- include "superset.componentLabels" (dict "component" "web" "root" .) | nindent 4 }}
+    app: {{ template "superset.name" . }}
+    chart: {{ template "superset.chart" . }}
+    release: {{ .Release.Name }}
+    heritage: {{ .Release.Service }}
+    {{- if .Values.extraLabels }}
+      {{- toYaml .Values.extraLabels | nindent 4 }}
+    {{- end }}
   {{- with .Values.service.annotations }}
   annotations: {{- toYaml . | nindent 4 }}
   {{- end }}
@@ -38,7 +44,8 @@ spec:
       nodePort: {{ .Values.service.nodePort.http }}
       {{- end }}
   selector:
-    {{- include "supersetNode.selectorLabels" . | nindent 4 }}
+    app: {{ template "superset.name" . }}
+    release: {{ .Release.Name }}
   {{- if .Values.service.loadBalancerIP }}
   loadBalancerIP: {{ .Values.service.loadBalancerIP }}
   {{- end }}

helm/superset/templates/serviceaccount.yaml

@@ -24,11 +24,17 @@ metadata:
   name: {{ include "superset.serviceAccountName" . }}
   namespace: {{ .Release.Namespace }}
   labels:
-    {{- include "superset.labels" . | nindent 4 }}
+    app.kubernetes.io/name: {{ include "superset.name" . }}
+    helm.sh/chart: {{ include "superset.chart" . }}
+    app.kubernetes.io/instance: {{ .Release.Name }}
+    app.kubernetes.io/managed-by: {{ .Release.Service }}
     {{- if semverCompare "> 1.6" .Capabilities.KubeVersion.GitVersion }}
     kubernetes.io/cluster-service: "true"
     {{- end }}
     addonmanager.kubernetes.io/mode: Reconcile
+    {{- if .Values.extraLabels }}
+      {{- toYaml .Values.extraLabels | nindent 4 }}
+    {{- end }}
   {{- if .Values.serviceAccount.annotations }}
   annotations: {{- toYaml .Values.serviceAccount.annotations | nindent 4 }}
   {{- end }}

helm/superset/tests/labels_test.yaml

@@ -1,520 +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.
-#
-suite: Label Consistency Tests
-templates:
-  - deployment.yaml
-  - deployment-worker.yaml
-  - deployment-beat.yaml
-  - deployment-flower.yaml
-  - deployment-ws.yaml
-  - service.yaml
-  - service-ws.yaml
-  - service-flower.yaml
-  - init-job.yaml
-  - ingress.yaml
-  - configmap-superset.yaml
-  - secret-superset-config.yaml
-  - secret-ws.yaml
-  - pdb.yaml
-  - pdb-worker.yaml
-  - pdb-beat.yaml
-  - pdb-flower.yaml
-  - pdb-ws.yaml
-
-# These tests validate that Kubernetes recommended labels are consistently applied
-# across all chart resources per https://kubernetes.io/docs/concepts/overview/working-with-objects/common-labels/
-#
-# Required Labels (app.kubernetes.io/):
-#   - name: The name of the application
-#   - instance: A unique name identifying the instance of an application
-#   - version: The current version of the application
-#   - component: The component within the architecture
-#   - part-of: The name of a higher level application this one is part of
-#   - managed-by: The tool being used to manage the operation of an application
-#
-# Helm-specific Labels:
-#   - helm.sh/chart: The chart name and version
-
-tests:
-  # =============================================================================
-  # Main Deployment Labels
-  # =============================================================================
-  - it: should have all recommended labels on main deployment
-    template: deployment.yaml
-    asserts:
-      - isNotNull:
-          path: metadata.labels["app.kubernetes.io/name"]
-      - isNotNull:
-          path: metadata.labels["app.kubernetes.io/instance"]
-      - isNotNull:
-          path: metadata.labels["app.kubernetes.io/version"]
-      - isNotNull:
-          path: metadata.labels["app.kubernetes.io/managed-by"]
-      - isNotNull:
-          path: metadata.labels["app.kubernetes.io/part-of"]
-      - isNotNull:
-          path: metadata.labels["app.kubernetes.io/component"]
-      - isNotNull:
-          path: metadata.labels["helm.sh/chart"]
-
-  - it: should have correct component label on main deployment
-    template: deployment.yaml
-    asserts:
-      - equal:
-          path: metadata.labels["app.kubernetes.io/component"]
-          value: web
-
-  - it: should have part-of label set to superset on main deployment
-    template: deployment.yaml
-    asserts:
-      - equal:
-          path: metadata.labels["app.kubernetes.io/part-of"]
-          value: superset
-
-  # =============================================================================
-  # Worker Deployment Labels
-  # =============================================================================
-  - it: should have all recommended labels on worker deployment
-    template: deployment-worker.yaml
-    asserts:
-      - isNotNull:
-          path: metadata.labels["app.kubernetes.io/name"]
-      - isNotNull:
-          path: metadata.labels["app.kubernetes.io/instance"]
-      - isNotNull:
-          path: metadata.labels["app.kubernetes.io/version"]
-      - isNotNull:
-          path: metadata.labels["app.kubernetes.io/managed-by"]
-      - isNotNull:
-          path: metadata.labels["app.kubernetes.io/part-of"]
-      - isNotNull:
-          path: metadata.labels["app.kubernetes.io/component"]
-
-  - it: should have correct component label on worker deployment
-    template: deployment-worker.yaml
-    asserts:
-      - equal:
-          path: metadata.labels["app.kubernetes.io/component"]
-          value: worker
-
-  # =============================================================================
-  # Celery Beat Deployment Labels
-  # =============================================================================
-  - it: should have all recommended labels on celerybeat deployment
-    template: deployment-beat.yaml
-    set:
-      supersetCeleryBeat.enabled: true
-    asserts:
-      - isNotNull:
-          path: metadata.labels["app.kubernetes.io/name"]
-      - isNotNull:
-          path: metadata.labels["app.kubernetes.io/instance"]
-      - isNotNull:
-          path: metadata.labels["app.kubernetes.io/component"]
-
-  - it: should have correct component label on celerybeat deployment
-    template: deployment-beat.yaml
-    set:
-      supersetCeleryBeat.enabled: true
-    asserts:
-      - equal:
-          path: metadata.labels["app.kubernetes.io/component"]
-          value: celerybeat
-
-  # =============================================================================
-  # Flower Deployment Labels
-  # =============================================================================
-  - it: should have all recommended labels on flower deployment
-    template: deployment-flower.yaml
-    set:
-      supersetCeleryFlower.enabled: true
-    asserts:
-      - isNotNull:
-          path: metadata.labels["app.kubernetes.io/name"]
-      - isNotNull:
-          path: metadata.labels["app.kubernetes.io/instance"]
-      - isNotNull:
-          path: metadata.labels["app.kubernetes.io/component"]
-
-  - it: should have correct component label on flower deployment
-    template: deployment-flower.yaml
-    set:
-      supersetCeleryFlower.enabled: true
-    asserts:
-      - equal:
-          path: metadata.labels["app.kubernetes.io/component"]
-          value: flower
-
-  # =============================================================================
-  # WebSocket Deployment Labels
-  # =============================================================================
-  - it: should have all recommended labels on websocket deployment
-    template: deployment-ws.yaml
-    set:
-      supersetWebsockets.enabled: true
-      supersetWebsockets.config.jwtSecret: "test-secret-for-unit-test"
-    asserts:
-      - isNotNull:
-          path: metadata.labels["app.kubernetes.io/name"]
-      - isNotNull:
-          path: metadata.labels["app.kubernetes.io/instance"]
-      - isNotNull:
-          path: metadata.labels["app.kubernetes.io/component"]
-
-  - it: should have correct component label on websocket deployment
-    template: deployment-ws.yaml
-    set:
-      supersetWebsockets.enabled: true
-      supersetWebsockets.config.jwtSecret: "test-secret-for-unit-test"
-    asserts:
-      - equal:
-          path: metadata.labels["app.kubernetes.io/component"]
-          value: websocket
-
-  # =============================================================================
-  # Service Labels
-  # =============================================================================
-  - it: should have all recommended labels on main service
-    template: service.yaml
-    asserts:
-      - isNotNull:
-          path: metadata.labels["app.kubernetes.io/name"]
-      - isNotNull:
-          path: metadata.labels["app.kubernetes.io/instance"]
-      - isNotNull:
-          path: metadata.labels["app.kubernetes.io/component"]
-
-  - it: should have correct component label on main service
-    template: service.yaml
-    asserts:
-      - equal:
-          path: metadata.labels["app.kubernetes.io/component"]
-          value: web
-
-  - it: should have all recommended labels on websocket service
-    template: service-ws.yaml
-    set:
-      supersetWebsockets.enabled: true
-      supersetWebsockets.config.jwtSecret: "test-secret-for-unit-test"
-    asserts:
-      - isNotNull:
-          path: metadata.labels["app.kubernetes.io/name"]
-      - isNotNull:
-          path: metadata.labels["app.kubernetes.io/instance"]
-      - isNotNull:
-          path: metadata.labels["app.kubernetes.io/component"]
-
-  - it: should have correct component label on websocket service
-    template: service-ws.yaml
-    set:
-      supersetWebsockets.enabled: true
-      supersetWebsockets.config.jwtSecret: "test-secret-for-unit-test"
-    asserts:
-      - equal:
-          path: metadata.labels["app.kubernetes.io/component"]
-          value: websocket
-
-  - it: should have all recommended labels on flower service
-    template: service-flower.yaml
-    set:
-      supersetCeleryFlower.enabled: true
-    asserts:
-      - isNotNull:
-          path: metadata.labels["app.kubernetes.io/name"]
-      - isNotNull:
-          path: metadata.labels["app.kubernetes.io/instance"]
-      - isNotNull:
-          path: metadata.labels["app.kubernetes.io/component"]
-
-  - it: should have correct component label on flower service
-    template: service-flower.yaml
-    set:
-      supersetCeleryFlower.enabled: true
-    asserts:
-      - equal:
-          path: metadata.labels["app.kubernetes.io/component"]
-          value: flower
-
-  # =============================================================================
-  # Init Job Labels
-  # =============================================================================
-  - it: should have all recommended labels on init job
-    template: init-job.yaml
-    set:
-      init.enabled: true
-      init.createAdmin: true
-      init.adminUser.password: "test-password"
-    asserts:
-      - isNotNull:
-          path: metadata.labels["app.kubernetes.io/name"]
-      - isNotNull:
-          path: metadata.labels["app.kubernetes.io/instance"]
-      - isNotNull:
-          path: metadata.labels["app.kubernetes.io/component"]
-
-  - it: should have correct component label on init job
-    template: init-job.yaml
-    set:
-      init.enabled: true
-      init.createAdmin: true
-      init.adminUser.password: "test-password"
-    asserts:
-      - equal:
-          path: metadata.labels["app.kubernetes.io/component"]
-          value: init
-
-  # =============================================================================
-  # Ingress Labels
-  # =============================================================================
-  - it: should have all recommended labels on ingress
-    template: ingress.yaml
-    set:
-      ingress.enabled: true
-      ingress.hosts:
-        - host: superset.example.com
-          paths:
-            - path: /
-              pathType: Prefix
-    asserts:
-      - isNotNull:
-          path: metadata.labels["app.kubernetes.io/name"]
-      - isNotNull:
-          path: metadata.labels["app.kubernetes.io/instance"]
-      - isNotNull:
-          path: metadata.labels["app.kubernetes.io/component"]
-
-  - it: should have correct component label on ingress
-    template: ingress.yaml
-    set:
-      ingress.enabled: true
-      ingress.hosts:
-        - host: superset.example.com
-          paths:
-            - path: /
-              pathType: Prefix
-    asserts:
-      - equal:
-          path: metadata.labels["app.kubernetes.io/component"]
-          value: ingress
-
-  # =============================================================================
-  # Selector Label Consistency
-  #
-  # These use value assertions (not isNotNull) on purpose: a missing/misscoped
-  # release name renders as the string "<no value>", which is non-null and would
-  # silently pass isNotNull. Asserting the concrete value catches that class of
-  # bug, and asserting the pod template labels equal the selector guards the
-  # immutable spec.selector.matchLabels <-> pod label invariant.
-  # =============================================================================
-  - it: should set selector matchLabels to concrete values on main deployment
-    template: deployment.yaml
-    asserts:
-      - equal:
-          path: spec.selector.matchLabels["app.kubernetes.io/name"]
-          value: superset
-      - equal:
-          path: spec.selector.matchLabels["app.kubernetes.io/instance"]
-          value: RELEASE-NAME
-      - equal:
-          path: spec.selector.matchLabels["app.kubernetes.io/component"]
-          value: web
-
-  - it: should match pod template labels to the selector on main deployment
-    template: deployment.yaml
-    asserts:
-      - equal:
-          path: spec.template.metadata.labels["app.kubernetes.io/name"]
-          value: superset
-      - equal:
-          path: spec.template.metadata.labels["app.kubernetes.io/instance"]
-          value: RELEASE-NAME
-      - equal:
-          path: spec.template.metadata.labels["app.kubernetes.io/component"]
-          value: web
-
-  - it: should set selector matchLabels to concrete values on worker deployment
-    template: deployment-worker.yaml
-    asserts:
-      - equal:
-          path: spec.selector.matchLabels["app.kubernetes.io/instance"]
-          value: RELEASE-NAME
-      - equal:
-          path: spec.selector.matchLabels["app.kubernetes.io/component"]
-          value: worker
-
-  - it: should match pod template labels to the selector on worker deployment
-    template: deployment-worker.yaml
-    asserts:
-      - equal:
-          path: spec.template.metadata.labels["app.kubernetes.io/instance"]
-          value: RELEASE-NAME
-      - equal:
-          path: spec.template.metadata.labels["app.kubernetes.io/component"]
-          value: worker
-
-  # =============================================================================
-  # Extra Labels Support
-  # =============================================================================
-  - it: should include extraLabels when specified
-    template: deployment.yaml
-    set:
-      extraLabels:
-        custom-label: custom-value
-        environment: production
-    asserts:
-      - equal:
-          path: metadata.labels.custom-label
-          value: custom-value
-      - equal:
-          path: metadata.labels.environment
-          value: production
-
-  - it: should include extraLabels in service
-    template: service.yaml
-    set:
-      extraLabels:
-        custom-label: custom-value
-    asserts:
-      - equal:
-          path: metadata.labels.custom-label
-          value: custom-value
-
-  # =============================================================================
-  # ConfigMap / Secret Labels
-  # =============================================================================
-  - it: should have recommended labels on extra-config configmap
-    template: configmap-superset.yaml
-    set:
-      extraConfigs:
-        custom.py: "FOO = 1"
-    asserts:
-      - isNotNull:
-          path: metadata.labels["app.kubernetes.io/name"]
-      - equal:
-          path: metadata.labels["app.kubernetes.io/instance"]
-          value: RELEASE-NAME
-      - isNotNull:
-          path: metadata.labels["app.kubernetes.io/managed-by"]
-      - equal:
-          path: metadata.labels["app.kubernetes.io/part-of"]
-          value: superset
-
-  - it: should have recommended labels on superset config secret
-    template: secret-superset-config.yaml
-    asserts:
-      - isNotNull:
-          path: metadata.labels["app.kubernetes.io/name"]
-      - equal:
-          path: metadata.labels["app.kubernetes.io/instance"]
-          value: RELEASE-NAME
-      - equal:
-          path: metadata.labels["app.kubernetes.io/part-of"]
-          value: superset
-
-  - it: should have recommended labels on websocket config secret
-    template: secret-ws.yaml
-    set:
-      supersetWebsockets.enabled: true
-    asserts:
-      - isNotNull:
-          path: metadata.labels["app.kubernetes.io/name"]
-      - equal:
-          path: metadata.labels["app.kubernetes.io/instance"]
-          value: RELEASE-NAME
-
-  # =============================================================================
-  # PodDisruptionBudget Labels (metadata must match the selector)
-  # =============================================================================
-  - it: should have recommended labels and matching selector on main pdb
-    template: pdb.yaml
-    set:
-      supersetNode.podDisruptionBudget.enabled: true
-      supersetNode.podDisruptionBudget.maxUnavailable: null
-    asserts:
-      - equal:
-          path: metadata.labels["app.kubernetes.io/instance"]
-          value: RELEASE-NAME
-      - equal:
-          path: metadata.labels["app.kubernetes.io/component"]
-          value: web
-      - equal:
-          path: spec.selector.matchLabels["app.kubernetes.io/instance"]
-          value: RELEASE-NAME
-      - equal:
-          path: spec.selector.matchLabels["app.kubernetes.io/component"]
-          value: web
-
-  - it: should set correct component on worker pdb
-    template: pdb-worker.yaml
-    set:
-      supersetWorker.podDisruptionBudget.enabled: true
-      supersetWorker.podDisruptionBudget.maxUnavailable: null
-    asserts:
-      - equal:
-          path: metadata.labels["app.kubernetes.io/component"]
-          value: worker
-      - equal:
-          path: spec.selector.matchLabels["app.kubernetes.io/component"]
-          value: worker
-
-  - it: should set correct component on celerybeat pdb
-    template: pdb-beat.yaml
-    set:
-      supersetCeleryBeat.podDisruptionBudget.enabled: true
-      supersetCeleryBeat.podDisruptionBudget.maxUnavailable: null
-    asserts:
-      - equal:
-          path: metadata.labels["app.kubernetes.io/component"]
-          value: celerybeat
-
-  - it: should set correct component on flower pdb
-    template: pdb-flower.yaml
-    set:
-      supersetCeleryFlower.podDisruptionBudget.enabled: true
-      supersetCeleryFlower.podDisruptionBudget.maxUnavailable: null
-    asserts:
-      - equal:
-          path: metadata.labels["app.kubernetes.io/component"]
-          value: flower
-
-  - it: should set correct component on websocket pdb
-    template: pdb-ws.yaml
-    set:
-      supersetWebsockets.enabled: true
-      supersetWebsockets.podDisruptionBudget.enabled: true
-      supersetWebsockets.podDisruptionBudget.maxUnavailable: null
-    asserts:
-      - equal:
-          path: metadata.labels["app.kubernetes.io/component"]
-          value: websocket
-      - equal:
-          path: spec.selector.matchLabels["app.kubernetes.io/component"]
-          value: websocket
-
-  - it: should use recommended labels on init job pod template
-    template: init-job.yaml
-    set:
-      init.enabled: true
-    asserts:
-      - equal:
-          path: spec.template.metadata.labels["app.kubernetes.io/instance"]
-          value: RELEASE-NAME
-      - equal:
-          path: spec.template.metadata.labels["app.kubernetes.io/component"]
-          value: init
-      - isNotNull:
-          path: spec.template.metadata.labels.job

helm/superset/values.yaml

@@ -283,7 +283,6 @@ supersetNode:
     redis_ssl:
       enabled: false
       ssl_cert_reqs: CERT_NONE
-    redis_driver: ""
     # You need to change below configuration incase bringing own PostgresSQL instance and also set postgresql.enabled:false
     # -- Database type for Superset metadata (Supported types: "postgresql", "mysql")
     db_type: "postgresql"
@@ -335,8 +334,6 @@ supersetNode:
   deploymentAnnotations: {}
   # -- Labels to be added to supersetNode deployment
   deploymentLabels: {}
-  # -- Custom pod spec to be added to supersetNode deployment
-  deploymentAdditionalPodSpec: {}
   # -- Affinity to be added to supersetNode deployment
   affinity: {}
   # -- TopologySpreadConstrains to be added to supersetNode deployments
@@ -462,8 +459,6 @@ supersetWorker:
   deploymentAnnotations: {}
   # -- Labels to be added to supersetWorker deployment
   deploymentLabels: {}
-  # -- Custom pod spec to be added to supersetWorker deployment
-  deploymentAdditionalPodSpec: {}
   # -- Affinity to be added to supersetWorker deployment
   affinity: {}
   # -- TopologySpreadConstrains to be added to supersetWorker deployments
@@ -570,8 +565,6 @@ supersetCeleryBeat:
   extraContainers: []
   # -- Annotations to be added to supersetCeleryBeat deployment
   deploymentAnnotations: {}
-  # -- Custom pod spec to be added to supersetCeleryBeat deployment
-  deploymentAdditionalPodSpec: {}
   # -- Affinity to be added to supersetCeleryBeat deployment
   affinity: {}
   # -- TopologySpreadConstrains to be added to supersetCeleryBeat deployments
@@ -687,8 +680,6 @@ supersetCeleryFlower:
   extraContainers: []
   # -- Annotations to be added to supersetCeleryFlower deployment
   deploymentAnnotations: {}
-  # -- Custom pod spec to be added to supersetCeleryFlower deployment
-  deploymentAdditionalPodSpec: {}
   # -- Affinity to be added to supersetCeleryFlower deployment
   affinity: {}
   # -- TopologySpreadConstrains to be added to supersetCeleryFlower deployments
@@ -766,8 +757,6 @@ supersetWebsockets:
   # -- Launch additional containers into supersetWebsockets pods
   extraContainers: []
   deploymentAnnotations: {}
-  # -- Custom pod spec to be added to supersetWebsockets deployment
-  deploymentAdditionalPodSpec: {}
   # -- Affinity to be added to supersetWebsockets deployment
   affinity: {}
   # -- TopologySpreadConstrains to be added to supersetWebsockets deployments
@@ -830,8 +819,6 @@ init:
   jobAnnotations:
     "helm.sh/hook": post-install,post-upgrade
     "helm.sh/hook-delete-policy": "before-hook-creation"
-  # -- Custom pod spec to be added to init job
-  additionalPodSpec: {}
   loadExamples: false
   createAdmin: true
   adminUser:

pyproject.toml

@@ -51,10 +51,10 @@ dependencies = [
     "flask-cors>=6.0.5, <7.0",
     "croniter>=6.2.2",
     "cron-descriptor",
-    "cryptography>=49.0.0, <50.0.0",
+    "cryptography>=48.0.0, <49.0.0",
     "deprecation>=2.1.0, <2.2.0",
     "flask>=2.2.5, <4.0.0",
-    "flask-appbuilder>=5.2.2, <6.0.0",
+    "flask-appbuilder>=5.2.1, <6.0.0",
     "flask-caching>=2.1.0, <3",
     "flask-compress>=1.13, <2.0",
     "flask-talisman>=1.0.0, <2.0",
@@ -64,7 +64,7 @@ dependencies = [
     "flask-wtf>=1.3.0, <2.0",
     "geopy",
     "greenlet<=3.5.1, >=3.5.1",
-    "gunicorn>=26.0.0, <27; sys_platform != 'win32'",
+    "gunicorn>=25.3.0, <26; sys_platform != 'win32'",
     "hashids>=1.3.1, <2",
     # holidays>=0.45 required for security fix
     "holidays>=0.45, <1",
@@ -77,7 +77,7 @@ dependencies = [
     # Flask-AppBuilder workaround. Tracking issue:
     # https://github.com/apache/superset/issues/33162
     "marshmallow>=3.0, <5",
-    "marshmallow-union>=0.1.15.post1",
+    "marshmallow-union>=0.1",
     "msgpack>=1.2.0, <1.3",
     "nh3>=0.3.5, <0.4",
     "numpy>1.23.5, <2.3",
@@ -101,14 +101,14 @@ dependencies = [
     "pyyaml>=6.0.3, <7.0.0",
     "PyJWT>=2.4.0, <3.0",
     "redis>=5.0.0, <6.0",
-    "rison>=2.0.1, <3.0",
-    "selenium>=4.45.0, <5.0",
+    "rison>=2.0.0, <3.0",
+    "selenium>=4.44.0, <5.0",
     "shillelagh[gsheetsapi]>=1.4.4, <2.0",
     "sshtunnel>=0.4.0, <0.5",
     "simplejson>=4.1.1",
-    "slack_sdk>=3.42.0, <4",
+    "slack_sdk>=3.19.0, <4",
     "sqlalchemy>=1.4, <2",
-    "sqlalchemy-utils>=0.42.1, <0.43", # expanding lowerbound to work with pydoris
+    "sqlalchemy-utils>=0.38.0, <0.43", # expanding lowerbound to work with pydoris
     "sqlglot>=30.8.0, <31",
     # newer pandas needs 0.9+
     "tabulate>=0.10.0, <1.0",
@@ -137,7 +137,7 @@ d1 = [
     "sqlalchemy-d1>=0.1.0",
     "dbapi-d1>=0.1.0",
 ]
-databend = ["databend-sqlalchemy>=0.5.5, <1.0"]
+databend = ["databend-sqlalchemy>=0.3.2, <1.0"]
 databricks = [
     "databricks-sql-connector==4.2.6",
     "databricks-sqlalchemy==1.0.5",
@@ -147,14 +147,14 @@ denodo = ["denodo-sqlalchemy>=2.0.5,<2.1.0"]
 dremio = ["sqlalchemy-dremio>=1.2.1, <4"]
 drill = ["sqlalchemy-drill>=1.1.10, <2"]
 druid = ["pydruid>=0.6.5,<0.7"]
-duckdb = ["duckdb>=1.5.4,<2", "duckdb-engine>=0.17.0"]
+duckdb = ["duckdb>=1.5.2,<2", "duckdb-engine>=0.17.0"]
 dynamodb = ["pydynamodb>=0.4.2"]
 solr = ["sqlalchemy-solr >= 0.2.4.3"]
 elasticsearch = ["elasticsearch-dbapi>=0.2.13, <0.3.0"]
 exasol = ["sqlalchemy-exasol>=2.4.0, <8.0"]
 excel = ["xlrd>=2.0.2, <2.1"]
 fastmcp = [
-    "fastmcp>=3.4.2,<4.0",
+    "fastmcp>=3.2.4,<4.0",
     # tiktoken backs the response-size-guard token estimator. Without
     # it, the middleware falls back to a coarser character-based
     # heuristic that under-counts JSON-heavy MCP responses.
@@ -174,19 +174,19 @@ hive = [
 ]
 impala = ["impyla>0.16.2, <0.23"]
 kusto = ["sqlalchemy-kusto>=3.1.2, <4"]
-kylin = ["kylinpy>=2.8.4, <2.9"]
+kylin = ["kylinpy>=2.8.1, <2.9"]
 mssql = ["pymssql>=2.3.13, <3"]
 # motherduck is an alias for duckdb - MotherDuck works via the duckdb driver
 motherduck = ["apache-superset[duckdb]"]
-mysql = ["mysqlclient>=2.2.8, <3"]
+mysql = ["mysqlclient>=2.1.0, <3"]
 ocient = [
-    "sqlalchemy-ocient>=1.0.0, <4",
+    "sqlalchemy-ocient>=1.0.0",
     "pyocient>=1.0.15, <4",
     "shapely",
     "geojson",
 ]
 oracle = ["oracledb>=2.0.0, <5"]
-parseable = ["sqlalchemy-parseable>=0.1.6,<0.2.0"]
+parseable = ["sqlalchemy-parseable>=0.1.3,<0.2.0"]
 pinot = ["pinotdb>=5.0.0, <10.0.0"]
 playwright = ["playwright>=1.60.0, <2"]
 postgres = ["psycopg2-binary==2.9.12"]
@@ -196,8 +196,8 @@ prophet = ["prophet>=1.1.6, <2"]
 redshift = ["sqlalchemy-redshift>=0.8.1, <0.9"]
 risingwave = ["sqlalchemy-risingwave"]
 shillelagh = ["shillelagh[all]>=1.4.4, <2"]
-singlestore = ["sqlalchemy-singlestoredb>=1.2.1, <2"]
-snowflake = ["snowflake-sqlalchemy>=1.10.2, <2"]
+singlestore = ["sqlalchemy-singlestoredb>=1.1.1, <2"]
+snowflake = ["snowflake-sqlalchemy>=1.2.4, <2"]
 sqlite = ["syntaqlite>=0.1.0,<0.5.0"]
 spark = [
     "pyhive[hive]>=0.6.5;python_version<'3.11'",
@@ -206,17 +206,17 @@ spark = [
     "thrift>=0.23.0, <1",
 ]
 tdengine = [
-    "taospy>=2.8.9",
+    "taospy>=2.7.21",
     "taos-ws-py>=0.6.9"
 ]
 teradata = ["teradatasql>=16.20.0.23"]
 thumbnails = [] # deprecated, will be removed in 7.0
 vertica = ["sqlalchemy-vertica-python>= 0.6.3, < 0.7"]
-netezza = ["nzalchemy>=11.0.2, < 11.2"]
+netezza = ["nzalchemy>=11.0.2"]
 starrocks = ["starrocks>=1.3.3, <2"]
 doris = ["pydoris>=1.0.0, <2.0.0"]
 oceanbase = ["oceanbase_py>=0.0.1.2"]
-ydb = ["ydb-sqlalchemy>=0.1.22", "ydb-sqlglot-plugin>=0.2.8"]
+ydb = ["ydb-sqlalchemy>=0.1.22", "ydb-sqlglot-plugin>=0.2.5"]
 development = [
     # no bounds for apache-superset-extensions-cli until a stable version
     "apache-superset-extensions-cli",
@@ -375,7 +375,6 @@ select = [
 
 ignore = [
     "S101",
-    "PT001",  # pytest-fixture-incorrect-parentheses-style: different ruff versions disagree
     "PT006",
     "T201",
     "N999",

pytest.ini

@@ -43,5 +43,5 @@ filterwarnings =
 #    error:The ``declarative_base\(\)`` function is now available:sqlalchemy.exc.RemovedIn20Warning
 #    error:The Engine.execute\(\) method is considered legacy:sqlalchemy.exc.RemovedIn20Warning
     error:The legacy calling style of select\(\) is deprecated:sqlalchemy.exc.RemovedIn20Warning
-    error:The "whens" argument to case:sqlalchemy.exc.RemovedIn20Warning
+#    error:The "whens" argument to case:sqlalchemy.exc.RemovedIn20Warning
 #    error:"User" object is being merged into a Session:sqlalchemy.exc.RemovedIn20Warning

requirements/base.in

@@ -26,7 +26,7 @@ filelock>=3.20.3,<4.0.0
 brotli>=1.2.0,<2.0.0
 numexpr>=2.9.0
 # Security: CVE-2026-34073 (MEDIUM) - Improper Certificate Validation
-cryptography>=49.0.0,<50.0.0
+cryptography>=48.0.0,<49.0.0
 # Security: Snyk - XSS vulnerability in Mako templates
 mako>=1.3.11,<2.0.0
 # Security: CVE-2024-52338 (CRITICAL) - Deserialization of untrusted data in IPC/Parquet readers

requirements/base.txt

@@ -86,7 +86,7 @@ cron-descriptor==1.4.5
     # via apache-superset (pyproject.toml)
 croniter==6.2.2
     # via apache-superset (pyproject.toml)
-cryptography==49.0.0
+cryptography==48.0.1
     # via
     #   -r requirements/base.in
     #   apache-superset (pyproject.toml)
@@ -122,7 +122,7 @@ flask==2.3.3
     #   flask-session
     #   flask-sqlalchemy
     #   flask-wtf
-flask-appbuilder==5.2.2
+flask-appbuilder==5.2.1
     # via
     #   apache-superset (pyproject.toml)
     #   apache-superset-core
@@ -169,7 +169,7 @@ greenlet==3.5.1
     #   apache-superset (pyproject.toml)
     #   shillelagh
     #   sqlalchemy
-gunicorn==26.0.0
+gunicorn==25.3.0
     # via apache-superset (pyproject.toml)
 h11==0.16.0
     # via wsproto
@@ -236,7 +236,7 @@ marshmallow-sqlalchemy==1.5.0
     # via
     #   -r requirements/base.in
     #   flask-appbuilder
-marshmallow-union==0.1.15.post1
+marshmallow-union==0.1.15
     # via apache-superset (pyproject.toml)
 mdurl==0.1.2
     # via markdown-it-py
@@ -315,7 +315,7 @@ pygeohash==3.2.2
     # via apache-superset (pyproject.toml)
 pygments==2.20.0
     # via rich
-pyjwt==2.13.0
+pyjwt==2.12.0
     # via
     #   apache-superset (pyproject.toml)
     #   flask-appbuilder
@@ -323,7 +323,7 @@ pyjwt==2.13.0
     #   redis
 pynacl==1.6.2
     # via paramiko
-pyopenssl==26.3.0
+pyopenssl==26.2.0
     # via
     #   -r requirements/base.in
     #   shillelagh
@@ -369,13 +369,13 @@ rfc3339-validator==0.1.4
     # via openapi-schema-validator
 rich==13.9.4
     # via flask-limiter
-rison==2.0.1
+rison==2.0.0
     # via apache-superset (pyproject.toml)
 rpds-py==0.25.0
     # via
     #   jsonschema
     #   referencing
-selenium==4.45.0
+selenium==4.44.0
     # via apache-superset (pyproject.toml)
 setuptools==80.9.0
     # via -r requirements/base.in
@@ -389,7 +389,7 @@ six==1.17.0
     #   python-dateutil
     #   rfc3339-validator
     #   wtforms-json
-slack-sdk==3.42.0
+slack-sdk==3.35.0
     # via apache-superset (pyproject.toml)
 sniffio==1.3.1
     # via trio
@@ -405,7 +405,7 @@ sqlalchemy==1.4.54
     #   marshmallow-sqlalchemy
     #   shillelagh
     #   sqlalchemy-utils
-sqlalchemy-utils==0.42.1
+sqlalchemy-utils==0.42.0
     # via
     #   apache-superset (pyproject.toml)
     #   apache-superset-core

requirements/development.txt

@@ -53,7 +53,7 @@ attrs==25.3.0
     #   requests-cache
     #   trio
 authlib==1.6.12
-    # via fastmcp-slim
+    # via fastmcp
 babel==2.17.0
     # via
     #   -c requirements/base-constraint.txt
@@ -178,13 +178,12 @@ croniter==6.2.2
     # via
     #   -c requirements/base-constraint.txt
     #   apache-superset
-cryptography==49.0.0
+cryptography==48.0.1
     # via
     #   -c requirements/base-constraint.txt
     #   apache-superset
     #   authlib
     #   google-auth
-    #   joserfc
     #   paramiko
     #   pyjwt
     #   pyopenssl
@@ -192,7 +191,7 @@ cryptography==49.0.0
 cycler==0.12.1
     # via matplotlib
 cyclopts==4.2.4
-    # via fastmcp-slim
+    # via fastmcp
 db-dtypes==1.3.1
     # via pandas-gbq
 defusedxml==0.7.1
@@ -221,7 +220,7 @@ docstring-parser==0.17.0
     # via cyclopts
 docutils==0.22.2
     # via rich-rst
-duckdb==1.5.4
+duckdb==1.5.3
     # via
     #   apache-superset
     #   duckdb-engine
@@ -237,11 +236,9 @@ et-xmlfile==2.0.0
     #   -c requirements/base-constraint.txt
     #   openpyxl
 exceptiongroup==1.3.0
-    # via fastmcp-slim
-fastmcp==3.4.2
-    # via apache-superset
-fastmcp-slim==3.4.2
     # via fastmcp
+fastmcp==3.2.4
+    # via apache-superset
 filelock==3.20.3
     # via
     #   -c requirements/base-constraint.txt
@@ -263,7 +260,7 @@ flask==2.3.3
     #   flask-sqlalchemy
     #   flask-testing
     #   flask-wtf
-flask-appbuilder==5.2.2
+flask-appbuilder==5.2.1
     # via
     #   -c requirements/base-constraint.txt
     #   apache-superset
@@ -385,7 +382,7 @@ greenlet==3.5.1
     #   shillelagh
     #   sqlalchemy
 griffelib==2.0.2
-    # via fastmcp-slim
+    # via fastmcp
 grpcio==1.81.1
     # via
     #   apache-superset
@@ -393,7 +390,7 @@ grpcio==1.81.1
     #   grpcio-status
 grpcio-status==1.60.1
     # via google-api-core
-gunicorn==26.0.0
+gunicorn==25.3.0
     # via
     #   -c requirements/base-constraint.txt
     #   apache-superset
@@ -416,7 +413,7 @@ httpcore==1.0.9
     # via httpx
 httpx==0.28.1
     # via
-    #   fastmcp-slim
+    #   fastmcp
     #   mcp
 httpx-sse==0.4.1
     # via mcp
@@ -475,14 +472,12 @@ jmespath==1.1.0
     # via
     #   boto3
     #   botocore
-joserfc==1.7.2
-    # via fastmcp-slim
 jsonpath-ng==1.8.0
     # via
     #   -c requirements/base-constraint.txt
     #   apache-superset
 jsonref==1.1.0
-    # via fastmcp-slim
+    # via fastmcp
 jsonschema==4.23.0
     # via
     #   -c requirements/base-constraint.txt
@@ -492,7 +487,7 @@ jsonschema==4.23.0
     #   openapi-spec-validator
 jsonschema-path==0.3.4
     # via
-    #   fastmcp-slim
+    #   fastmcp
     #   openapi-spec-validator
 jsonschema-specifications==2025.4.1
     # via
@@ -546,7 +541,7 @@ marshmallow-sqlalchemy==1.5.0
     # via
     #   -c requirements/base-constraint.txt
     #   flask-appbuilder
-marshmallow-union==0.1.15.post1
+marshmallow-union==0.1.15
     # via
     #   -c requirements/base-constraint.txt
     #   apache-superset
@@ -555,7 +550,7 @@ matplotlib==3.9.0
 mccabe==0.7.0
     # via pylint
 mcp==1.24.0
-    # via fastmcp-slim
+    # via fastmcp
 mdurl==0.1.2
     # via
     #   -c requirements/base-constraint.txt
@@ -572,7 +567,7 @@ msgspec==0.19.0
     # via
     #   -c requirements/base-constraint.txt
     #   flask-session
-mysqlclient==2.2.8
+mysqlclient==2.2.6
     # via apache-superset
 nh3==0.3.5
     # via
@@ -599,7 +594,7 @@ odfpy==1.4.1
     #   -c requirements/base-constraint.txt
     #   pandas
 openapi-pydantic==0.5.1
-    # via fastmcp-slim
+    # via fastmcp
 openapi-schema-validator==0.6.3
     # via
     #   -c requirements/base-constraint.txt
@@ -611,7 +606,7 @@ openpyxl==3.1.5
     #   -c requirements/base-constraint.txt
     #   pandas
 opentelemetry-api==1.39.1
-    # via fastmcp-slim
+    # via fastmcp
 ordered-set==4.1.0
     # via
     #   -c requirements/base-constraint.txt
@@ -632,7 +627,7 @@ packaging==25.0
     #   deprecation
     #   docker
     #   duckdb-engine
-    #   fastmcp-slim
+    #   fastmcp
     #   google-cloud-bigquery
     #   gunicorn
     #   limits
@@ -677,7 +672,7 @@ pip==25.1.1
 platformdirs==4.3.8
     # via
     #   -c requirements/base-constraint.txt
-    #   fastmcp-slim
+    #   fastmcp
     #   pylint
     #   requests-cache
     #   virtualenv
@@ -719,7 +714,7 @@ psutil==6.1.0
 psycopg2-binary==2.9.12
     # via apache-superset
 py-key-value-aio==0.4.4
-    # via fastmcp-slim
+    # via fastmcp
 pyarrow==24.0.0
     # via
     #   -c requirements/base-constraint.txt
@@ -746,7 +741,7 @@ pydantic==2.11.7
     #   -c requirements/base-constraint.txt
     #   apache-superset
     #   apache-superset-core
-    #   fastmcp-slim
+    #   fastmcp
     #   mcp
     #   openapi-pydantic
     #   pydantic-settings
@@ -755,9 +750,7 @@ pydantic-core==2.33.2
     #   -c requirements/base-constraint.txt
     #   pydantic
 pydantic-settings==2.10.1
-    # via
-    #   fastmcp-slim
-    #   mcp
+    # via mcp
 pydata-google-auth==1.9.0
     # via pandas-gbq
 pydruid==0.6.9
@@ -776,7 +769,7 @@ pyhive==0.7.0
     # via apache-superset
 pyinstrument==5.1.2
     # via apache-superset
-pyjwt==2.13.0
+pyjwt==2.12.0
     # via
     #   -c requirements/base-constraint.txt
     #   apache-superset
@@ -790,7 +783,7 @@ pynacl==1.6.2
     # via
     #   -c requirements/base-constraint.txt
     #   paramiko
-pyopenssl==26.3.0
+pyopenssl==26.2.0
     # via
     #   -c requirements/base-constraint.txt
     #   shillelagh
@@ -800,7 +793,7 @@ pyparsing==3.2.3
     #   apache-superset
     #   matplotlib
 pyperclip==1.10.0
-    # via fastmcp-slim
+    # via fastmcp
 pysocks==1.7.1
     # via
     #   -c requirements/base-constraint.txt
@@ -842,14 +835,12 @@ python-dotenv==1.2.2
     # via
     #   -c requirements/base-constraint.txt
     #   apache-superset
-    #   fastmcp-slim
+    #   fastmcp
     #   pydantic-settings
 python-ldap==3.4.7
     # via apache-superset
 python-multipart==0.0.29
-    # via
-    #   fastmcp-slim
-    #   mcp
+    # via mcp
 pytz==2025.2
     # via
     #   -c requirements/base-constraint.txt
@@ -865,7 +856,7 @@ pyyaml==6.0.3
     #   -c requirements/base-constraint.txt
     #   apache-superset
     #   apispec
-    #   fastmcp-slim
+    #   fastmcp
     #   jsonschema-path
     #   pre-commit
 redis==5.3.1
@@ -908,12 +899,12 @@ rich==13.9.4
     # via
     #   -c requirements/base-constraint.txt
     #   cyclopts
-    #   fastmcp-slim
+    #   fastmcp
     #   flask-limiter
     #   rich-rst
 rich-rst==1.3.1
     # via cyclopts
-rison==2.0.1
+rison==2.0.0
     # via
     #   -c requirements/base-constraint.txt
     #   apache-superset
@@ -928,7 +919,7 @@ s3transfer==0.16.0
     # via boto3
 secretstorage==3.5.0
     # via keyring
-selenium==4.45.0
+selenium==4.44.0
     # via
     #   -c requirements/base-constraint.txt
     #   apache-superset
@@ -957,7 +948,7 @@ six==1.17.0
     #   python-dateutil
     #   rfc3339-validator
     #   wtforms-json
-slack-sdk==3.42.0
+slack-sdk==3.35.0
     # via
     #   -c requirements/base-constraint.txt
     #   apache-superset
@@ -985,7 +976,7 @@ sqlalchemy==1.4.54
     #   sqlalchemy-utils
 sqlalchemy-bigquery==1.17.0
     # via apache-superset
-sqlalchemy-utils==0.42.1
+sqlalchemy-utils==0.42.0
     # via
     #   -c requirements/base-constraint.txt
     #   apache-superset
@@ -1004,10 +995,8 @@ sshtunnel==0.4.0
     # via
     #   -c requirements/base-constraint.txt
     #   apache-superset
-starlette==1.3.1
-    # via
-    #   fastmcp-slim
-    #   mcp
+starlette==0.49.1
+    # via mcp
 statsd==4.0.1
     # via apache-superset
 syntaqlite==0.4.2
@@ -1046,7 +1035,6 @@ typing-extensions==4.15.0
     #   apache-superset-core
     #   cattrs
     #   exceptiongroup
-    #   fastmcp-slim
     #   grpcio
     #   limits
     #   mcp
@@ -1074,7 +1062,7 @@ tzdata==2025.2
 tzlocal==5.2
     # via trino
 uncalled-for==0.2.0
-    # via fastmcp-slim
+    # via fastmcp
 url-normalize==2.2.1
     # via
     #   -c requirements/base-constraint.txt
@@ -1089,7 +1077,7 @@ urllib3==2.7.0
     #   selenium
 uvicorn==0.37.0
     # via
-    #   fastmcp-slim
+    #   fastmcp
     #   mcp
 vine==5.1.0
     # via
@@ -1105,7 +1093,7 @@ watchdog==6.0.0
     #   apache-superset
     #   apache-superset-extensions-cli
 watchfiles==1.1.1
-    # via fastmcp-slim
+    # via fastmcp
 wcwidth==0.2.13
     # via
     #   -c requirements/base-constraint.txt
@@ -1115,7 +1103,7 @@ websocket-client==1.8.0
     #   -c requirements/base-constraint.txt
     #   selenium
 websockets==15.0.1
-    # via fastmcp-slim
+    # via fastmcp
 werkzeug==3.1.6
     # via
     #   -c requirements/base-constraint.txt

scripts/translations/apply_do_not_translate.py

@@ -1,128 +0,0 @@
-#!/usr/bin/env python3
-# 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.
-"""Stamp do-not-translate msgids in a .pot with an extracted-comment marker.
-
-For every msgid listed in ``superset/translations/do-not-translate.txt`` that is
-present in the target .pot, add a ``#. do-not-translate`` extracted
-comment. gettext extracted comments (``#.``) propagate from the .pot into every
-language .po on ``pybabel update``, so the do-not-translate status stays
-consistent across all catalogs from a single registry.
-
-Run from ``babel_update.sh`` after the .pot is extracted and normalized (and
-before ``pybabel update``). Idempotent: re-running makes no further changes.
-
-Usage:
-  python scripts/translations/apply_do_not_translate.py [POT_PATH]
-  # POT_PATH defaults to superset/translations/messages.pot
-"""
-
-from __future__ import annotations
-
-import sys
-from pathlib import Path
-
-# The standardized extracted-comment marker. Kept in sync with backfill_po.py.
-MARKER: str = "do-not-translate"
-_MARKER_LINE: str = f"#. {MARKER}"
-
-TRANSLATIONS_DIR: Path = (
-    Path(__file__).parent.parent.parent / "superset" / "translations"
-)
-DEFAULT_POT: Path = TRANSLATIONS_DIR / "messages.pot"
-REGISTRY: Path = TRANSLATIONS_DIR / "do-not-translate.txt"
-
-
-def load_registry(path: Path = REGISTRY) -> set[str]:
-    """Return the set of do-not-translate msgids (skips comments/blank lines).
-
-    Each line is stripped before the blank/comment check, so trailing
-    whitespace or an indented comment never yields a msgid that fails to match
-    the .pot.
-    """
-    if not path.exists():
-        return set()
-    entries: set[str] = set()
-    for raw_line in path.read_text(encoding="utf-8").splitlines():
-        line: str = raw_line.strip()
-        if line and not line.startswith("#"):
-            entries.add(line)
-    return entries
-
-
-def _escape(msgid: str) -> str:
-    """Escape a msgid the way gettext writes it on a `msgid "..."` line."""
-    return msgid.replace("\\", "\\\\").replace('"', '\\"')
-
-
-def apply_markers(pot_path: Path, registry: set[str]) -> int:
-    """Insert the marker comment above each registry msgid via text edit.
-
-    Text manipulation (rather than a polib round-trip) preserves the .pot's
-    exact wrapping/layout, so the only change is the added marker lines.
-    Idempotent. Returns the number of entries newly marked.
-    """
-    lines: list[str] = pot_path.read_text(encoding="utf-8").split("\n")
-    targets: set[str] = {f'msgid "{_escape(m)}"' for m in registry}
-    out: list[str] = []
-    changed: int = 0
-    for line in lines:
-        if line in targets and (not out or out[-1] != _MARKER_LINE):
-            # `#.` extracted comments precede `msgid`; these registry entries are
-            # bare single-line msgids, so inserting directly above is correct.
-            out.append(_MARKER_LINE)
-            changed += 1
-        out.append(line)
-    if changed:
-        pot_path.write_text("\n".join(out), encoding="utf-8")
-    return changed
-
-
-def main() -> None:
-    """Stamp the marker onto the target .pot from the registry."""
-    pot_path: Path = Path(sys.argv[1]) if len(sys.argv) > 1 else DEFAULT_POT
-    if not pot_path.exists():
-        print(f"POT file not found: {pot_path}", file=sys.stderr)
-        sys.exit(1)
-    # Fail fast if the registry file is absent: babel_update.sh depends on this
-    # step to stamp the .pot, and continuing would silently publish catalogs
-    # without any do-not-translate markers. An existing-but-empty registry is a
-    # valid state (nothing to mark), so only a missing file is an error.
-    if not REGISTRY.exists():
-        print(
-            f"do-not-translate registry not found at {REGISTRY}; refusing to "
-            "produce unmarked translation artifacts.",
-            file=sys.stderr,
-        )
-        sys.exit(1)
-    registry: set[str] = load_registry()
-    if not registry:
-        print(
-            f"do-not-translate registry {REGISTRY} is empty; nothing to mark.",
-            file=sys.stderr,
-        )
-        return
-    changed: int = apply_markers(pot_path, registry)
-    print(
-        f"do-not-translate: marked {changed} new entr(y/ies) with {MARKER} "
-        f"in {pot_path.name} ({len(registry)} msgids in registry).",
-        file=sys.stderr,
-    )
-
-
-if __name__ == "__main__":
-    main()

scripts/translations/babel_update.sh

@@ -55,14 +55,6 @@ msgcat --sort-by-msgid --no-wrap --no-location superset/translations/messages.po
 cat $LICENSE_TMP superset/translations/messages.pot > messages.pot.tmp \
   && mv messages.pot.tmp superset/translations/messages.pot
 
-# Stamp do-not-translate msgids (superset/translations/do-not-translate.txt) with
-# a `#. do-not-translate` extracted comment. Extracted comments
-# propagate from the .pot into every catalog on the `pybabel update` below, so
-# the do-not-translate status stays consistent across all languages.
-# Fail fast: without this guard the script would continue past a marker-stamping
-# failure and `pybabel update` would publish catalogs missing the markers.
-python scripts/translations/apply_do_not_translate.py superset/translations/messages.pot || exit 1
-
 # --no-fuzzy-matching: when a *new* source string is added, Babel's fuzzy
 # matcher otherwise guesses a "close" existing translation and marks it
 # `#, fuzzy` in every language catalog. Those guesses are (a) usually wrong

scripts/translations/backfill_po.py

@@ -91,28 +91,22 @@ _ASF_LICENSE_HEADER = """\
 LANGUAGE_NAMES: dict[str, str] = {
     "ar": "Arabic",
     "ca": "Catalan",
-    "cs": "Czech",
     "de": "German",
     "es": "Spanish",
     "fa": "Persian (Farsi)",
-    "fi": "Finnish",
     "fr": "French",
     "it": "Italian",
     "ja": "Japanese",
     "ko": "Korean",
-    "lv": "Latvian",
     "mi": "Māori",
     "nl": "Dutch",
     "pl": "Polish",
     "pt": "Portuguese",
     "pt_BR": "Brazilian Portuguese",
-    "ro": "Romanian",
     "ru": "Russian",
     "sk": "Slovak",
     "sl": "Slovenian",
     "sr": "Serbian",
-    "sr_Latn": "Serbian (Latin script)",
-    "th": "Thai",
     "tr": "Turkish",
     "uk": "Ukrainian",
     "zh": "Chinese (Simplified)",
@@ -152,60 +146,6 @@ def _is_missing(entry: polib.POEntry) -> bool:
     return not entry.msgstr
 
 
-# Canonical registry of msgids that must never be machine-translated: literal
-# tokens compared against source (SQL keywords, confirmation words), enum values
-# (d3 interpolation modes), icon names (e.g. "bolt" -> the ⚡ Explore control
-# icon), API field names, code constants, and example placeholders. Translating
-# them can break icon lookups, enum matching, or API contracts, or is simply
-# meaningless (proper nouns, example values). apply_do_not_translate.py stamps
-# these msgids in messages.pot with a `#. do-not-translate`
-# extracted comment that propagates to every catalog on `pybabel update`.
-DO_NOT_TRANSLATE_REGISTRY: Path = TRANSLATIONS_DIR / "do-not-translate.txt"
-
-
-def _load_do_not_translate(path: Path = DO_NOT_TRANSLATE_REGISTRY) -> frozenset[str]:
-    """Load the do-not-translate msgids (skips comment/blank lines).
-
-    Lines are stripped before the blank/comment checks, matching the parsing in
-    apply_do_not_translate.py, so trailing whitespace or an indented comment
-    never yields a msgid that fails to match a catalog entry.
-    """
-    if not path.exists():
-        return frozenset()
-    return frozenset(
-        stripped
-        for line in path.read_text(encoding="utf-8").splitlines()
-        if (stripped := line.strip()) and not stripped.startswith("#")
-    )
-
-
-DO_NOT_TRANSLATE: frozenset[str] = _load_do_not_translate()
-
-# An explicit do-not-translate marker on an entry, matched in either the
-# extracted comment (`#. do-not-translate`, the standard propagated
-# from the .pot) or a translator comment (e.g. the ru catalog's legacy
-# "# Не переводить"). Honored so a human's deliberate decision is never
-# overridden even if a msgid is missing from the registry.
-_DO_NOT_TRANSLATE_COMMENT: re.Pattern[str] = re.compile(
-    r"не\s+переводить|do[\s-]?not[\s-]?translate|don'?t\s+translate",
-    re.IGNORECASE,
-)
-
-
-def _is_do_not_translate(entry: polib.POEntry) -> bool:
-    """Return True if an entry must be left for a human (never machine-filled).
-
-    Either its msgid is in the do-not-translate registry, or the entry carries
-    an explicit do-not-translate marker in its extracted or translator comment.
-    """
-    if entry.msgid in DO_NOT_TRANSLATE:
-        return True
-    return any(
-        comment and _DO_NOT_TRANSLATE_COMMENT.search(comment)
-        for comment in (entry.comment, entry.tcomment)
-    )
-
-
 def _context_langs(
     item: dict[str, Any], index: dict[str, Any], target_lang: str
 ) -> list[str]:
@@ -406,97 +346,6 @@ def translate_batch(
     return parse_response(result.stdout.strip(), len(batch))
 
 
-def _translate_single_plaintext(
-    model: str,
-    target_lang: str,
-    item: dict[str, Any],
-    index: dict[str, Any],
-) -> str | None:
-    """Translate a single entry with a plain-text prompt (no JSON envelope).
-
-    Fallback for an entry whose JSON batch response cannot be parsed — typically
-    because the source string contains literal double-quotes that the model
-    echoes back unescaped, corrupting the surrounding JSON. Asking for a bare
-    string sidesteps the JSON contract entirely. Returns the translation text,
-    or None if the CLI call fails.
-    """
-    claude_bin = shutil.which("claude")
-    if not claude_bin:
-        raise RuntimeError(
-            "claude CLI not found. Install Claude Code or add it to PATH."
-        )
-    lines = [
-        "You are a professional translator specializing in software UI strings.",
-        f"Translate the following English string into {_lang_name(target_lang)} "
-        f"({target_lang}).",
-        "Return ONLY the translation as plain text — no surrounding quotes, no "
-        "JSON, no markdown fences, no explanation.",
-        "Preserve all format placeholders exactly (%(name)s, {name}, %s, %d), any "
-        "HTML tags, and any inner quotation marks.",
-        "",
-        f"English: {item['msgid']}",
-    ]
-    if item.get("msgid_plural"):
-        lines.append(f"English plural: {item['msgid_plural']}")
-    refs = index.get(item["index_key"], {})
-    ref_lines = [
-        f"{_lang_name(lang)}: {val}"
-        for lang, val in sorted(refs.items())
-        if lang != target_lang and isinstance(val, str) and val
-    ]
-    if ref_lines:
-        lines.append("")
-        lines.append("Reference translations in other languages:")
-        lines.extend(ref_lines)
-    prompt = "\n".join(lines)
-    # claude_bin is resolved via shutil.which — not user-controlled input
-    result = subprocess.run(  # noqa: S603
-        [claude_bin, "--model", model, "-p"],
-        input=prompt,
-        capture_output=True,
-        text=True,
-        check=False,
-    )
-    if result.returncode != 0:
-        return None
-    text = result.stdout.strip()
-    # Strip accidental markdown fences or wrapping quotes the model may add.
-    text = re.sub(r"^```[^\n]*\n?", "", text)
-    text = re.sub(r"\n?```$", "", text).strip()
-    if len(text) >= 2 and text[0] == '"' and text[-1] == '"':
-        text = text[1:-1]
-    return text or None
-
-
-def _resilient_translate(
-    model: str,
-    target_lang: str,
-    batch: list[dict[str, Any]],
-    index: dict[str, Any],
-) -> dict[int, str]:
-    """Translate a batch, isolating entries that break the JSON response contract.
-
-    ``translate_batch`` sends the whole batch in one request and parses a single
-    JSON object back. A source string containing literal double-quotes can make
-    the model emit unescaped quotes, so ``json.loads`` fails and the ENTIRE batch
-    would be lost. To salvage the rest, on a parse failure (ValueError) we bisect
-    the batch and recurse; a lone entry that still fails falls back to a
-    plain-text prompt via ``_translate_single_plaintext``. Returned keys are
-    positions within ``batch``. RuntimeError (CLI failure) is left to propagate
-    to the caller, preserving the existing per-batch failure handling.
-    """
-    try:
-        return translate_batch(model, target_lang, batch, index)
-    except ValueError:
-        if len(batch) == 1:
-            text = _translate_single_plaintext(model, target_lang, batch[0], index)
-            return {0: text} if text else {}
-        mid = len(batch) // 2
-        left = _resilient_translate(model, target_lang, batch[:mid], index)
-        right = _resilient_translate(model, target_lang, batch[mid:], index)
-        return {**left, **{k + mid: v for k, v in right.items()}}
-
-
 def _apply_plural_translation(entry: polib.POEntry, translation: str) -> None:
     """Distribute a model response across the entry's plural forms.
 
@@ -613,7 +462,7 @@ def _process_batches(
             file=sys.stderr,
         )
         try:
-            translations = _resilient_translate(model, lang, batch_items, index)
+            translations = translate_batch(model, lang, batch_items, index)
         except (ValueError, RuntimeError) as exc:
             print(f"  ERROR in batch starting at {batch_start}: {exc}", file=sys.stderr)
             failed_count += len(batch_entries)
@@ -701,15 +550,6 @@ def backfill(
     missing: list[polib.POEntry] = [e for e in cat if e.msgid and _is_missing(e)]
     print(f"Found {len(missing)} untranslated entries for '{lang}'.", file=sys.stderr)
 
-    skipped_dnt: list[polib.POEntry] = [e for e in missing if _is_do_not_translate(e)]
-    if skipped_dnt:
-        missing = [e for e in missing if not _is_do_not_translate(e)]
-        print(
-            f"Skipping {len(skipped_dnt)} do-not-translate entries (literal "
-            f"tokens / translator-marked); they are left untranslated.",
-            file=sys.stderr,
-        )
-
     if min_context > 0:
         before = len(missing)
         missing = [

scripts/translations/build_translation_index.py

@@ -86,19 +86,7 @@ def build_index(translations_dir: Path) -> dict[str, Any]:
 
     for lang in langs:
         po_path = translations_dir / lang / "LC_MESSAGES" / "messages.po"
-        try:
-            cat = polib.pofile(str(po_path))
-        except (OSError, UnicodeDecodeError) as exc:
-            # A single malformed catalog shouldn't block backfilling every
-            # other language. polib raises OSError on syntax errors (e.g. an
-            # unescaped quote) and UnicodeDecodeError on bad encoding; skip
-            # either with a loud warning so the corrupt file gets fixed
-            # separately.
-            print(
-                f"WARNING: skipping {lang} — could not parse {po_path}: {exc}",
-                file=sys.stderr,
-            )
-            continue
+        cat = polib.pofile(str(po_path))
         for entry in cat:
             if not entry.msgid:
                 continue  # skip header entry

scripts/translations/check_translation_regression.py

@@ -20,31 +20,21 @@ Check that source-code changes don't cause translation regressions.
 
 What counts as a regression
 ---------------------------
-A regression is an *existing translation that a source change invalidated*:
-a message that was a **confirmed, non-fuzzy translation** in the baseline and
-is **fuzzy** after the PR. The check keys on this per-``msgid`` transition
-rather than on the aggregate count of fuzzy entries, because a bare count
-cannot tell apart two changes that move the fuzzy total by the same amount:
-
-* ``translated -> fuzzy`` — a reworded source string stranded a real
-  translation. **This is the regression.**
-* ``untranslated -> fuzzy`` — an empty ``msgstr`` was filled with a fuzzy
-  (unconfirmed) guess, e.g. an AI backfill committed as ``#, fuzzy``. No
-  existing translation was lost, so this is **not** a regression and must
-  pass.
-
-Keying on the per-entry transition lets a backfill PR commit fuzzy guesses for
-previously-untranslated strings (the ja/fi catalog backfills) without tripping
-the check, while still catching a genuine invalidation even when the same PR
-also adds new strings (which a count-delta heuristic would let mask it).
+A regression is an *existing translation that a source change invalidated*.
+The check keys on the **increase in fuzzy entries** rather than a drop in the
+translated count, because a count drop happens identically for a benign
+*deletion* and a real *rename*, so it cannot distinguish the two — whereas a
+``#, fuzzy`` marker unambiguously flags a stranded translation.
 
 Note ``babel_update.sh`` runs ``pybabel update`` with ``--no-fuzzy-matching``,
 so *adding* (or renaming) a source string does **not** auto-generate a fuzzy
 guess against an unrelated existing translation — new strings land as cleanly
-untranslated (empty ``msgstr``). The fuzzies this check sees therefore arrive
-another way — typically a committed ``.po`` edit. *Deleting* a string is still
-not a regression: with ``--ignore-obsolete`` it is simply dropped and no fuzzy
-is created.
+untranslated (empty ``msgstr``). This deliberately avoids the prior behaviour
+where *every* PR that merely added a translatable string tripped this check on
+spurious fuzzies. As a result the check now guards against ``#, fuzzy`` entries
+that arrive another way — e.g. a committed ``.po`` edit — rather than ones the
+update step synthesises. *Deleting* a string is still not a regression: with
+``--ignore-obsolete`` it is simply dropped and no fuzzy is created.
 
 Usage
 -----
@@ -137,72 +127,28 @@ def count_stats(po_file: Path) -> dict[str, int]:
     }
 
 
-def entry_keys(po_file: Path) -> dict[str, list[str]]:
-    """Return per-``msgid`` key sets for a .po file.
-
-    ``translated_keys`` lists the non-fuzzy, non-obsolete entries with a
-    populated ``msgstr`` — confirmed translations a source reword could strand.
-    ``fuzzy_keys`` lists the non-obsolete entries carrying the ``fuzzy`` flag
-    (however they arrived — a committed backfill guess or a real invalidation).
-
-    A key combines ``msgctxt`` and ``msgid`` (gettext's own identity rule) so
-    context-disambiguated entries stay distinct. The header entry (empty
-    ``msgid``) is ignored. The regression check compares the baseline's
-    ``translated_keys`` against the PR's ``fuzzy_keys``: their intersection is
-    exactly the set of confirmed translations the PR turned fuzzy.
-
-    Raises:
-        OSError: if ``polib`` cannot read or parse the file. As with a msgfmt
-            failure, a catalog we cannot parse is surfaced rather than silently
-            counted as empty.
-    """
-    import polib  # type: ignore[import-untyped]  # noqa: PLC0415
-
-    translated_keys: list[str] = []
-    fuzzy_keys: list[str] = []
-    for entry in polib.pofile(str(po_file)):
-        if entry.obsolete or not entry.msgid:
-            continue
-        key = f"{entry.msgctxt}\x04{entry.msgid}" if entry.msgctxt else entry.msgid
-        if "fuzzy" in entry.flags:
-            fuzzy_keys.append(key)
-        elif (
-            all(entry.msgstr_plural.values())
-            if entry.msgid_plural
-            else bool(entry.msgstr)
-        ):
-            translated_keys.append(key)
-    return {"translated_keys": translated_keys, "fuzzy_keys": fuzzy_keys}
-
-
 def get_counts(
     translations_dir: Path,
     failures: Optional[set[str]] = None,
-) -> dict[str, dict[str, object]]:
+) -> dict[str, dict[str, int]]:
     """Count translated/fuzzy entries for every ``.po`` file in a directory.
 
-    Each language maps to ``{"translated", "fuzzy", "translated_keys",
-    "fuzzy_keys"}`` — aggregate counts (for the human-readable summary) plus the
-    per-``msgid`` key sets the regression check actually keys on.
-
     If ``failures`` is provided, the name of each language whose ``.po`` file
-    is present on disk but could not be counted (msgfmt non-zero exit,
-    unparseable output, or a polib parse error) is added to it. Such a language
-    is deliberately absent from the returned mapping — but, unlike a language
-    whose catalog was simply deleted, it must not be mistaken for an intentional
-    removal: a caller that cares about the distinction (see :func:`cmd_compare`)
-    can inspect ``failures`` and treat it as a hard error.
+    is present on disk but could not be counted (msgfmt non-zero exit, or
+    unparseable output) is added to it. Such a language is deliberately absent
+    from the returned mapping — but, unlike a language whose catalog was simply
+    deleted, it must not be mistaken for an intentional removal: a caller that
+    cares about the distinction (see :func:`cmd_compare`) can inspect
+    ``failures`` and treat it as a hard error.
     """
-    counts: dict[str, dict[str, object]] = {}
+    counts: dict[str, dict[str, int]] = {}
     for po_file in sorted(translations_dir.glob("*/LC_MESSAGES/messages.po")):
         lang = po_file.parent.parent.name
         if lang in SKIP_LANGS:
             continue
         try:
-            stats: dict[str, object] = dict(count_stats(po_file))
-            stats.update(entry_keys(po_file))
-            counts[lang] = stats
-        except (subprocess.CalledProcessError, RuntimeError, OSError) as exc:
+            counts[lang] = count_stats(po_file)
+        except (subprocess.CalledProcessError, RuntimeError) as exc:
             # A malformed .po file (msgfmt non-zero exit, or stderr we
             # can't parse) is a real problem worth seeing, but it shouldn't
             # take the whole regression check down with it — that would
@@ -218,73 +164,42 @@ def get_counts(
     return counts
 
 
-def _normalize(entry: object) -> dict[str, object]:
-    """Coerce a baseline entry into ``{"translated", "fuzzy", *_keys}``.
+def _normalize(entry: object) -> dict[str, int]:
+    """Coerce a baseline entry into ``{"translated", "fuzzy"}``.
 
-    ``translated_keys``/``fuzzy_keys`` are the per-``msgid`` sets the check
-    keys on. They are ``None`` (not ``[]``) when the baseline predates the
-    per-entry format — an absent set means "unknown", which routes
-    :func:`cmd_compare` to the coarse aggregate fallback, whereas an empty list
-    is a known-empty set. Legacy formats — a ``{"translated", "fuzzy"}`` dict
-    with no key sets, or a bare integer translated count — are both tolerated.
+    Tolerates the legacy baseline format where each language mapped directly to
+    an integer translated count (no fuzzy data); such entries contribute a
+    fuzzy baseline of 0.
     """
     if isinstance(entry, dict):
         return {
             "translated": int(entry.get("translated", 0)),
             "fuzzy": int(entry.get("fuzzy", 0)),
-            "translated_keys": (
-                list(entry["translated_keys"]) if "translated_keys" in entry else None
-            ),
-            "fuzzy_keys": (
-                list(entry["fuzzy_keys"]) if "fuzzy_keys" in entry else None
-            ),
         }
     if isinstance(entry, int):
-        return {
-            "translated": entry,
-            "fuzzy": 0,
-            "translated_keys": None,
-            "fuzzy_keys": None,
-        }
+        return {"translated": entry, "fuzzy": 0}
     raise TypeError(f"Unsupported baseline entry: {entry!r}")
 
 
-def _key_list(stats: dict[str, object], field: str) -> Optional[list[str]]:
-    """Return ``stats[field]`` as a list of keys, or ``None`` if unavailable.
-
-    A missing or non-list value reads as "unknown" so the caller can fall back
-    to the aggregate comparison instead of treating it as an empty key set.
-    """
-    value = stats.get(field)
-    return list(value) if isinstance(value, list) else None
-
-
-def _count(stats: dict[str, object], field: str) -> int:
-    """Return ``stats[field]`` as an int count, defaulting to 0."""
-    value = stats.get(field, 0)
-    return value if isinstance(value, int) else 0
-
-
-def build_regression_report(regressions: list[tuple[str, int, int, int]]) -> str:
+def build_regression_report(regressions: list[tuple[str, int, int]]) -> str:
     """Build a markdown report for posting as a PR comment.
 
-    Each regression tuple is ``(lang, before_fuzzy, after_fuzzy, invalidated)``
-    where ``invalidated`` is the number of confirmed translations the PR turned
-    fuzzy.
+    Each regression tuple is ``(lang, before_fuzzy, after_fuzzy)``.
     """
-    rows = "\n".join(f"| `{lang}` | {n} |" for lang, _b, _a, n in regressions)
-    affected = ", ".join(f"`{lang}`" for lang, *_ in regressions)
+    rows = "\n".join(
+        f"| `{lang}` | {b} | {a} | +{a - b} |" for lang, b, a in regressions
+    )
+    affected = ", ".join(f"`{lang}`" for lang, _, _ in regressions)
     return (
         "## ⚠️ Translation Regression Detected\n\n"
         f"A source change in this PR renamed or reworded strings, invalidating "
         f"existing translations (they are now `#, fuzzy`) in {affected}. Please "
         f"resolve the affected `.po` files before merging.\n\n"
-        "_Note: neither intentionally **deleting** a translatable string nor "
-        "filling a previously-**untranslated** entry with a fuzzy guess (e.g. an "
-        "AI backfill) is a regression — only a confirmed translation that a "
-        "renamed/reworded source string turned fuzzy is flagged here._\n\n"
-        "| Language | Invalidated translations |\n"
-        "|----------|-------------------------:|\n"
+        "_Note: intentionally **deleting** a translatable string is not a "
+        "regression and is not flagged here — only translations invalidated by "
+        "a renamed/reworded source string are._\n\n"
+        "| Language | Fuzzy before | Fuzzy after | New |\n"
+        "|----------|-------------:|------------:|----:|\n"
         f"{rows}\n\n"
         "### How to fix\n\n"
         "**1. Install dependencies** (if not already set up):\n\n"
@@ -316,41 +231,6 @@ def cmd_count(translations_dir: Path) -> None:
     print(json.dumps(counts, indent=2))
 
 
-def _detect_regressions(
-    before: dict[str, dict[str, object]],
-    after: dict[str, dict[str, object]],
-) -> list[tuple[str, int, int, int]]:
-    """Return ``(lang, before_fuzzy, after_fuzzy, invalidated)`` per regressed lang.
-
-    A regression is a key in the baseline's ``translated_keys`` that is fuzzy
-    after the PR — a confirmed translation a source reword stranded. Filling a
-    previously-untranslated entry with a fuzzy guess (backfill) is therefore not
-    flagged (its key was absent from the baseline's translated set), and neither
-    is deleting a string (with ``--ignore-obsolete`` it drops, creating no
-    fuzzy). When per-entry key data is unavailable (a legacy baseline, or a
-    catalog whose key set could not be read), fall back to the coarse rule: any
-    net increase in the aggregate fuzzy count.
-    """
-    regressions: list[tuple[str, int, int, int]] = []
-    for lang, before_stats in sorted(before.items()):
-        after_stats = after.get(lang)
-        if after_stats is None:
-            # Catalog absent from `after`: an intentional deletion (a
-            # present-but-uncountable catalog was already caught by the caller).
-            continue
-        b_fuzzy = _count(before_stats, "fuzzy")
-        a_fuzzy = _count(after_stats, "fuzzy")
-        before_translated = before_stats.get("translated_keys")
-        after_fuzzy = _key_list(after_stats, "fuzzy_keys")
-        if isinstance(before_translated, list) and after_fuzzy is not None:
-            invalidated = set(after_fuzzy) & set(before_translated)
-            if invalidated:
-                regressions.append((lang, b_fuzzy, a_fuzzy, len(invalidated)))
-        elif a_fuzzy > b_fuzzy:
-            regressions.append((lang, b_fuzzy, a_fuzzy, a_fuzzy - b_fuzzy))
-    return regressions
-
-
 def cmd_compare(
     before_path: str,
     translations_dir: Path,
@@ -379,12 +259,23 @@ def cmd_compare(
         )
         sys.exit(1)
 
-    if regressions := _detect_regressions(before, after):
+    # A regression is an *increase* in fuzzy entries: the PR's source diff
+    # renamed/reworded strings, leaving their committed translations stranded.
+    # A plain drop in the translated count is NOT used — deleting a string
+    # lowers it identically to a rename but is a legitimate change, and with
+    # `pybabel update --ignore-obsolete` a deletion creates no fuzzy entry.
+    regressions: list[tuple[str, int, int]] = []
+    for lang, before_stats in sorted(before.items()):
+        after_stats = after.get(lang, {"translated": 0, "fuzzy": 0})
+        if after_stats["fuzzy"] > before_stats["fuzzy"]:
+            regressions.append((lang, before_stats["fuzzy"], after_stats["fuzzy"]))
+
+    if regressions:
         print("Translation regression detected!\n")
-        for lang, _b, _a, n in regressions:
+        for lang, b, a in regressions:
             print(
-                f"  {lang}: {n} confirmed translation(s) invalidated "
-                f"(now fuzzy) by a renamed/reworded source string"
+                f"  {lang}: {a - b} translation(s) invalidated "
+                f"(fuzzy {b} -> {a}) by a renamed/reworded source string"
             )
         print(
             "\nResolve the newly-fuzzy entries in the affected .po files "
@@ -399,16 +290,14 @@ def cmd_compare(
     # All good — print a summary so it's easy to read in CI logs.
     print("No translation regressions.\n")
     for lang in sorted(after):
-        before_stats: dict[str, object] = before.get(lang, {})
+        before_stats = before.get(lang, {"translated": 0, "fuzzy": 0})
         after_stats = after[lang]
-        b_translated = _count(before_stats, "translated")
-        a_translated = _count(after_stats, "translated")
-        b_fuzzy = _count(before_stats, "fuzzy")
-        a_fuzzy = _count(after_stats, "fuzzy")
+        t_delta = after_stats["translated"] - before_stats["translated"]
+        f_delta = after_stats["fuzzy"] - before_stats["fuzzy"]
         print(
-            f"  {lang}: translated {b_translated} -> {a_translated} "
-            f"({a_translated - b_translated:+d}), fuzzy "
-            f"{b_fuzzy} -> {a_fuzzy} ({a_fuzzy - b_fuzzy:+d})"
+            f"  {lang}: translated {before_stats['translated']} -> "
+            f"{after_stats['translated']} ({t_delta:+d}), fuzzy "
+            f"{before_stats['fuzzy']} -> {after_stats['fuzzy']} ({f_delta:+d})"
         )
 
 

superset-embedded-sdk/.nvmrc

@@ -1 +0,0 @@
-../superset-frontend/.nvmrc

superset-embedded-sdk/.nvmrc

@@ -0,0 +1 @@
+v24.16.0

superset-embedded-sdk/CONTRIBUTING.md

@@ -32,7 +32,6 @@ and therefore are not easily unit-testable. We have instead opted to test the sd
 This way, the tests can assert that the sdk actually mounts the iframe and communicates with it correctly.
 
 At time of writing, these tests are not written yet, because we haven't yet put together the demo app that they will leverage.
-
 ### Things to e2e test once we have a demo app:
 
 **happy path:**

superset-embedded-sdk/README.md

@@ -41,12 +41,12 @@ npm install --save @superset-ui/embedded-sdk
 ```
 
 ```js
-import { embedDashboard } from "@superset-ui/embedded-sdk";
+import { embedDashboard } from '@superset-ui/embedded-sdk';
 
 embedDashboard({
-  id: "abc123", // given by the Superset embedding UI
-  supersetDomain: "https://superset.example.com",
-  mountPoint: document.getElementById("my-superset-container"), // any html element that can contain an iframe
+  id: 'abc123', // given by the Superset embedding UI
+  supersetDomain: 'https://superset.example.com',
+  mountPoint: document.getElementById('my-superset-container'), // any html element that can contain an iframe
   fetchGuestToken: () => fetchGuestTokenFromBackend(),
   dashboardUiConfig: {
     // dashboard UI config: hideTitle, hideTab, hideChartControls, filters.visible, filters.expanded (optional), urlParams (optional)
@@ -55,21 +55,21 @@ embedDashboard({
       expanded: true,
     },
     urlParams: {
-      foo: "value1",
-      bar: "value2",
+      foo: 'value1',
+      bar: 'value2',
       // themeMode: 'dark', // set the initial theme: 'dark' | 'system' | 'default' (default: 'default')
       // ...
     },
   },
   // optional additional iframe sandbox attributes
   iframeSandboxExtras: [
-    "allow-top-navigation",
-    "allow-popups-to-escape-sandbox",
+    'allow-top-navigation',
+    'allow-popups-to-escape-sandbox',
   ],
   // optional Permissions Policy features
-  iframeAllowExtras: ["clipboard-write", "fullscreen"],
+  iframeAllowExtras: ['clipboard-write', 'fullscreen'],
   // optional config to enforce a particular referrerPolicy
-  referrerPolicy: "same-origin",
+  referrerPolicy: 'same-origin',
   // optional callback to customize permalink URLs
   resolvePermalinkUrl: ({ key }) => `https://my-app.com/analytics/share/${key}`,
 });
@@ -163,13 +163,13 @@ Use the `themeMode` URL parameter to control the embedded dashboard's initial co
 
 ```js
 embedDashboard({
-  id: "abc123",
-  supersetDomain: "https://superset.example.com",
-  mountPoint: document.getElementById("my-superset-container"),
+  id: 'abc123',
+  supersetDomain: 'https://superset.example.com',
+  mountPoint: document.getElementById('my-superset-container'),
   fetchGuestToken: () => fetchGuestTokenFromBackend(),
   dashboardUiConfig: {
     urlParams: {
-      themeMode: "dark", // 'dark' | 'system' | 'default' (default: 'default')
+      themeMode: 'dark', // 'dark' | 'system' | 'default' (default: 'default')
     },
   },
 });
@@ -193,7 +193,7 @@ To pass additional sandbox attributes you can use `iframeSandboxExtras`:
 
 ```js
 // optional additional iframe sandbox attributes
-iframeSandboxExtras: ["allow-top-navigation", "allow-popups-to-escape-sandbox"];
+iframeSandboxExtras: ['allow-top-navigation', 'allow-popups-to-escape-sandbox'];
 ```
 
 ### Permissions Policy
@@ -202,7 +202,7 @@ To enable specific browser features within the embedded iframe, use `iframeAllow
 
 ```js
 // optional Permissions Policy features
-iframeAllowExtras: ["clipboard-write", "fullscreen"];
+iframeAllowExtras: ['clipboard-write', 'fullscreen'];
 ```
 
 Common permissions you might need:
@@ -225,9 +225,9 @@ When users click share buttons inside an embedded dashboard, Superset generates
 
 ```js
 embedDashboard({
-  id: "abc123",
-  supersetDomain: "https://superset.example.com",
-  mountPoint: document.getElementById("my-superset-container"),
+  id: 'abc123',
+  supersetDomain: 'https://superset.example.com',
+  mountPoint: document.getElementById('my-superset-container'),
   fetchGuestToken: () => fetchGuestTokenFromBackend(),
 
   // Customize permalink URLs
@@ -245,9 +245,9 @@ To restore the dashboard state from a permalink in your app:
 const permalinkKey = routeParams.key;
 
 embedDashboard({
-  id: "abc123",
-  supersetDomain: "https://superset.example.com",
-  mountPoint: document.getElementById("my-superset-container"),
+  id: 'abc123',
+  supersetDomain: 'https://superset.example.com',
+  mountPoint: document.getElementById('my-superset-container'),
   fetchGuestToken: () => fetchGuestTokenFromBackend(),
   resolvePermalinkUrl: ({ key }) => `https://my-app.com/analytics/share/${key}`,
   dashboardUiConfig: {

superset-embedded-sdk/babel.config.js

@@ -18,7 +18,9 @@
  */
 
 module.exports = {
-  presets: ["@babel/preset-typescript", "@babel/preset-env"],
+  presets: [
+    "@babel/preset-typescript",
+    "@babel/preset-env"
+  ],
   sourceMaps: true,
-  ignore: ["**/*.test.ts"],
 };