Bump cssbox to 5.0.2 for dos bugfix

I don't think we are susceptible to this, but the scanners pick it up
and there's finally a release.

This was merged in https://github.com/metabase/metabase/pull/50642 to
master and will target 53. There's lots of other stuff in there so I'm
opening this smaller, targeted change against the 52 branch

.clj-kondo/config.edn

@@ -128,10 +128,12 @@
      clojure.core.async/to-chan!
      clojure.core.async/to-chan!!
      metabase.channel.core/send!
-     metabase.models.notification/create-notification!
      metabase.driver.sql-jdbc.execute/execute-prepared-statement!
+     metabase.models.notification/create-notification!
      metabase.pulse.send/send-pulse!
      metabase.query-processor.store/store-database!
+     ;; Safe in tests, where we typically use a private, temporary index per thread.
+     metabase.search.core/reindex!
      metabase.util/run-count!
      next.jdbc/execute!}}
 
@@ -342,9 +344,8 @@
                                      metabase.query-analysis.failure-map}
     metabase.related               #{metabase.related}
     metabase.sample-data           #{metabase.sample-data}
-    metabase.search                #{metabase.search
-                                     ;; deprecating naked metabase.search namespace in favor of this.
-                                     metabase.search.core
+    metabase.search                #{metabase.search.core
+                                     ;; Need to expose this submodule, to break circular dependencies with models.
                                      metabase.search.spec}
     metabase.server                #{metabase.server
                                      metabase.server.handler

.clj-kondo/src/hooks/metabase/models/setting.clj

@@ -21,6 +21,7 @@
      database-enable-actions
      deprecation-notice-version
      dismissed-custom-dashboard-toast
+     dismissed-onboarding-sidebar-link
      email-configured?
      email-from-address
      email-from-name
@@ -161,6 +162,7 @@
      token-features
      token-status
      toucan-name
+     trial-banner-dismissal-timestamp
      uncached-setting
      user-visibility
      version

.github/actions/build-e2e-matrix/action.yml

@@ -1,71 +0,0 @@
-name: Build E2E Matrix
-description: Build and output a custom matrix for E2E tests.
-
-outputs:
-  matrix:
-    description: Parameterized matrix in JSON format
-    value: ${{ steps.matrix.outputs.result }}
-
-runs:
-  using: "composite"
-  steps:
-    - uses: actions/github-script@v7
-      id: matrix
-      with:
-        script: | # js
-          const java = 21;
-
-          const defaultRunner = "ubuntu-22.04";
-
-          const defaultOptions = {
-            "java-version": java,
-            runner: defaultRunner,
-            edition: "ee",
-            context: "folder"
-          };
-
-          const testSets = [
-            ["actions", {} ],
-            ["admin", {} ],
-            ["admin-2", {} ],
-            ["binning", {} ],
-            ["collections", {} ],
-            ["custom-column", {} ],
-            ["dashboard", {} ],
-            ["dashboard-cards", {} ],
-            ["dashboard-filters", {} ],
-            ["dashboard-filters-2", {} ],
-            ["embedding", {} ],
-            ["embedding-sdk", { context: "embedding-sdk" } ],
-            ["filters", {} ],
-            ["filters-reproductions", {}],
-            ["joins", {} ],
-            ["metrics", {} ],
-            ["models", {} ],
-            ["native", {} ],
-            ["native-filters", {} ],
-            ["onboarding", {} ],
-            ["organization", {} ],
-            ["permissions", {} ],
-            ["question", {} ],
-            ["question-reproductions", {} ],
-            ["search", {}],
-            ["sharing", {} ],
-            ["visualizations-charts", {} ],
-            ["visualizations-tabular", {} ],
-            ["oss-subset", { edition: 'oss', context: "special" } ],
-            ["slow", { context: "special" } ],
-            ["flaky", { context: "special" } ],
-            ["mongo", { context: "qa-database" } ],
-          ];
-
-          const config = testSets.map(([name, specialOptions]) => {
-            return {
-              ...defaultOptions,
-              ...specialOptions,
-              name,
-            }
-          });
-
-          const matrix = { include: config };
-          return matrix;

.github/actions/e2e-prepare-containers/action.yml

@@ -90,7 +90,7 @@ runs:
 
         if ${{ inputs.webhook }}; then
           echo -e "${Y}Starting webhook test container..." &&
-          docker run -d -p 9080:8080/tcp tarampampam/webhook-tester serve --create-session 00000000-0000-0000-0000-000000000000 &&
+          docker run -d -p 9080:8080/tcp tarampampam/webhook-tester:1.1.0 serve --create-session 00000000-0000-0000-0000-000000000000 &&
           while ! nc -z localhost 9080; do sleep 1; done &&
           echo -e "${G}Webhook tester is up and running!"
         fi

.github/auto_request_review.yml

@@ -5,9 +5,9 @@
 files:
   # migrations related files
   'resources/migrations/**':
-    - team:core-backend-components
+    - team:core-workflows
   'src/metabase/db/custom_migrations.clj':
-    - team:core-backend-components
+    - team:core-workflows
 
 options:
   ignore_draft: true

.github/team.json

@@ -12,7 +12,10 @@
         "metamben",
         "lbrdnk",
         "appleby",
-        "uladzimirdev"
+        "uladzimirdev",
+        "wzimrin",
+        "ericnormand",
+        "lorem--ipsum"
       ]
     },
     {
@@ -24,16 +27,17 @@
       "name": "Embedding",
       "label": ".Team/Embedding",
       "projectUrl": "https://github.com/orgs/metabase/projects/88/views/1",
-      "members": ["WiNloSt", "deniskaber", "oisincoveney", "npretto", "heypoom"]
+      "members": ["WiNloSt", "oisincoveney", "npretto", "heypoom"]
     },
     {
-      "name": "BEC",
-      "label": ".Team/BackendComponents",
+      "name": "Workflows",
+      "label": ".Team/Workflows",
       "projectUrl": "https://github.com/orgs/metabase/projects/50/views/1",
       "members": [
         "qnkhuat",
         "piranha",
-        "crisptrutski"
+        "crisptrutski",
+        "deniskaber"
       ]
     },
     {

.github/workflows/backend.yml

@@ -154,6 +154,7 @@ jobs:
         uses: ./.github/actions/prepare-backend
         with:
           m2-cache-key: be-tests
+          java-version: "${{ matrix.java-version }}"
       # Depending on which files changed, we might either have to build static-viz
       # from scratch or download the previously built artifact
       - name: Build static-viz frontend
@@ -194,9 +195,9 @@ jobs:
           fail-on-error: false
 
   be-tests-stub:
-    needs: [be-tests]
+    needs: [files-changed, static-viz-files-changed, be-tests]
     if: |
-      !cancelled() &&
+      always() &&
       github.event.pull_request.draft == false && needs.be-tests.result == 'skipped'
     runs-on: ubuntu-22.04
     name: be-tests-java-${{ matrix.java-version }}-${{ matrix.edition }}

.github/workflows/doc-md-links.yml

@@ -1,18 +0,0 @@
-name: Lint doc Markdown links
-
-on:
-  push:
-    paths:
-      - docs/**
-  pull_request:
-    paths:
-      - docs/**
-jobs:
-  markdown-link-check:
-    runs-on: ubuntu-22.04
-    steps:
-      - uses: actions/checkout@v4
-      - name: Prepare front-end environment
-        uses: ./.github/actions/prepare-frontend
-      - name: Lint doc links
-        run: yarn run docs-lint-links

.github/workflows/drivers.yml

@@ -144,13 +144,16 @@ jobs:
       MB_DATABRICKS_TEST_HTTP_PATH: ${{ secrets.MB_DATABRICKS_JDBC_TEST_HTTP_PATH }}
       MB_DATABRICKS_TEST_TOKEN: ${{ secrets.MB_DATABRICKS_JDBC_TEST_TOKEN }}
       MB_DATABRICKS_TEST_CATALOG: 'metabase_ci'
+      MB_DATABRICKS_TEST_CLIENT_ID: ${{ secrets.MB_DATABRICKS_JDBC_TEST_CLIENT_ID }}
+      MB_DATABRICKS_TEST_OAUTH_SECRET: ${{ secrets.MB_DATABRICKS_JDBC_TEST_OAUTH_SECRET }}
     steps:
     - uses: actions/checkout@v4
     - name: Test Databricks driver
       uses: ./.github/actions/test-driver
       with:
         junit-name: 'be-tests-databricks-ee'
-        test-args: ":exclude-tags '[:mb/once]'"
+        test-args: >-
+          :only-tags [:mb/driver-tests]
     - name: Upload Test Results
       uses: ./.github/actions/upload-test-results
       if: always()

.github/workflows/e2e-component-tests-embedding-sdk-cross-version.yml

@@ -0,0 +1,250 @@
+name: E2E Cross-version Component Tests for Embedding SDK
+
+on:
+  push:
+    branches:
+      - "release-**"
+  pull_request:
+    types: [opened, synchronize, reopened, ready_for_review]
+    branches:
+      - "release-**"
+
+concurrency:
+  group: ${{ github.workflow }}-${{ github.head_ref && github.ref || github.run_id }}
+  cancel-in-progress: true
+
+jobs:
+  files-changed:
+    name: Check which files changed
+    runs-on: ubuntu-22.04
+    timeout-minutes: 3
+    outputs:
+      e2e_all: ${{ steps.changes.outputs.e2e_all }}
+    steps:
+      - uses: actions/checkout@v4
+      - name: Test which files changed
+        uses: dorny/paths-filter@v3.0.0
+        id: changes
+        with:
+          token: ${{ github.token }}
+          filters: .github/file-paths.yaml
+
+  # if this is a test on a release branch, we need to check the build requirements
+  get-build-requirements:
+    if: |
+      !cancelled()
+    runs-on: ubuntu-22.04
+    timeout-minutes: 10
+    outputs:
+      java_version: ${{ fromJson(steps.dependencies.outputs.result).java_version }}
+      node_version: ${{ fromJson(steps.dependencies.outputs.result).node_version }}
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          sparse-checkout: release
+      - name: Prepare build scripts
+        run: cd ${{ github.workspace }}/release && yarn && yarn build
+      - name: Get build dependencies
+        uses: actions/github-script@v7
+        id: dependencies
+        with:
+          script: | # js
+            const {
+              getBuildRequirements,
+              getVersionFromReleaseBranch,
+            } = require('${{ github.workspace }}/release/dist/index.cjs');
+            const targetBranchName = '${{ github.base_ref || github.ref }}';
+
+            const version = getVersionFromReleaseBranch(targetBranchName);
+            const requirements = getBuildRequirements(version);
+
+            return {
+              java_version: requirements.java,
+              node_version: requirements.node,
+            };
+
+  build:
+    needs: [files-changed, get-build-requirements]
+    if: |
+      !cancelled() &&
+      github.event.pull_request.draft == false
+    runs-on: ubuntu-22.04
+    timeout-minutes: 25
+    env:
+      MB_EDITION: ee
+      INTERACTIVE: false
+      # make sure that builds on release branches get licenses, because we use them for releases
+      SKIP_LICENSES: ${{ github.event_name == 'pull_request' }}
+    steps:
+      - uses: actions/checkout@v4
+      - name: Prepare front-end environment
+        uses: ./.github/actions/prepare-frontend
+        with:
+          node-version: "${{ needs.get-build-requirements.outputs.node_version }}"
+      - name: Prepare back-end environment
+        uses: ./.github/actions/prepare-backend
+        with:
+          m2-cache-key: uberjar
+          java-version: "${{ needs.get-build-requirements.outputs.java_version || 11 }}"
+
+      - name: Build uberjar with ./bin/build.sh
+        run: ./bin/build.sh
+
+      - name: Prepare uberjar artifact
+        uses: ./.github/actions/prepare-uberjar-artifact
+        with:
+          name: metabase-ee-${{ github.event.pull_request.head.sha || github.sha }}-uberjar
+
+  resolve-sdk-version:
+    if: |
+      !cancelled()
+    runs-on: ubuntu-22.04
+    timeout-minutes: 10
+    outputs:
+      sdk_version: ${{ fromJson(steps.dependencies.outputs.result).sdk_version }}
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          sparse-checkout: release
+      - name: Prepare build scripts
+        run: cd ${{ github.workspace }}/release && yarn && yarn build
+      - name: Get latest SDK release for this branch
+        uses: actions/github-script@v7
+        id: dependencies
+        with:
+          script: | # js
+            const { getSdkVersionFromReleaseBranchName } = require('${{ github.workspace }}/release/dist/index.cjs');
+            const branchName = '${{ github.base_ref || github.ref }}';
+
+            const sdk_version = await getSdkVersionFromReleaseBranchName({
+              github,
+              owner: context.repo.owner,
+              repo: context.repo.repo,
+              branchName,
+            });
+
+            return {
+              sdk_version,
+            };
+
+  e2e-tests:
+    needs: [get-build-requirements, build, resolve-sdk-version]
+    if: |
+      !cancelled() && needs.build.result == 'success'
+    runs-on: ubuntu-22.04
+    timeout-minutes: 45
+    name: e2e-tests-embedding-sdk
+    env:
+      MB_EDITION: ee
+      DISPLAY: ""
+      # Any env starting with `CYPRESS_` will be available to all Cypress tests via `Cypress.env()`
+      # Example: you can get `CYPRESS_FOO` with `Cypress.env("FOO")`
+      CYPRESS_ALL_FEATURES_TOKEN: ${{ secrets.ENTERPRISE_TOKEN }}
+      CYPRESS_NO_FEATURES_TOKEN: ${{ secrets.E2E_STARTER_TOKEN }}
+      CYPRESS_PULL_REQUEST_ID: ${{ github.event.pull_request.number || '' }}
+      COMMIT_INFO_MESSAGE: ${{ github.event.pull_request.title || github.event.head_commit.message || github.event.head.sha }}
+      TZ: US/Pacific # to make node match the instance tz
+      CYPRESS_CI: true
+
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Prepare Docker containers
+        uses: ./.github/actions/e2e-prepare-containers
+        with:
+          username: ${{ secrets.DOCKERHUB_USERNAME }}
+          password: ${{ secrets.DOCKERHUB_TOKEN }}
+
+      # Needed to omit newly added tests for functionality that is not yet released
+      - name: Sparse checkout tests from SDK release commit
+        uses: actions/checkout@v4
+        with:
+          ref: embedding-sdk-${{ needs.resolve-sdk-version.outputs.sdk_version }}
+          path: sdk-release-e2e
+          sparse-checkout: e2e
+
+      - name: Move tests from the release commit into the repo
+        run: |
+          rm -rf ./e2e/support/helpers/*
+          mv ./sdk-release-e2e/e2e/support/helpers/* ./e2e/support/helpers
+          rm -rf ./e2e/test-component/*
+          mv ./sdk-release-e2e/e2e/test-component/* ./e2e/test-component
+        shell: bash
+
+      - name: Retrieve uberjar artifact for ee
+        uses: actions/download-artifact@v4
+        with:
+          name: metabase-ee-${{ github.event.pull_request.head.sha || github.sha }}-uberjar
+
+      - name: Get the version info
+        run: |
+          jar xf target/uberjar/metabase.jar version.properties
+          mv version.properties resources/
+
+      - name: Prepare front-end environment
+        uses: ./.github/actions/prepare-frontend
+
+      - name: Prepare JDK ${{ needs.get-build-requirements.outputs.java_version || 11 }}
+        uses: actions/setup-java@v4
+        with:
+          java-version: ${{ needs.get-build-requirements.outputs.java_version || 11 }}
+          distribution: "temurin"
+
+      - name: Prepare Cypress environment
+        id: cypress-prep
+        uses: ./.github/actions/prepare-cypress
+
+      - name: Install Embedding SDK package v${{ needs.resolve-sdk-version.outputs.sdk_version }}
+        run: yarn add @metabase/embedding-sdk-react@${{ needs.resolve-sdk-version.outputs.sdk_version }}
+
+      - name: Run E2E tests for Embedding SDK
+        run: yarn run test-cypress-run-component-sdk --browser ${{ steps.cypress-prep.outputs.chrome-path }}
+
+      - name: Upload Test Results
+        uses: ./.github/actions/upload-test-results
+        if: always()
+        with:
+          input-path: ./target/junit
+          output-name: e2e-embedding-sdk
+          bucket: ${{ vars.AWS_S3_TEST_RESULTS_BUCKET }}
+          aws-access-key-id: ${{ secrets.AWS_TEST_RESULTS_ACCESS_KEY_ID }}
+          aws-secret-access-key: ${{ secrets.AWS_TEST_RESULTS_SECRET_ACCESS_KEY }}
+          aws-region: ${{ vars.AWS_REGION }}
+          trunk-api-token: ${{ secrets.TRUNK_API_TOKEN }}
+
+      - name: Upload Cypress Artifacts upon failure
+        uses: actions/upload-artifact@v4
+        if: failure()
+        with:
+          name: cypress-recording-embedding-sdk-cross-version
+          path: |
+            ./cypress
+            ./logs/test.log
+          if-no-files-found: ignore
+
+      - name: Publish Summary
+        if: failure()
+        uses: actions/github-script@v7
+        with:
+          script: | #js
+            const {
+               parseReport,
+               formatSummary
+             } = require("./.github/scripts/handle-mochawesome-report.js");
+
+             const report = parseReport();
+             const summary = formatSummary(report);
+
+             await core.summary.addRaw(summary).write();
+
+  e2e-tests-skipped-stub:
+    needs: [e2e-tests]
+    if: |
+      !cancelled() &&
+      needs.e2e-tests.result == 'skipped'
+    runs-on: ubuntu-22.04
+    timeout-minutes: 5
+    name: e2e-component-tests-embedding-sdk-cross-version
+    steps:
+      - run: |
+          echo "Didn't run due to conditional filtering"

.github/workflows/e2e-component-tests-embedding-sdk.yml

@@ -32,7 +32,7 @@ jobs:
   get-build-requirements:
     if: |
       !cancelled() &&
-      contains(github.ref, 'release-x')
+      contains(github.base_ref || github.ref, 'release-x')
     runs-on: ubuntu-22.04
     timeout-minutes: 10
     outputs:
@@ -53,7 +53,7 @@ jobs:
               getBuildRequirements,
               getVersionFromReleaseBranch,
             } = require('${{ github.workspace }}/release/dist/index.cjs');
-            const targetBranchName = '${{ github.base_ref }}';
+            const targetBranchName = '${{ github.base_ref || github.ref }}';
 
             const version = getVersionFromReleaseBranch(targetBranchName);
             const requirements = getBuildRequirements(version);

.github/workflows/e2e-matrix-builder.yml

@@ -0,0 +1,97 @@
+name: E2E Matrix Builder
+
+on:
+  workflow_call:
+    inputs:
+      chunks:
+        required: true
+        type: number
+        default: 30
+    outputs:
+      matrix:
+        value: ${{ jobs.build-matrix.outputs.matrix }}
+
+jobs:
+  build-matrix:
+    runs-on: ubuntu-22.04
+    timeout-minutes: 5
+    outputs:
+      matrix: ${{ steps.matrix.outputs.config }}
+    steps:
+      - uses: actions/setup-node@v3
+        with:
+          node-version: '20.x'
+      - uses: actions/checkout@v4
+        with:
+          sparse-checkout: e2e
+      - name: get test file names
+        id: test-files
+        shell: bash
+        run: |
+          echo "::set-output name=filenames::$(find e2e/test/scenarios -name '*.cy.spec.*' | tr '\n' ',')"
+      - uses: actions/github-script@v7
+        id: matrix
+        with:
+          script: | # js
+            const chunk = (arr, size) => {
+              const chunks = [];
+              const n = Math.ceil(arr.length / size);
+              for (let i = 0; i < n; i++) {
+                chunks.push(arr.slice(i * size, (i + 1) * size));
+              }
+              return chunks;
+            };
+
+            const java = 21;
+            const defaultRunner = "ubuntu-22.04";
+
+            // these are special and shouldn't be chunked out arbitrarily
+            const blacklist = [
+              "/embedding-sdk/",
+              "/cross-version/"
+            ];
+
+            const defaultOptions = {
+              "java-version": java,
+              runner: defaultRunner,
+              specs: "./e2e/test/scenarios/**/*.cy.spec.*",
+              edition: "ee",
+            };
+
+            const specialTests = [
+              { name: "embedding-sdk", specs: "./e2e/test/scenarios/embedding-sdk/**.cy.spec.*" },
+              { name: "oss-subset", edition: 'oss', tags: "@OSS" },
+              { name: "slow", tags: "@slow+-@flaky" },
+              { name: "mongo", tags: "@mongo" },
+            ];
+
+            const fileNames = "${{ steps.test-files.outputs.filenames }}"
+              .split(",")
+              .filter(Boolean)
+              .filter(testPath => !blacklist.some(blacklisted => testPath.includes(blacklisted)));
+
+            const fileCount = fileNames.length;
+
+            // subtract the special tests since they all get their own runners
+            const chunkSize = fileCount / (Number('${{ inputs.chunks }}') - specialTests.length);
+
+
+
+            const chunkedFiles = chunk(fileNames, chunkSize);
+
+            const regularTests = chunkedFiles.map((files, index) => ({
+              name: `e2e-group-${index + 1}`,
+              specs: files.join(","),
+              tags: '',
+            }));
+
+            const testSets = [...regularTests, ...specialTests];
+
+            const config = testSets.map((options) => ({
+              ...defaultOptions,
+              ...options,
+            }));
+
+            console.log("matrix config", config);
+
+            core.setOutput("config", JSON.stringify({ include: config }));

.github/workflows/e2e-test.yml

@@ -0,0 +1,151 @@
+name: E2E Test
+run-name: E2E Test - ${{ inputs.name }}
+
+on:
+  workflow_call:
+    inputs:
+      name:
+        required: true
+        type: string
+      edition: # oss | ee
+        required: false
+        type: string
+        default: ee
+      specs:
+        required: false
+        default: ./e2e/test/scenarios/**/*.cy.spec.*
+        type: string
+      tags:
+        required: false
+        type: string
+      runner:
+        required: false
+        type: string
+        default: ubuntu-22.04
+
+jobs:
+  e2e-tests:
+    runs-on: ${{ inputs.runner }}
+    timeout-minutes: 45
+    name: e2e-tests-${{ inputs.name }}-${{ inputs.edition }}
+    env:
+      MB_EDITION: ${{ inputs.edition }}
+      DISPLAY: ""
+      QA_DB_ENABLED: true
+      # Any env starting with `CYPRESS_` will be available to all Cypress tests via `Cypress.env()`
+      # Example: you can get `CYPRESS_FOO` with `Cypress.env("FOO")`
+      CYPRESS_ALL_FEATURES_TOKEN: ${{ secrets.ENTERPRISE_TOKEN }}
+      CYPRESS_NO_FEATURES_TOKEN: ${{ secrets.E2E_STARTER_TOKEN }}
+      CYPRESS_PULL_REQUEST_ID: ${{ github.event.pull_request.number || '' }}
+      COMMIT_INFO_MESSAGE: ${{ github.event.pull_request.title || github.event.head_commit.message || github.event.head.sha }}
+      MB_SNOWPLOW_AVAILABLE: true
+      MB_SNOWPLOW_URL: "http://localhost:9090" # Snowplow micro
+      TZ: US/Pacific # to make node match the instance tz
+      CYPRESS_CI: true
+      CYPRESS_QA_DB_MONGO: ${{ inputs.name == 'mongo' }}
+      CYPRESS_IS_EMBEDDING_SDK: ${{ inputs.name == 'embedding-sdk' }}
+      mongo: ${{ inputs.name == 'mongo' }}
+      postgres: ${{ inputs.name != 'mongo' }}
+      mysql: ${{ inputs.name != 'mongo' }}
+      openldap: ${{ contains(inputs.specs, 'ldap') }}
+      maildev: true
+      webhook: true
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Prepare Docker containers
+        uses: ./.github/actions/e2e-prepare-containers
+        with:
+          username: ${{ secrets.DOCKERHUB_USERNAME }}
+          password: ${{ secrets.DOCKERHUB_TOKEN }}
+          maildev: true
+          openldap: ${{ env.openldap }}
+          postgres: ${{ env.postgres }}
+          mysql: ${{ env.mysql }}
+          mongo: ${{ env.mongo }}
+          webhook: ${{ env.webhook }}
+
+      - name: Run Embedding SDK Storybook
+        if: inputs.name == 'embedding-sdk'
+        uses: ./.github/actions/run-embedding-sdk-storybook
+
+      - name: Retrieve uberjar artifact for ${{ inputs.edition }}
+        uses: actions/download-artifact@v4
+        with:
+          name: metabase-${{ inputs.edition }}-${{ github.event.pull_request.head.sha || github.sha }}-uberjar
+
+      - name: Get the version info
+        run: |
+          jar xf target/uberjar/metabase.jar version.properties
+          mv version.properties resources/
+
+      - name: Prepare front-end environment
+        uses: ./.github/actions/prepare-frontend
+
+      - name: Prepare JDK 21
+        uses: actions/setup-java@v4
+        with:
+          java-version: 21
+          distribution: "temurin"
+
+      - name: Prepare Cypress environment
+        id: cypress-prep
+        uses: ./.github/actions/prepare-cypress
+
+      - name: Run Snowplow micro
+        uses: ./.github/actions/run-snowplow-micro
+
+      - name: Run EE Cypress tests on ${{ inputs.name }}
+        if: ${{ !inputs.tags }}
+        shell: bash
+        run: |
+          yarn run test-cypress-run \
+          --env grepTags="-@slow+-@mongo+-@flaky+-@OSS --@quarantine",grepOmitFiltered=true \
+          --spec '${{ inputs.specs }}' \
+          --browser ${{ steps.cypress-prep.outputs.chrome-path }}
+
+      - name: Run Tagged EE Cypress tests on ${{ inputs.name }}
+        if: ${{ inputs.tags }}
+        shell: bash
+        run: |
+          yarn run test-cypress-run \
+          --env grepTags="${{inputs.tags}} --@quarantine",grepOmitFiltered=true \
+          --spec '${{ inputs.specs }}' \
+          --browser ${{ steps.cypress-prep.outputs.chrome-path }}
+
+      - name: Upload Test Results
+        uses: ./.github/actions/upload-test-results
+        if: always()
+        with:
+          input-path: ./target/junit
+          output-name: e2e-${{ inputs.name }}
+          bucket: ${{ vars.AWS_S3_TEST_RESULTS_BUCKET }}
+          aws-access-key-id: ${{ secrets.AWS_TEST_RESULTS_ACCESS_KEY_ID }}
+          aws-secret-access-key: ${{ secrets.AWS_TEST_RESULTS_SECRET_ACCESS_KEY }}
+          aws-region: ${{ vars.AWS_REGION }}
+          trunk-api-token: ${{ secrets.TRUNK_API_TOKEN }}
+
+      - name: Upload Cypress Artifacts upon failure
+        uses: actions/upload-artifact@v4
+        if: failure()
+        with:
+          name: cypress-recording-${{ inputs.name }}-${{ inputs.edition }}
+          path: |
+            ./cypress
+            ./logs/test.log
+          if-no-files-found: ignore
+
+      - name: Publish Summary
+        if: failure()
+        uses: actions/github-script@v7
+        with:
+          script: | #js
+            const {
+               parseReport,
+               formatSummary
+             } = require("./.github/scripts/handle-mochawesome-report.js");
+
+             const report = parseReport();
+             const summary = formatSummary(report);
+
+             await core.summary.addRaw(summary).write();

.github/workflows/e2e-tests.yml

@@ -29,15 +29,9 @@ jobs:
           filters: .github/file-paths.yaml
 
   e2e-matrix-builder:
-    runs-on: ubuntu-22.04
-    timeout-minutes: 5
-    outputs:
-      matrix: ${{ steps.e2e-matrix.outputs.matrix }}
-    steps:
-      - uses: actions/checkout@v4
-      - name: Generate matrix for E2E tests
-        id: e2e-matrix
-        uses: ./.github/actions/build-e2e-matrix
+    uses: ./.github/workflows/e2e-matrix-builder.yml
+    with:
+      chunks: 50
 
   # if this is a test on a release branch, we need to check the build requirements
   get-build-requirements:
@@ -70,12 +64,12 @@ jobs:
               node_version: requirements.node,
             };
 
+
   build:
-    needs: [files-changed, e2e-matrix-builder, get-build-requirements]
+    needs: [files-changed, get-build-requirements]
     if: |
       !cancelled() &&
       github.event.pull_request.draft == false &&
-      needs.e2e-matrix-builder.result == 'success' &&
       needs.files-changed.outputs.e2e_all == 'true'
     runs-on: ubuntu-22.04
     timeout-minutes: 25
@@ -108,179 +102,58 @@ jobs:
           name: metabase-${{ matrix.edition }}-${{ github.event.pull_request.head.sha || github.sha }}-uberjar
 
   e2e-tests:
+    name: ${{ matrix.name }}-${{ matrix.edition }}
+    uses: ./.github/workflows/e2e-test.yml
     needs: [build, e2e-matrix-builder]
     if: |
       !cancelled() && needs.build.result == 'success'
-    runs-on: ${{ matrix.runner }}
-    timeout-minutes: 45
-    name: e2e-tests-${{ matrix.name }}-${{ matrix.edition }}
-    env:
-      MB_EDITION: ${{ matrix.edition }}
-      DISPLAY: ""
-      QA_DB_ENABLED: true
-      # Any env starting with `CYPRESS_` will be available to all Cypress tests via `Cypress.env()`
-      # Example: you can get `CYPRESS_FOO` with `Cypress.env("FOO")`
-      CYPRESS_ALL_FEATURES_TOKEN: ${{ secrets.ENTERPRISE_TOKEN }}
-      CYPRESS_NO_FEATURES_TOKEN: ${{ secrets.E2E_STARTER_TOKEN }}
-      CYPRESS_PULL_REQUEST_ID: ${{ github.event.pull_request.number || '' }}
-      COMMIT_INFO_MESSAGE: ${{ github.event.pull_request.title || github.event.head_commit.message || github.event.head.sha }}
-      MB_SNOWPLOW_AVAILABLE: true
-      MB_SNOWPLOW_URL: "http://localhost:9090" # Snowplow micro
-      TZ: US/Pacific # to make node match the instance tz
-      CYPRESS_CI: true
     strategy:
       fail-fast: false
-      matrix: ${{ fromJSON(needs.e2e-matrix-builder.outputs.matrix) }}
+      matrix: ${{ fromJson(needs.e2e-matrix-builder.outputs.matrix) }}
+    secrets: inherit
+    with:
+      name: ${{ matrix.name }}
+      edition: ${{ matrix.edition }}
+      specs: ${{ matrix.specs }}
+      tags: ${{ matrix.tags }}
+      runner: ${{ matrix.runner }}
 
-    steps:
-      - uses: actions/checkout@v4
-
-      - name: Prepare Docker containers
-        uses: ./.github/actions/e2e-prepare-containers
-        with:
-          username: ${{ secrets.DOCKERHUB_USERNAME }}
-          password: ${{ secrets.DOCKERHUB_TOKEN }}
-          maildev: true
-          openldap: ${{ startsWith(matrix.name, 'admin') }}
-          postgres: ${{ matrix.name != 'mongo'}}
-          mysql: ${{ matrix.name != 'mongo'}}
-          mongo: ${{ matrix.name == 'mongo'}}
-          webhook: true
-
-      - name: Retrieve uberjar artifact for ${{ matrix.edition }}
-        uses: actions/download-artifact@v4
-        with:
-          name: metabase-${{ matrix.edition }}-${{ github.event.pull_request.head.sha || github.sha }}-uberjar
-
-      - name: Get the version info
-        run: |
-          jar xf target/uberjar/metabase.jar version.properties
-          mv version.properties resources/
-
-      - name: Prepare front-end environment
-        uses: ./.github/actions/prepare-frontend
-
-      - name: Prepare JDK ${{ matrix.java-version }}
-        uses: actions/setup-java@v4
-        with:
-          java-version: ${{ matrix.java-version }}
-          distribution: "temurin"
-
-      - name: Prepare Cypress environment
-        id: cypress-prep
-        uses: ./.github/actions/prepare-cypress
-
-      - name: Run Snowplow micro
-        uses: ./.github/actions/run-snowplow-micro
-
-      - name: Run OSS-specific Cypress tests
-        if: matrix.edition == 'oss' && github.event_name != 'schedule'
-        run: |
-          yarn run test-cypress-run \
-          --env grepTags=@OSS,grepOmitFiltered=true \
-          --spec './e2e/test/scenarios/**/*.cy.spec.(js|ts)' \
-          --browser ${{ steps.cypress-prep.outputs.chrome-path }}
-
-      - name: Run slow and resource-intensive Cypress tests
-        if: matrix.name == 'slow' && github.event_name != 'schedule'
-        run: |
-          yarn run test-cypress-run \
-          --env grepTags="@slow",grepOmitFiltered=true \
-          --spec './e2e/test/scenarios/**/*.cy.spec.(js|ts)' \
-          --browser ${{ steps.cypress-prep.outputs.chrome-path }}
-
-      - name: Run Flaky Cypress tests
-        if: matrix.name == 'flaky' && github.event_name != 'schedule'
-        run: |
-          yarn run test-cypress-run \
-          --env grepTags="@flaky --@quarantine",grepOmitFiltered=true \
-          --spec './e2e/test/scenarios/**/*.cy.spec.(js|ts)' \
-          --browser ${{ steps.cypress-prep.outputs.chrome-path }}
-
-      - name: Run EE Cypress tests on ${{ matrix.name }}
-        if: matrix.context == 'folder' && github.event_name != 'schedule'
-        run: |
-          yarn run test-cypress-run \
-          --env grepTags="-@slow+-@mongo+-@flaky --@quarantine",grepOmitFiltered=true \
-          --folder ${{ matrix.name }} \
-          --browser ${{ steps.cypress-prep.outputs.chrome-path }}
-
-      - name: Run E2E tests that depend on Mongo
-        if: matrix.name == 'mongo'
-        run: |
-          yarn run test-cypress-run \
-          --env grepTags="@mongo --@quarantine",grepOmitFiltered=true \
-          --spec './e2e/test/scenarios/**/*.cy.spec.(js|ts)' \
-          --browser ${{ steps.cypress-prep.outputs.chrome-path }}
-        env:
-          CYPRESS_QA_DB_MONGO: true
-
-      - name: Run Embedding SDK Storybook
-        if: matrix.context == 'embedding-sdk' && github.event_name != 'schedule'
-        uses: ./.github/actions/run-embedding-sdk-storybook
-
-      - name: Run E2E tests for Embedding SDK
-        if: matrix.context == 'embedding-sdk' && github.event_name != 'schedule'
-        run: |
-          yarn run test-cypress-run \
-          --env grepTags="-@slow+-@flaky --@quarantine",grepOmitFiltered=true \
-          --folder 'embedding-sdk' \
-          --browser ${{ steps.cypress-prep.outputs.chrome-path }}
-        env:
-          CYPRESS_IS_EMBEDDING_SDK: true
-        shell: bash
-
-      - name: Upload Test Results
-        uses: ./.github/actions/upload-test-results
-        if: always()
-        with:
-          input-path: ./target/junit
-          output-name: e2e-${{ matrix.name }}
-          bucket: ${{ vars.AWS_S3_TEST_RESULTS_BUCKET }}
-          aws-access-key-id: ${{ secrets.AWS_TEST_RESULTS_ACCESS_KEY_ID }}
-          aws-secret-access-key: ${{ secrets.AWS_TEST_RESULTS_SECRET_ACCESS_KEY }}
-          aws-region: ${{ vars.AWS_REGION }}
-          trunk-api-token: ${{ secrets.TRUNK_API_TOKEN }}
-
-      - name: Upload Cypress Artifacts upon failure
-        uses: actions/upload-artifact@v4
-        if: failure()
-        with:
-          name: cypress-recording-${{ matrix.name }}-${{ matrix.edition }}
-          path: |
-            ./cypress
-            ./logs/test.log
-          if-no-files-found: ignore
-
-      - name: Publish Summary
-        if: failure()
-        uses: actions/github-script@v7
-        with:
-          script: | #js
-            const {
-               parseReport,
-               formatSummary
-             } = require("./.github/scripts/handle-mochawesome-report.js");
-
-             const report = parseReport();
-             const summary = formatSummary(report);
-
-             await core.summary.addRaw(summary).write();
-
-  e2e-tests-skipped-stub:
-    needs: [e2e-tests, e2e-matrix-builder]
+  # run this separately to make it non-blocking
+  flaky-e2e-tests:
+    name: Flaky e2e Tests
+    uses: ./.github/workflows/e2e-test.yml
+    needs: build
     if: |
-      !cancelled() &&
-      needs.e2e-tests.result == 'skipped'
-    runs-on: ${{ matrix.runner }}
+      !cancelled() && needs.build.result == 'success'
+    secrets: inherit
+    with:
+      name: Flaky
+      tags: "@flaky"
+
+  e2e-tests-result:
+    needs: [e2e-tests, flaky-e2e-tests]
+    runs-on: ubuntu-latest
     timeout-minutes: 5
-    name: e2e-tests-${{ matrix.name }}-${{ matrix.edition }}
-    strategy:
-      fail-fast: false
-      matrix: ${{ fromJSON(needs.e2e-matrix-builder.outputs.matrix) }}
+    name: e2e-tests-result
+    if: always() && !cancelled()
+    env:
+      E2E_TESTS_RESULT: ${{ needs.e2e-tests.result }}
+      FLAKY_E2E_TESTS_RESULT: ${{ needs.flaky-e2e-tests.result }}
     steps:
-      - run: |
+      - name: Stub
+        if: ${{ needs.e2e-tests.result == 'skipped' }}
+        run: |
           echo "Didn't run due to conditional filtering"
+      - name: Test results
+        if: ${{ needs.e2e-tests.result != 'skipped' }}
+        run: | # sh
+          echo "E2E Tests: ${{ needs.e2e-tests.result }}"
+          echo "Flaky E2E Tests: ${{ needs.flaky-e2e-tests.result }}"
+
+          if [ "${{ needs.e2e-tests.result }}" != "success" ]; then
+            echo "E2E Tests failed"
+            exit 1
+          fi
 
   pr-env:
     needs: [build]

.github/workflows/frontend.yml

@@ -123,3 +123,43 @@ jobs:
           m2-cache-key: "cljs"
       - name: Run frontend timezones tests
         run: yarn run test-timezones
+
+  fe-tests-result:
+    needs:
+      - fe-lint
+      - fe-type-check
+      - fe-tests-unit
+      - fe-tests-timezones
+    if: always() && !cancelled()
+    runs-on: ubuntu-latest
+    timeout-minutes: 5
+    env:
+      needs: ${{ toJson(needs) }}
+    steps:
+      - name: Check frontend job status
+        uses: actions/github-script@v7
+        env:
+          needs: ${{ toJson(needs) }}
+        with:
+          script: | # js
+            const needs = JSON.parse(process.env.needs);
+            const jobs = Object.entries(needs).map(
+              ([jobName, jobValues]) => ({
+                name: jobName,
+                result: jobValues.result
+              }));
+
+            // are all jobs skipped or successful?
+            if (jobs.every(job => (job.result === 'skipped' || job.result === 'success'))) {
+              console.log('All jobs are skipped or successful');
+              process.exit(0);
+            }
+
+            // otherwise, something failed
+            console.log('Some frontend jobs failed');
+            jobs.forEach((job) => {
+              if (job.result !== 'success') {
+                console.log(`${job.name} - ${job.result}`);
+              }
+            });
+            process.exit(1);

.github/workflows/links.yml

@@ -0,0 +1,32 @@
+name: Links
+
+on:
+  repository_dispatch:
+  workflow_dispatch:
+  schedule:
+    - cron: "0 0 * * 0"
+
+jobs:
+  linkChecker:
+    runs-on: ubuntu-latest
+    permissions:
+      issues: write # required for peter-evans/create-issue-from-file
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Link Checker
+        id: lychee
+        uses: lycheeverse/lychee-action@v2
+        with:
+          fail: false
+          args: docs --config ./.lychee/config.toml --verbose --no-progress
+          format: markdown
+
+      - name: Create Issue From File
+        if: steps.lychee.outputs.exit_code != 0
+        uses: peter-evans/create-issue-from-file@v5
+        with:
+          title: Link Checker Report
+          content-filepath: ./.lychee/out.md
+          labels: "Type:Documentation"
+          assignees: jeff-bruemmer

.github/workflows/loki-update.yml

@@ -61,9 +61,9 @@ jobs:
         with:
           github-token: ${{secrets.METABASE_AUTOMATION_USER_TOKEN}}
           script: |
-            github.issues.removeLabel({
+            github.rest.issues.removeLabel({
               issue_number: context.issue.number,
               owner: context.repo.owner,
               repo: context.repo.repo,
               name: 'loki-update'
-            })
+            });

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

@@ -210,12 +210,16 @@ jobs:
 
       - name: Create a PR updating readme + published version, and changelog (using GitHub Metabase Automation account)
         run: |
+          # TODO: Remove this step once github includes the new gh CLI version 2.65.0
+          eval "$(/home/linuxbrew/.linuxbrew/bin/brew shellenv)"
+          brew install gh
+
           git checkout -b update-sdk-version-${{ env.sdk_version }}
           git commit -a -m 'Update Readme version references and published npm version to ${{ env.sdk_version }}'
           git push origin HEAD
           gh pr create --base ${{ inputs.branch }}\
                        --assignee "${GITHUB_ACTOR}"\
-                       --title "Update SDK version to ${{ env.sdk_version }}"\
+                       --title "docs(sdk): Update SDK version to ${{ env.sdk_version }}"\
                        --body "Update Readme version references and published npm package version to ${{ env.sdk_version }}"
         env:
           GH_TOKEN: ${{ secrets.METABASE_AUTOMATION_USER_TOKEN }}
@@ -257,8 +261,8 @@ jobs:
           # Please keep the value in sync with `inputs.branch`'s release branch
           npm publish --tag ${{fromJson('{"master": "nightly", "release-x.51.x": "51-stable"}')[inputs.branch]}}
 
-      - name: Add `latest` tag to the latest release branch (`release-x.51.x`) deployment
-        if: ${{ inputs.branch == 'release-x.51.x' }}
+      - name: Add `latest` tag to the latest release branch (`release-x.52.x`) deployment
+        if: ${{ inputs.branch == 'release-x.52.x' }}
         working-directory: sdk
         run: |
           npm dist-tag add @metabase/embedding-sdk-react@${{ env.sdk_version }} latest

.github/workflows/release-log.yml

@@ -1,15 +1,18 @@
 name: Update Release Log
-run-name: Update Release Log ${{ inputs.version }}
+run-name: Update Release Log ${{ inputs.version || github.ref_name }}
 
 on:
+  push:
+    branches:
+      - release-x.*
+    tags:
+      - v*
   workflow_dispatch:
     inputs:
       version:
         description: 'Major Metabase version (e.g. 45, 52, 68)'
         type: number
         required: true
-  schedule:
-    - cron: '45 * * * *' # hourly
   workflow_call:
     inputs:
       version:
@@ -21,11 +24,8 @@ jobs:
   update-release-log:
     runs-on: ubuntu-latest
     timeout-minutes: 5
-    # don't run this workflow on a cron for forks
-    if: ${{ github.event_name != 'schedule' || github.repository == 'metabase/metabase' }}
-    env:
-      VERSION: ${{ (github.event_name == 'workflow_dispatch' || github.event_name == 'workflow_call')
-        && inputs.version || vars.CURRENT_VERSION }}
+    # don't run this workflow for forks
+    if: ${{ github.event_name != 'push' || github.repository == 'metabase/metabase' }}
     steps:
       - name: Configure AWS credentials
         uses: aws-actions/configure-aws-credentials@v4
@@ -35,9 +35,37 @@ jobs:
           aws-region: ${{ vars.AWS_REGION }}
       - uses: actions/checkout@v4
         with:
+          ref: master # this only works on master
           fetch-depth: 0 # we want all branches and tags
       - name: Install Dependencies
         run: yarn --cwd release --frozen-lockfile && npm i -g tsx
+      - name: Build release scripts
+        run: yarn --cwd release build
+      - name: Get version number
+        uses: actions/github-script@v7
+        with:
+          script: | # js
+            const {
+              getVersionFromReleaseBranch,
+              getMajorVersion,
+            } = require('${{ github.workspace }}/release/dist/index.cjs');
+
+            console.log({ context });
+
+            // if the version is explicitly set, use that
+            if (context.payload?.inputs?.version) {
+              core.exportVariable('VERSION', context.payload.inputs.version);
+              return;
+            }
+
+            // otherwise, get the version from the release branch name
+            const branch = context.payload.ref;
+            const version = getVersionFromReleaseBranch(branch);
+            const majorVersion = getMajorVersion(version);
+
+            console.log({ branch, version, majorVersion });
+            core.exportVariable('VERSION', majorVersion);
+
       - name: generate release Log
         run: cd release && tsx ./src/release-log-run.ts $VERSION > v$VERSION.html
       - name: generate release channel log

.github/workflows/release.yml

@@ -472,78 +472,6 @@ jobs:
         git config user.email github-actions@github.com
         $GITHUB_WORKSPACE/release/reorder-tags.sh ${{ needs.check-version.outputs.ee }} ${{ inputs.commit }}
 
-  trigger-docs-update:
-    if: ${{ !inputs.auto }}
-    needs:
-      - push-tags
-      - check-version
-    runs-on: ubuntu-22.04
-    timeout-minutes: 10
-    permissions:
-      contents: write
-      pull-requests: write
-    env:
-      NEW_OSS_VERSION: ${{ needs.check-version.outputs.oss }}
-      NEW_EE_VERSION: ${{ needs.check-version.outputs.ee }}
-      GH_TOKEN: ${{ secrets.METABASE_AUTOMATION_USER_TOKEN }}
-    steps:
-      - uses: actions/github-script@v7
-        with:
-          github-token: ${{ secrets.METABASE_AUTOMATION_USER_TOKEN }}
-          script: | # js
-            await github.rest.repos.createDispatchEvent({
-              owner: '${{ github.repository_owner }}',
-              repo: '${{ secrets.DOCS_REPO }}',
-              event_type: 'trigger-docs-update',
-              client_payload: {
-                version: '${{ inputs.version }}'
-              }
-            });
-      - uses: actions/checkout@v4
-        with:
-          token: ${{ secrets.METABASE_AUTOMATION_USER_TOKEN }}
-      - name: update releases.md
-        uses: actions/github-script@v7
-        with:
-          github-token: ${{ secrets.METABASE_AUTOMATION_USER_TOKEN }}
-          script: | # js
-            const fs = require('fs');
-
-            const releaseText = fs.readFileSync('./docs/releases.md', 'utf8');
-
-            const newReleaseText = releaseText
-              .replace(
-                /## Metabase Enterprise Edition releases\n\n/,
-                `## Metabase Enterprise Edition releases\n\n- [${process.env.NEW_EE_VERSION}](https://github.com/metabase/metabase/releases/tag/${process.env.NEW_EE_VERSION})\n`
-              )
-              .replace(
-                /## Metabase Open Source Edition releases\n\n/,
-                `## Metabase Open Source Edition releases\n\n- [${process.env.NEW_OSS_VERSION}](https://github.com/metabase/metabase/releases/tag/${process.env.NEW_OSS_VERSION})\n`
-              );
-
-            fs.writeFileSync('./docs/releases.md', newReleaseText);
-
-      - name: commit and push updates
-        run: | # bash
-          git config --global user.email "metabase-bot@metabase.com"
-          git config --global user.name "Metabase bot"
-
-          git checkout -b docs-add-$NEW_OSS_VERSION
-          cd docs/
-
-          git add releases.md
-          git commit -m "Add $NEW_OSS_VERSION to the list of releases"
-          git push origin docs-add-$NEW_OSS_VERSION --force
-
-      - name: open pr with updates
-        run: | # bash
-          gh pr create --fill \
-            --body "Like it says on the tin 😁" \
-            --label "Type:Documentation" \
-            --label "backport" \
-            --reviewer "jeff-bruemmer" \
-            --assignee "jeff-bruemmer"
-
   trigger-cloud-issues:
     if: ${{ !inputs.auto }}
     needs: push-tags

.gitignore

@@ -21,6 +21,7 @@
 /*.trace.db
 /.babel_cache
 /.env
+/.envrc
 /.lein-env
 /.lein-failures
 /.lein-plugins

.lychee/config.toml

@@ -0,0 +1 @@
+accept = ["200..=204", "429"]

.lycheeignore

@@ -0,0 +1,2 @@
+http://localhost*
+https://admin.google.com

.storybook-sdk/main.js

@@ -0,0 +1,105 @@
+const webpack = require("webpack");
+const MiniCssExtractPlugin = require("mini-css-extract-plugin");
+const appConfig = require("../webpack.config");
+const fs = require("fs");
+const path = require("path");
+
+const {
+  isEmbeddingSdkPackageInstalled,
+  embeddingSdkVersion: EMBEDDING_SDK_VERSION,
+} = resolveEmbeddingSdkPackage();
+
+module.exports = {
+  core: {
+    builder: "webpack5",
+  },
+  stories: ["../enterprise/frontend/src/embedding-sdk/**/*.stories.tsx"],
+  staticDirs: ["../resources/frontend_client"],
+  addons: [
+    "@storybook/addon-essentials",
+    "@storybook/addon-links",
+    "@storybook/addon-a11y",
+    "@storybook/addon-interactions",
+    "storybook-addon-pseudo-states",
+  ],
+  features: {
+    interactionsDebugger: true,
+  },
+  babel: () => {},
+  typescript: {
+    reactDocgen: "react-docgen-typescript-plugin",
+  },
+  webpackFinal: storybookConfig => ({
+    ...storybookConfig,
+    plugins: [
+      ...storybookConfig.plugins,
+      new MiniCssExtractPlugin(),
+      new webpack.ProvidePlugin({
+        Buffer: ["buffer", "Buffer"],
+      }),
+      new webpack.EnvironmentPlugin({
+        EMBEDDING_SDK_VERSION,
+        IS_EMBEDDING_SDK: true,
+      }),
+    ],
+    module: {
+      ...storybookConfig.module,
+      rules: [
+        ...storybookConfig.module.rules.filter(
+          rule => !isCSSRule(rule) && !isSvgRule(rule),
+        ),
+        ...appConfig.module.rules.filter(
+          rule => isCSSRule(rule) || isSvgRule(rule),
+        ),
+      ],
+    },
+    resolve: {
+      ...storybookConfig.resolve,
+      alias: {
+        ...appConfig.resolve.alias,
+        ...(isEmbeddingSdkPackageInstalled && {
+          // $ means that only exact "embedding-sdk" imports will be rerouted, all nested embedding-sdk/* will still be resolved locally
+          "embedding-sdk$": require.resolve("@metabase/embedding-sdk-react"),
+        }),
+      },
+      extensions: appConfig.resolve.extensions,
+    },
+  }),
+};
+
+const isCSSRule = rule => rule.test.toString() === "/\\.css$/";
+const isSvgRule = rule => rule.test && rule.test?.test(".svg");
+
+function resolveEmbeddingSdkPackage() {
+  let isEmbeddingSdkPackageInstalled = false;
+  let embeddingSdkVersion;
+
+  try {
+    const packagePath = require.resolve("@metabase/embedding-sdk-react");
+    if (packagePath.includes("node_modules")) {
+      isEmbeddingSdkPackageInstalled = true;
+    }
+
+    const packageJsonContent = fs.readFileSync(
+      path.join(packagePath, "package.json"),
+      "utf-8",
+    );
+    embeddingSdkVersion = JSON.stringify(
+      JSON.parse(packageJsonContent)?.version,
+    );
+  } catch (err) {
+    const sdkPackageTemplateJson = fs.readFileSync(
+      path.resolve(
+        "./enterprise/frontend/src/embedding-sdk/package.template.json",
+      ),
+      "utf-8",
+    );
+    const sdkPackageTemplateJsonContent = JSON.parse(sdkPackageTemplateJson);
+    embeddingSdkVersion = JSON.stringify(sdkPackageTemplateJsonContent.version);
+  }
+
+  return {
+    isEmbeddingSdkPackageInstalled,
+    embeddingSdkVersion,
+  };
+}

.storybook-sdk/preview.tsx

@@ -0,0 +1,32 @@
+import { GlobalTypes } from "@storybook/types";
+
+// @ts-expect-error: See metabase/lib/delay
+// This will skip the skippable delays in stories
+window.METABASE_REMOVE_DELAYS = true;
+
+import { storybookThemeOptions } from "embedding-sdk/test/storybook-themes";
+
+export const parameters = {
+  actions: { argTypesRegex: "^on[A-Z].*" },
+  controls: {
+    matchers: {
+      color: /(background|color)$/i,
+      date: /Date$/,
+    },
+  },
+};
+
+export const decorators = []; // No decorators for Embedding SDK stories, as we want to simulate real use cases
+
+export const globalTypes: GlobalTypes = {
+  sdkTheme: {
+    name: "SDK Theme",
+    description: "Global theme for sdk components",
+    defaultValue: "default",
+    toolbar: {
+      icon: "paintbrush",
+      items: storybookThemeOptions,
+      showName: true,
+    },
+  },
+};

.storybook/main.js

@@ -4,27 +4,16 @@ const appConfig = require("../webpack.config");
 const fs = require("fs");
 const path = require("path");
 
-const isEmbeddingSDK = process.env.IS_EMBEDDING_SDK === "true";
-
 const mainAppStories = [
   "../frontend/**/*.stories.mdx",
   "../frontend/**/*.stories.@(js|jsx|ts|tsx)",
 ];
 
-const embeddingSdkStories = [
-  "../enterprise/frontend/src/embedding-sdk/**/*.stories.tsx",
-];
-
-const {
-  isEmbeddingSdkPackageInstalled,
-  embeddingSdkVersion: EMBEDDING_SDK_VERSION,
-} = resolveEmbeddingSdkPackage();
-
 module.exports = {
   core: {
     builder: "webpack5",
   },
-  stories: isEmbeddingSDK ? embeddingSdkStories : mainAppStories,
+  stories: mainAppStories,
   staticDirs: ["../resources/frontend_client"],
   addons: [
     "@storybook/addon-essentials",
@@ -49,8 +38,7 @@ module.exports = {
         Buffer: ["buffer", "Buffer"],
       }),
       new webpack.EnvironmentPlugin({
-        EMBEDDING_SDK_VERSION,
-        IS_EMBEDDING_SDK: isEmbeddingSDK,
+        IS_EMBEDDING_SDK: false,
       }),
     ],
     module: {
@@ -68,10 +56,6 @@ module.exports = {
       ...storybookConfig.resolve,
       alias: {
         ...appConfig.resolve.alias,
-        ...(isEmbeddingSdkPackageInstalled && {
-          // $ means that only exact "embedding-sdk" imports will be rerouted, all nested embedding-sdk/* will still be resolved locally
-          "embedding-sdk$": require.resolve("@metabase/embedding-sdk-react"),
-        }),
       },
       extensions: appConfig.resolve.extensions,
     },
@@ -80,28 +64,3 @@ module.exports = {
 
 const isCSSRule = rule => rule.test.toString() === "/\\.css$/";
 const isSvgRule = rule => rule.test && rule.test?.test(".svg");
-
-function resolveEmbeddingSdkPackage() {
-  let isEmbeddingSdkPackageInstalled = false;
-  let embeddingSdkVersion;
-
-  try {
-    embeddingSdkVersion =
-      require("@metabase/embedding-sdk-react/package.json").version;
-    isEmbeddingSdkPackageInstalled = true;
-  } catch (err) {
-    const sdkPackageTemplateJson = fs.readFileSync(
-      path.resolve(
-        "./enterprise/frontend/src/embedding-sdk/package.template.json",
-      ),
-      "utf-8",
-    );
-    const sdkPackageTemplateJsonContent = JSON.parse(sdkPackageTemplateJson);
-    embeddingSdkVersion = JSON.stringify(sdkPackageTemplateJsonContent.version);
-  }
-
-  return {
-    isEmbeddingSdkPackageInstalled,
-    embeddingSdkVersion,
-  };
-}

.storybook/preview.tsx

@@ -1,14 +1,14 @@
 import React from "react";
 import { ThemeProvider } from "metabase/ui";
 
-const isEmbeddingSDK = process.env.IS_EMBEDDING_SDK === "true";
+// @ts-expect-error: See metabase/lib/delay
+// This will skip the skippable delays in stories
+window.METABASE_REMOVE_DELAYS = true;
 
-if (!isEmbeddingSDK) {
-  require("metabase/css/core/index.css");
-  require("metabase/css/vendor.css");
-  require("metabase/css/index.module.css");
-  require("metabase/lib/dayjs");
-}
+require("metabase/css/core/index.css");
+require("metabase/css/vendor.css");
+require("metabase/css/index.module.css");
+require("metabase/lib/dayjs");
 
 import { EmotionCacheProvider } from "metabase/styled-components/components/EmotionCacheProvider";
 import { getMetabaseCssVariables } from "metabase/styled-components/theme/css-variables";
@@ -39,19 +39,22 @@ const globalStyles = css`
   ${baseStyle}
 `;
 
-export const decorators = isEmbeddingSDK
-  ? [] // No decorators for Embedding SDK stories, as we want to simulate real use cases
-  : [
-      renderStory => (
-        <EmotionCacheProvider>
-          <ThemeProvider>
-            <Global styles={globalStyles} />
-            <CssVariables />
-            {renderStory()}
-          </ThemeProvider>
-        </EmotionCacheProvider>
-      ),
-    ];
+export const decorators = [
+  renderStory => {
+    if (!document.body.classList.contains("mb-wrapper")) {
+      document.body.classList.add("mb-wrapper");
+    }
+    return (
+      <EmotionCacheProvider>
+        <ThemeProvider>
+          <Global styles={globalStyles} />
+          <CssVariables />
+          {renderStory()}
+        </ThemeProvider>
+      </EmotionCacheProvider>
+    );
+  },
+];
 
 function CssVariables() {
   const theme = useTheme();

bin/embedding-sdk/fixup-types-after-compilation.js

@@ -5,7 +5,6 @@ const fs = require("fs");
 const path = require("path");
 
 const SDK_DIST_DIR_PATH = path.resolve("./resources/embedding-sdk/dist");
-const SDK_PACKAGE_NAME = "@metabase/embedding-sdk-react";
 
 /*
  * This script replaces all custom aliases in Embedding SDK generated ".d.ts" files so that this imports could be resolved
@@ -14,12 +13,12 @@ const SDK_PACKAGE_NAME = "@metabase/embedding-sdk-react";
 
 // this map should be synced with "tsconfig.sdk.json"
 const REPLACES_MAP = {
-  "metabase-enterprise": `${SDK_PACKAGE_NAME}/dist/enterprise/frontend/src/metabase-enterprise`,
-  "metabase-lib": `${SDK_PACKAGE_NAME}/dist/frontend/src/metabase-lib`,
-  "metabase-types": `${SDK_PACKAGE_NAME}/dist/frontend/src/metabase-types`,
-  metabase: `${SDK_PACKAGE_NAME}/dist/frontend/src/metabase`,
-  "embedding-sdk": `${SDK_PACKAGE_NAME}/dist/enterprise/frontend/src/embedding-sdk`,
-  cljs: `${SDK_PACKAGE_NAME}/dist/target/cljs_release`,
+  "metabase-enterprise": "enterprise/frontend/src/metabase-enterprise",
+  "metabase-lib": "frontend/src/metabase-lib",
+  "metabase-types": "frontend/src/metabase-types",
+  metabase: "frontend/src/metabase",
+  "embedding-sdk": "enterprise/frontend/src/embedding-sdk",
+  cljs: "target/cljs_release",
 };
 
 const traverseFilesTree = dir => {
@@ -42,24 +41,30 @@ const traverseFilesTree = dir => {
   }
 };
 
+const getRelativePath = (fromPath, toPath) => {
+  const relativePath = path.relative(path.dirname(fromPath), toPath);
+  return relativePath.startsWith(".") ? relativePath : "./" + relativePath;
+};
+
 const replaceAliasedImports = filePath => {
   let fileContent = fs.readFileSync(filePath, { encoding: "utf8" });
 
-  Object.entries(REPLACES_MAP).forEach(([alias, replacement]) => {
+  Object.entries(REPLACES_MAP).forEach(([alias, targetPath]) => {
+    const relativePath = getRelativePath(
+      filePath,
+      path.join(SDK_DIST_DIR_PATH, targetPath),
+    );
+
     fileContent = fileContent
-      // replaces "metabase-lib/foo" with "<sdk>/metabase-lib/foo"
-      .replaceAll(`from "${alias}/`, `from "${replacement}/`)
-      // replaces "metabase-lib" with "<sdk>/metabase-lib"
-      .replaceAll(`from "${alias}"`, `from "${replacement}"`)
-      .replaceAll(`import("${alias}`, `import("${replacement}`)
+      .replaceAll(`from "${alias}/`, `from "${relativePath}/`)
+      .replaceAll(`from "${alias}"`, `from "${relativePath}"`)
+      .replaceAll(`import("${alias}`, `import("${relativePath}`)
       .replace(
-        // replace dynamic imports using alias, with possible relative paths - "../../" and "frontend/src/"
-        // import("(../)*(frontend/src/)*<alias>
         new RegExp(
           `import\\("(\\.\\.\/)*(frontend\/src\/)*${alias.replace("/", "\\/")}`,
           "gi",
         ),
-        `import("${replacement}`,
+        `import("${relativePath}`,
       );
   });
 

deps.edn

@@ -49,6 +49,7 @@
   com.fasterxml.woodstox/woodstox-core      {:mvn/version "6.6.1"}              ; trans dep of commons-codec
   com.h2database/h2                         {:mvn/version "2.1.214"}            ; embedded SQL database
   com.gfredericks/test.chuck                {:mvn/version "0.2.14"}             ; generating strings from regex
+  com.mchange/c3p0                          {:mvn/version "0.10.1"}             ; DB connection pool
   com.snowplowanalytics/snowplow-java-tracker
   {:mvn/version "1.0.1"               ; Snowplow analytics
    :exclusions [com.fasterxml.jackson.core/jackson-databind]}
@@ -76,11 +77,11 @@
   instaparse/instaparse                     {:mvn/version "1.4.12"}             ; Make your own parser
   junegunn/grouper                          {:mvn/version "0.1.1"}              ; Batch processing helper
   clj-commons/clj-yaml                      {:mvn/version "1.0.27"}             ; Clojure wrapper for YAML library SnakeYAML
-  io.github.camsaul/toucan2                 {:mvn/version "1.0.556"}
+  io.github.camsaul/toucan2                 {:mvn/version "1.0.560"}
   io.github.eerohele/pp                     {:git/tag "2024-01-04.60"           ; super fast pretty-printing library
                                              :git/sha "a428751"
                                              :git/url "https://github.com/eerohele/pp"}
-  io.github.metabase/macaw                  {:mvn/version "0.2.24"}             ; Parse native SQL queries
+  io.github.metabase/macaw                  {:mvn/version "0.2.25"}             ; Parse native SQL queries
   ;; The 2.X line of Resilience4j requires Java 17, so we cannot upgrade this dependency until that is our minimum JVM version
   io.github.resilience4j/resilience4j-retry {:mvn/version "1.7.1" #_"must be 1.7.1"} ; Support for retrying operations
   io.prometheus/simpleclient_hotspot        {:mvn/version "0.16.0"}             ; prometheus jvm collector
@@ -107,7 +108,7 @@
   net.i2p.crypto/eddsa                      {:mvn/version "0.3.0"}              ; ED25519 key support (optional dependency for org.apache.sshd/sshd-core)
   net.redhogs.cronparser/cron-parser-core   {:mvn/version "3.5"                 ; describe Cron schedule in human-readable language
                                              :exclusions  [org.slf4j/slf4j-api]}
-  net.sf.cssbox/cssbox                      {:mvn/version "5.0.1"               ; HTML / CSS rendering
+  net.sf.cssbox/cssbox                      {:mvn/version "5.0.2"               ; HTML / CSS rendering
                                              :exclusions  [org.slf4j/slf4j-api
                                                            junit/junit]}
   net.thisptr/jackson-jq                    {:mvn/version "1.0.0-preview.20240207"} ; Java implementation of the JQ json query language

dev/src/dev.clj

@@ -55,6 +55,7 @@
    [clojure.test]
    [dev.debug-qp :as debug-qp]
    [dev.explain :as dev.explain]
+   [dev.memory :as dev.memory]
    [dev.migrate :as dev.migrate]
    [dev.model-tracking :as model-tracking]
    [dev.render-png :as render-png]
@@ -109,6 +110,9 @@
   migrate!
   rollback!
   migration-sql-by-id]
+ [dev.memory
+  with-memory-logging
+  measuring-thread-allocations]
  [render-png
   open-html
   open-png-bytes

dev/src/dev/memory.clj

@@ -19,8 +19,6 @@
     (assert (.isThreadAllocatedMemorySupported mx-bean))
     (.getThreadAllocatedBytes mx-bean thread-id)))
 
-(set! *warn-on-reflection* true)
-
 (defn mb-str
   "Format bytes as megabytes"
   [bytes]
@@ -42,11 +40,42 @@
      (log/warnf "Allocated: %s" (mb-str (:allocations m#)))
      (:result m#)))
 
+(def ^{:dynamic true
+       :private true} *memory-log-level* -1)
+
+(defn- used-mb
+  []
+  (let [rt (Runtime/getRuntime)
+        mb (* 1024.0 1024.0)]
+    (/ (- (.totalMemory rt) (.freeMemory rt)) mb)))
+
+(defn log-memory-usage
+  "Executes body-fn and logs memory usage before and after execution.
+  Returns the result of body-fn."
+  [body-fn context]
+  (binding [*memory-log-level* (inc *memory-log-level*)]
+    (let [indent (apply str (repeat *memory-log-level* "  "))
+          before (used-mb)
+          print-stats (fn
+                        ([stats]
+                         (log/infof "%s%s | Memory before:: %.2f MB "
+                                    indent context stats))
+                        ([before after]
+                         (log/infof "%s%s | Memory after:: %.2f MB (delta: %.2f MB)"
+                                    indent context after (- after before))))
+          _ (print-stats before)
+          result (body-fn)
+          after (used-mb)
+          _ (print-stats before after)]
+      result)))
+
+(defmacro with-memory-logging
+  "Executes body and logs memory usage before and after execution.
+  Returns the result of body."
+  [context & body]
+  `(log-memory-usage (fn [] ~@body) ~context))
+
 (comment
   ;; almost correct, at least a constant error
   (measuring-thread-allocations
-   (byte-array (* 1024 1024)))
-  ;; => 1.028MB
-  ;; => 1.028MB
-  ;; => 1.028MB
-  )
+   (byte-array (* 1024 1024))))

dev/src/dev/migrate.clj

@@ -37,7 +37,7 @@
   ([direction & [version]]
    (mdb/migrate! (mdb/data-source) direction version)
    #_{:clj-kondo/ignore [:discouraged-var]}
-   (println "Migrated up. Latest migration:" (latest-migration))))
+   (println (format "Migrated %s. Latest migration: %s" (name direction) (latest-migration)))))
 
 (defn- rollback-n-migrations!
   [^Integer n]

docs/CONTRIBUTING.md

@@ -1,7 +1,7 @@
 ---
 title: Contributing to Metabase
 redirect_from:
-  - /docs/latest/contributing
+  - /docs/latest/developers-guide/contributing
 ---
 
 # Contributing to Metabase
@@ -61,7 +61,7 @@ Once one or more people have started to work on a feature, it should be marked [
 
 ### E) Verification and merging
 
-All PRs that involve more than an insignificant change should be reviewed. See our [Code Review Process](code-reviews.md).
+All PRs that involve more than an insignificant change should be reviewed. See our [Code Review Process](./developers-guide/code-reviews.md).
 
 If all goes well, the feature gets coded up, verified and then the pull request gets merged! High-fives all around.
 
@@ -95,7 +95,7 @@ By our definition, "Bugs" are situations where the program doesn't do what it wa
 
 There are a lot of docs, which means keeping them up to date is hard. If you notice inconsistencies, errors, or outdated information, please help us keep them current!
 
-Note that **we cannot accept translations for documentation at this time**. We support [in-app translations](../configuring-metabase/localization.md), and only support languages that have 100% coverage. But 1) the in-app text is orders of magnitude shorter than our docs, 2) it changes at a slower pace, and 3) we have a lot of people help out. We may consider supporting docs in multiple languages in the future, but for now we need to focus our resources on improving our existing documentation (and expanding it to include all of the new features we're adding).
+Note that **we cannot accept translations for documentation at this time**. We support [in-app translations](./configuring-metabase/localization.md), and only support languages that have 100% coverage. But 1) the in-app text is orders of magnitude shorter than our docs, 2) it changes at a slower pace, and 3) we have a lot of people help out. We may consider supporting docs in multiple languages in the future, but for now we need to focus our resources on improving our existing documentation (and expanding it to include all of the new features we're adding).
 
 ### Working on features
 

docs/README.md

@@ -132,6 +132,7 @@ Metabase's reference documentation.
 - [Data reference](./exploration-and-organization/data-model-reference.md)
 - [Events and timelines](./exploration-and-organization/events-and-timelines.md)
 - [X-rays](./exploration-and-organization/x-rays.md)
+- [Content verification](./exploration-and-organization/content-verification.md)
 
 ### People
 
@@ -140,7 +141,8 @@ Metabase's reference documentation.
 - [Managing people and groups](./people-and-groups/managing.md)
 - [Password complexity](./people-and-groups/changing-password-complexity.md)
 - [Session expiration](./people-and-groups/changing-session-expiration.md)
-- [Google Sign-In or LDAP](./people-and-groups/google-and-ldap.md)
+- [Google Sign-In](./people-and-groups/google-sign-in.md)
+- [LDAP](./people-and-groups/ldap.md)
 - [API keys](./people-and-groups/api-keys.md)
 
 #### Paid SSO options
@@ -206,7 +208,7 @@ Metabase's reference documentation.
 ### Metabase API
 
 - [Metabase API documentation](./api-documentation.md)
-- [API tutorial](https://www.metabase.com/learn/metabase-basics/administration/administration-and-operation//metabase-api)
+- [API tutorial](https://www.metabase.com/learn/metabase-basics/administration/administration-and-operation/metabase-api)
 
 ### Troubleshooting
 
@@ -262,7 +264,7 @@ We tweet stuff.
 
 Follow us on GitHub.
 
-### [List of releases](./releases.md)
+### [List of releases](https://github.com/metabase/metabase/releases)
 
 A list of all Metabase releases, including both the Enterprise Edition and the Open Source Edition.
 

docs/api-documentation.md

@@ -7,7 +7,7 @@ title: "Metabase API documentation"
 _These reference files were generated from source comments by running:_
 
 ```
-clojure -M:ee:run api-documentation
+clojure -M:ee:doc api-documentation
 ```
 
 ## About the Metabase API
@@ -17,12 +17,16 @@ clojure -M:ee:run api-documentation
 
 ## API tutorial
 
-Check out an introduction to the [Metabase API](https://www.metabase.com/learn/metabase-basics/administration/administration-and-operation//metabase-api).
+Check out an introduction to the [Metabase API](https://www.metabase.com/learn/administration/metabase-api.html).
 
 ## API keys
 
 Create keys to authenticate programmatic requests to your Metabase. See [API keys](./people-and-groups/api-keys.md).
 
+## API changelog
+
+For breaking changes, see the API [changelog](./developers-guide/api-changelog.md).
+
 ## API endpoints
 
 _* indicates endpoints used for features available on [paid plans](https://www.metabase.com/pricing)._

docs/api/alert.md

@@ -2,12 +2,16 @@
 title: "Alert"
 summary: |
   /api/alert endpoints.
+  
+    Deprecated: will soon be migrated to notification APIs.
 ---
 
 # Alert
 
 /api/alert endpoints.
 
+  Deprecated: will soon be migrated to notification APIs.
+
 ## `DELETE /api/alert/:id/subscription`
 
 For users to unsubscribe themselves from the given alert.

docs/api/cache.md

@@ -44,11 +44,11 @@ Invalidate cache entries.
 
 -  **`include`** All cache configuration overrides should invalidate cache too.
 
--  **`database`** A database id.
+-  **`database`** A list of database ids.
 
--  **`dashboard`** A dashboard id.
+-  **`dashboard`** A list of dashboard ids.
 
--  **`question`** A question id.
+-  **`question`** A list of question ids.
 
 ## `PUT /api/cache/`
 

docs/api/card.md

@@ -208,7 +208,9 @@ Run the query associated with a Card, and return its results as a file in the sp
 
 -  **`parameters`** nullable value must be a valid JSON string.
 
--  **`format_rows`** nullable boolean.
+-  **`pivot_results`** nullable value must be a valid boolean string ('true' or 'false').
+
+-  **`format_rows`** nullable value must be a valid boolean string ('true' or 'false').
 
 ## `POST /api/card/:card-id/refresh`
 

docs/api/collection.md

@@ -223,10 +223,14 @@ Modify an existing Collection, including archiving or unarchiving it, or moving
 
 ## `PUT /api/collection/graph`
 
-Do a batch update of Collections Permissions by passing in a modified graph.
-  Will overwrite parts of the graph that are present in the request, and leave the rest unchanged.
+Do a batch update of Collections Permissions by passing in a modified graph. Will overwrite parts of the graph that
+  are present in the request, and leave the rest unchanged.
 
-  If the `skip_graph` query parameter is true, it will only return the current revision.
+  If the `force` query parameter is `true`, a `revision` number is not required. The provided graph will be persisted
+  as-is, and has the potential to clobber other writes that happened since the last read.
+
+  If the `skip_graph` query parameter is `true`, it will only return the current revision, not the entire permissions
+  graph.
 
 You must be a superuser to do this.
 
@@ -234,11 +238,13 @@ You must be a superuser to do this.
 
 -  **`namespace`** nullable value must be a non-blank string.
 
--  **`revision`** value must be an integer.
+-  **`revision`** nullable value must be an integer.
 
 -  **`groups`** map.
 
--  **`skip_graph`** nullable value must be a valid boolean string ('true' or 'false').
+-  **`skip-graph`** nullable value must be a valid boolean string ('true' or 'false').
+
+-  **`force`** nullable value must be a valid boolean string ('true' or 'false').
 
 ---
 

docs/api/dashboard.md

@@ -220,7 +220,9 @@ Run the query associated with a Saved Question (`Card`) in the context of a `Das
 
 -  **`parameters`** nullable value must be a valid JSON string.
 
--  **`format_rows`** nullable boolean.
+-  **`format_rows`** nullable value must be a valid boolean string ('true' or 'false').
+
+-  **`pivot_results`** nullable value must be a valid boolean string ('true' or 'false').
 
 -  **`request-parameters`**
 

docs/api/dataset.md

@@ -30,7 +30,9 @@ Execute a query and download the result data as a file in the specified format.
 
 -  **`visualization_settings`** value must be a valid JSON string.
 
--  **`format_rows`** nullable boolean.
+-  **`pivot_results`** nullable value must be a valid boolean string ('true' or 'false').
+
+-  **`format_rows`** nullable value must be a valid boolean string ('true' or 'false').
 
 ## `POST /api/dataset/native`
 

docs/api/ee/advanced-permissions-application.md

@@ -24,6 +24,14 @@ Do a batch update of Application Permissions by passing a modified graph.
 
 You must be a superuser to do this.
 
+### PARAMS:
+
+-  **`skip-graph`** nullable value must be a valid boolean string ('true' or 'false').
+
+-  **`force`** nullable value must be a valid boolean string ('true' or 'false').
+
+-  **`body`** map.
+
 ---
 
 [<< Back to API index](../../api-documentation.md)

docs/api/ee/content-verification-review.md

@@ -20,7 +20,7 @@ You must be a superuser to do this.
 
 -  **`moderated_item_id`** value must be an integer greater than zero.
 
--  **`moderated_item_type`** enum of card, :card.
+-  **`moderated_item_type`** enum of card, :card, dashboard, :dashboard.
 
 -  **`status`** nullable nullable enum of verified.
 

docs/api/embed.md

@@ -140,6 +140,8 @@ Like `GET /api/embed/card/query`, but returns the results as a file in the speci
 
 -  **`format_rows`** nullable boolean.
 
+-  **`pivot_results`** nullable boolean.
+
 -  **`query-params`**
 
 ## `GET /api/embed/dashboard/:token`
@@ -188,6 +190,8 @@ Fetch the results of running a Card belonging to a Dashboard using a JSON Web To
 
 -  **`format_rows`** nullable boolean.
 
+-  **`pivot_results`** nullable boolean.
+
 -  **`query-params`**
 
 ## `GET /api/embed/dashboard/:token/field/:field-id/remapping/:remapped-id`

docs/api/notify.md

@@ -42,6 +42,22 @@ Sync a new table without running a full database sync. Requires `schema_name` an
 
 -  **`table_name`** value must be a non-blank string.
 
+## `POST /api/notify/db/attached_datawarehouse`
+
+Sync the attached datawarehouse. Can provide in the body:
+  - table_name and schema_name: both strings. Will look for an existing table and sync it, otherwise will try to find a
+  new table with that name and sync it. If it cannot find a table it will throw an error. If table_name is empty or
+  blank, will sync the entire database.
+  - synchronous?: is a boolean value to indicate if this should block on the result.
+
+### PARAMS:
+
+-  **`table_name`** nullable value must be a non-blank string.
+
+-  **`schema_name`** nullable string.
+
+-  **`synchronous?`** nullable value must be a valid boolean string ('true' or 'false').
+
 ---
 
 [<< Back to API index](../api-documentation.md)

docs/api/permissions.md

@@ -118,7 +118,9 @@ You must be a superuser to do this.
 
 ### PARAMS:
 
--  **`skip-graph`** nullable boolean.
+-  **`skip-graph`** nullable value must be a valid boolean string ('true' or 'false').
+
+-  **`force`** nullable value must be a valid boolean string ('true' or 'false').
 
 -  **`body`** map.
 

docs/api/public.md

@@ -114,6 +114,8 @@ Fetch a publicly-accessible Card and return query results in the specified forma
 
 -  **`format_rows`** nullable boolean.
 
+-  **`pivot_results`** nullable boolean.
+
 ## `GET /api/public/dashboard/:uuid`
 
 Fetch a publicly-accessible Dashboard. Does not require auth credentials. Public sharing must be enabled.
@@ -286,6 +288,10 @@ Fetch the results of running a publicly-accessible Card belonging to a Dashboard
 
 -  **`export-format`** enum of csv, api, xlsx, json.
 
+-  **`format_rows`** nullable value must be a valid boolean string ('true' or 'false').
+
+-  **`pivot_results`** nullable value must be a valid boolean string ('true' or 'false').
+
 ## `POST /api/public/dashboard/:uuid/dashcard/:dashcard-id/execute`
 
 Execute the associated Action in the context of a `Dashboard` and `DashboardCard` that includes it.

docs/api/pulse.md

@@ -1,12 +1,18 @@
 ---
 title: "Pulse"
 summary: |
-  /api/pulse endpoints.
+  `/api/pulse` endpoints. These are all authenticated. For unauthenticated `/api/pulse/unsubscribe` endpoints,
+    see [[metabase.api.pulse.unsubscribe]].
+  
+    Deprecated: will soon be migrated to notification APIs.
 ---
 
 # Pulse
 
-/api/pulse endpoints.
+`/api/pulse` endpoints. These are all authenticated. For unauthenticated `/api/pulse/unsubscribe` endpoints,
+  see [[metabase.api.pulse.unsubscribe]].
+
+  Deprecated: will soon be migrated to notification APIs.
 
 ## `DELETE /api/pulse/:id/subscription`
 
@@ -78,7 +84,7 @@ Get PNG rendering of a Card with `id`.
 
 Get HTML rendering of a Dashboard with `id`.
 
-  This endpoint relies on a custom middleware defined in `metabase.pulse.preview/style-tag-nonce-middleware` to
+  This endpoint relies on a custom middleware defined in `metabase.channel.render.core/style-tag-nonce-middleware` to
   allow the style tag to render properly, given our Content Security Policy setup. This middleware is attached to these
   routes at the bottom of this namespace using `metabase.api.common/define-routes`.
 

docs/api/search.md

@@ -11,7 +11,7 @@ API endpoints for Search.
 ## `GET /api/search/`
 
 Search for items in Metabase.
-  For the list of supported models, check [[metabase.search/all-models]].
+  For the list of supported models, check [[metabase.search.config/all-models]].
 
   Filters:
   - `archived`: set to true to search archived items only, default is false
@@ -34,7 +34,7 @@ Search for items in Metabase.
 
 ### PARAMS:
 
--  **`filter_items_in_personal_collection`** nullable enum of only, exclude.
+-  **`filter_items_in_personal_collection`** nullable enum of all, only, only-mine, exclude, exclude-others.
 
 -  **`table_db_id`** nullable value must be an integer greater than zero.
 
@@ -60,39 +60,29 @@ Search for items in Metabase.
 
 -  **`last_edited_at`** nullable value must be a non-blank string.
 
+-  **`calculate_available_models`** nullable true.
+
+-  **`context`** nullable keyword.
+
 -  **`model_ancestors`** nullable boolean.
 
-## `GET /api/search/models`
+## `GET /api/search/weights`
 
-Get the set of models that a search query will return.
+Return the current weights being used to rank the search results.
 
 ### PARAMS:
 
--  **`filter_items_in_personal_collection`** 
-
--  **`created_by`** nullable vector of value must be an integer greater than zero.
-
--  **`verified`** nullable true.
-
--  **`created_at`** nullable value must be a non-blank string.
-
--  **`archived`** nullable value must be a valid boolean string ('true' or 'false').
-
--  **`q`** 
-
--  **`search_native_query`** nullable true.
-
--  **`search_engine`** nullable string.
-
--  **`last_edited_by`** nullable vector of value must be an integer greater than zero.
-
--  **`last_edited_at`** nullable value must be an integer greater than zero.
-
--  **`table-db-id`** nullable value must be an integer greater than zero.
+-  **`overrides`**
 
 ## `POST /api/search/force-reindex`
 
-If fulltext search is enabled, this will trigger a synchronous reindexing operation.
+This will trigger an immediate reindexing, if we are using search index.
+
+You must be a superuser to do this.
+
+## `POST /api/search/re-init`
+
+This will blow away any search indexes, re-create, and re-populate them.
 
 You must be a superuser to do this.
 

docs/api/session.md

@@ -61,34 +61,6 @@ Login with Google Auth.
 
 -  **`request`**
 
-## `POST /api/session/pulse/unsubscribe`
-
-Allow non-users to unsubscribe from pulses/subscriptions, with the hash given through email.
-
-### PARAMS:
-
--  **`email`** string.
-
--  **`hash`** string.
-
--  **`pulse-id`** value must be an integer greater than zero.
-
--  **`request`**
-
-## `POST /api/session/pulse/unsubscribe/undo`
-
-Allow non-users to undo an unsubscribe from pulses/subscriptions, with the hash given through email.
-
-### PARAMS:
-
--  **`email`** string.
-
--  **`hash`** string.
-
--  **`pulse-id`** value must be an integer greater than zero.
-
--  **`request`**
-
 ## `POST /api/session/reset_password`
 
 Reset password with a reset token.

docs/api/slack.md

@@ -12,6 +12,14 @@ summary: |
 
 Returns the YAML manifest file that should be used to bootstrap new Slack apps.
 
+## `POST /api/slack/bug-report`
+
+Send diagnostic information to the configured Slack channels.
+
+### PARAMS:
+
+-  **`diagnosticInfo`** map.
+
 ## `PUT /api/slack/settings`
 
 Update Slack related settings. You must be a superuser to do this. Also updates the slack-cache.
@@ -26,6 +34,8 @@ Update Slack related settings. You must be a superuser to do this. Also updates
 
 -  **`slack-files-channel`** nullable value must be a non-blank string.
 
+-  **`slack-bug-report-channel`** nullable string.
+
 ---
 
 [<< Back to API index](../api-documentation.md)

docs/api/user.md

@@ -130,7 +130,7 @@ Update a user's password.
 
 -  **`password`** password is too common.
 
--  **`old_password`**
+-  **`old_password`** 
 
 -  **`request`**
 
@@ -146,4 +146,4 @@ You must be a superuser to do this.
 
 ---
 
-[<< Back to API index](../api-documentation.md)
+[<< Back to API index](../api-documentation.md)

docs/configuring-metabase/config-file.md

@@ -6,14 +6,18 @@ title: "Configuration file"
 
 {% include plans-blockquote.html feature="Loading from a configuration file" self-hosted-only="true" %}
 
-On self-hosted Pro and Enterprise plans, Metabase supports initialization on launch from a config file named `config.yml`. The config file should be located at:
+On self-hosted [Pro](https://www.metabase.com/product/pro) and [Enterprise](https://www.metabase.com/product/enterprise) plans, Metabase supports initialization on launch from a config file named `config.yml`. The config file should be located at:
 
 - The current directory (the directory where the running Metabase JAR is located).
 - The path specified by the `MB_CONFIG_FILE_PATH` [environment variable](./environment-variables.md).
 
-The settings as defined in the config file work the same as if you set these settings in the Admin Settings in your Metabase. Settings defined in this configuration file will update any existing settings. If, for example, a database already exists (that is, you'd already added it via the initial set up or **Admin settings** > **Databases**, Metabase will update the database entry based on the data in the config file).
+The settings as defined in the config file work the same as if you set these settings in the Admin Settings in your Metabase. Settings defined in this configuration file will update any existing settings. If, for example, a database already exists (that is, you'd already added it via the initial set up or **Admin settings** > **Databases**, Metabase will update the database entry based on the data in the config file). Which means: if you define a setting in the config file, and then later change that setting in your Metabase application, keep in mind that the config file will overwrite that change whenever Metabase restarts.
 
-The config file settings are not treated as a hardcoded source of truth (like [environment variables](./environment-variables.md) are). Settings set by environment variables cannot be changed, even in the Admin settings in the application itself.
+The config file settings are NOT treated as a hardcoded source of truth (like [environment variables](./environment-variables.md) are). Settings set by environment variables cannot be changed, even in the Admin settings in the application itself.
+
+## Example config template
+
+See [Config template](./config-template.md).
 
 ## Config setup
 
@@ -85,7 +89,7 @@ config:
         host: localhost
         port: 5432
         user: dbuser
-        password: "{{ env POSTGRES_TEST_DATA_PASSWORD }}"
+        password: "{{{ env POSTGRES_TEST_DATA_PASSWORD }}}"
         dbname: test-data
 {% endraw %}
 ```
@@ -118,7 +122,7 @@ config:
         host: localhost
         port: 5432
         user: dbuser
-        password: "{{ env POSTGRES_TEST_DATA_PASSWORD }}"
+        password: "{{{ env POSTGRES_TEST_DATA_PASSWORD }}}"
         dbname: test-data
       uploads_enabled: true
       uploads_schema_name: uploads
@@ -130,7 +134,7 @@ See [Uploads](../databases/uploads.md).
 
 ## Referring to environment variables in the `config.yml`
 
-As shown in the Databases examples above, environment variables can be specified with `{% raw %}{{ template-tags }}{% endraw %}` like `{% raw %}{{ env POSTGRES_TEST_DATA_PASSWORD }}{% endraw %}` or `{% raw %}[[options {{template-tags}}]]{% endraw %}`.
+As shown in the Databases examples above, environment variables can be specified with `{% raw %}{{{ template-tags }}}{% endraw %}` like `{% raw %}{{{ env POSTGRES_TEST_DATA_PASSWORD }}}{% endraw %}` or `{% raw %}[[options {{{template-tags}}}]]{% endraw %}`.
 
 Metabase doesn't support recursive expansion, so if one of your environment variables references _another_ environment variable, you're going to have a bad time.
 
@@ -181,43 +185,7 @@ config:
       details: ...
 ```
 
-Just to give you an idea for some settings, here's an incomplete list of settings you can set via the config file:
-
-```txt
-application-colors
-config-from-file-sync-databases
-check-for-updates
-experimental-enable-actions
-persisted-model-refresh-cron-schedule
-email-smtp-host
-email-smtp-username
-start-of-week
-email-smtp-password
-email-smtp-port
-email-from-name
-email-from-address
-email-reply-to
-premium-embedding-token
-follow-up-email-sent
-persisted-models-enabled
-site-locale
-application-name
-settings-last-updated
-instance-creation
-enable-public-sharing
-enable-embedding
-embedding-secret-key
-jwt-group-sync
-anon-tracking-enabled
-snowplow-available
-jwt-enabled
-google-auth-enabled
-redirect-all-requests-to-https
-site-url
-site-name
-```
-
-But you can set any of the Admin settings with the config file. Check out the list of [environment variable](./environment-variables.md) to see what you can configure (though note that not all environment variables can be set via the config file.)
+But you can set any of the Admin settings with the config file (for a list of settings, check out the [config file template](./config-template.md)). You can also browse the list of [environment variable](./environment-variables.md) to see what you can configure (though note that not all environment variables can be set via the config file.)
 
 ## Loading a new Metabase from a config file
 
@@ -226,3 +194,8 @@ Since loading from a config file is a Pro/Enterprise feature: for new installati
 ```sh
 MB_PREMIUM_EMBEDDING_TOKEN="[your token]" java --add-opens java.base/java.nio=ALL-UNNAMED -jar metabase.jar
 ```
+
+## Further reading
+
+- [Config file template](./config-template.md)
+- [Environment variables](./environment-variables.md)

docs/configuring-metabase/config-template.md

@@ -0,0 +1,254 @@
+---
+title: "Metabase config file template"
+---
+
+# Metabase config file template
+
+You can generate the following config file template by changing into the top-level Metabase directory and running:
+
+```
+clojure -M:doc:ee config-template
+```
+
+The template lists example `database`, `user`, and `settings` sections for the [config file](./config-file.md).
+
+
+```yaml
+# A config file template for Metabase.
+# You'll need to update (or remove) the `users` and `databases` sections.
+# The settings in `settings` include default values. We recommend removing
+# or commenting out settings that you don't set.
+# For more on the configuration file, see:
+# https://www.metabase.com/docs/latest/configuring-metabase/config-file
+# For more on what each setting does, check out:
+# https://www.metabase.com/docs/latest/configuring-metabase/environment-variables
+version: 1
+config:
+  users:
+  - first_name: First
+    last_name: Person
+    password: metabot1
+    email: first@example.com
+  - first_name: Normal
+    last_name: Person
+    password: metabot1
+    email: normal@example.com
+  - first_name: Admin
+    last_name: Person
+    password: metabot1
+    is_superuser: true
+    email: admin@example.com
+  databases:
+  - name: Sample PostgreSQL
+    engine: postgres
+    details:
+      host: postgres-data
+      port: 5432
+      user: metabase
+      password: metasample123
+      dbname: sample
+  - name: Sample MySQL
+    engine: mysql
+    details:
+      host: mysql-data
+      port: 3306
+      user: metabase
+      password: metasample123
+      dbname: sample
+  settings:
+    admin-email: null
+    aggregated-query-row-limit: null
+    allowed-iframe-hosts: |-
+      youtube.com,
+      youtu.be,
+      loom.com,
+      vimeo.com,
+      docs.google.com,
+      calendar.google.com,
+      airtable.com,
+      typeform.com,
+      canva.com,
+      codepen.io,
+      figma.com,
+      grafana.com,
+      miro.com,
+      excalidraw.com,
+      notion.com,
+      atlassian.com,
+      trello.com,
+      asana.com,
+      gist.github.com,
+      linkedin.com,
+      twitter.com,
+      x.com
+    anon-tracking-enabled: true
+    api-key: null
+    application-colors: {}
+    application-favicon-url: app/assets/img/favicon.ico
+    application-font: Lato
+    application-font-files: null
+    application-logo-url: app/assets/img/logo.svg
+    application-name: Metabase
+    attachment-table-row-limit: 20
+    bcc-enabled: true
+    breakout-bin-width: 10.0
+    breakout-bins-num: 8
+    check-for-updates: true
+    config-from-file-sync-databases: true
+    custom-formatting: {}
+    custom-geojson: null
+    custom-homepage: false
+    custom-homepage-dashboard: null
+    db-connection-timeout-ms: 10000
+    db-query-timeout-minutes: 20
+    download-row-limit: null
+    ee-ai-features-enabled: false
+    ee-openai-api-key: null
+    ee-openai-model: gpt-4-turbo-preview
+    email-from-address: notifications@metabase.com
+    email-from-name: null
+    email-max-recipients-per-second: null
+    email-reply-to: null
+    email-smtp-host: null
+    email-smtp-password: null
+    email-smtp-port: null
+    email-smtp-security: none
+    email-smtp-username: null
+    embedding-app-origins-interactive: null
+    embedding-app-origins-sdk: localhost:*
+    embedding-homepage: hidden
+    embedding-secret-key: null
+    enable-embedding-interactive: false
+    enable-embedding-sdk: false
+    enable-embedding-static: false
+    enable-password-login: true
+    enable-pivoted-exports: true
+    enable-public-sharing: true
+    enable-query-caching: true
+    enable-xrays: true
+    enum-cardinality-threshold: 60
+    follow-up-email-sent: false
+    google-auth-auto-create-accounts-domain: null
+    google-auth-client-id: null
+    google-auth-enabled: null
+    health-check-logging-enabled: true
+    help-link: metabase
+    help-link-custom-destination: https://www.metabase.com/help/premium
+    humanization-strategy: simple
+    is-metabot-enabled: false
+    jdbc-data-warehouse-max-connection-pool-size: 15
+    jwt-attribute-email: email
+    jwt-attribute-firstname: first_name
+    jwt-attribute-groups: groups
+    jwt-attribute-lastname: last_name
+    jwt-enabled: false
+    jwt-group-mappings: {}
+    jwt-group-sync: false
+    jwt-identity-provider-uri: null
+    jwt-shared-secret: null
+    jwt-user-provisioning-enabled: true
+    landing-page: ''
+    landing-page-illustration: default
+    landing-page-illustration-custom: null
+    ldap-attribute-email: mail
+    ldap-attribute-firstname: givenName
+    ldap-attribute-lastname: sn
+    ldap-bind-dn: null
+    ldap-enabled: false
+    ldap-group-base: null
+    ldap-group-mappings: {}
+    ldap-group-membership-filter: (member={dn})
+    ldap-group-sync: false
+    ldap-host: null
+    ldap-password: null
+    ldap-port: 389
+    ldap-security: none
+    ldap-sync-user-attributes: true
+    ldap-sync-user-attributes-blacklist: userPassword,dn,distinguishedName
+    ldap-user-base: null
+    ldap-user-filter: (&(objectClass=inetOrgPerson)(|(uid={login})(mail={login})))
+    ldap-user-provisioning-enabled: true
+    loading-message: doing-science
+    login-page-illustration: default
+    login-page-illustration-custom: null
+    map-tile-server-url: https://{s}.tile.openstreetmap.org/{z}/{x}/{y}.png
+    metabot-default-embedding-model: text-embedding-ada-002
+    metabot-feedback-url: https://amtix3l3qvitb2qxstaqtcoqby0monuf.lambda-url.us-east-1.on.aws/
+    metabot-get-prompt-templates-url: https://stkxezsr2kcnkhusi3fgcc5nqm0ttgfx.lambda-url.us-east-1.on.aws/
+    metabot-prompt-generator-token-limit: 6000
+    native-query-autocomplete-match-style: substring
+    nested-field-columns-value-length-limit: 50000
+    no-data-illustration: default
+    no-data-illustration-custom: null
+    no-object-illustration: default
+    no-object-illustration-custom: null
+    notification-link-base-url: null
+    notification-thread-pool-size: 10
+    num-metabot-choices: 1
+    openai-api-key: null
+    openai-model: gpt-4-turbo-preview
+    openai-organization: null
+    persisted-model-refresh-cron-schedule: 0 0 0/6 * * ? *
+    persisted-models-enabled: false
+    premium-embedding-token: null
+    query-analysis-enabled: true
+    query-caching-max-kb: 2000
+    query-caching-max-ttl: 3024000.0
+    redirect-all-requests-to-https: false
+    report-timezone: null
+    reset-token-ttl-hours: 48
+    retry-initial-interval: 500
+    retry-max-attempts: 7
+    retry-max-interval-millis: 30000
+    retry-multiplier: 2.0
+    retry-randomization-factor: 0.1
+    saml-application-name: Metabase
+    saml-attribute-email: null
+    saml-attribute-firstname: http://schemas.xmlsoap.org/ws/2005/05/identity/claims/givenname
+    saml-attribute-group: member_of
+    saml-attribute-lastname: http://schemas.xmlsoap.org/ws/2005/05/identity/claims/surname
+    saml-enabled: false
+    saml-group-mappings: {}
+    saml-group-sync: false
+    saml-identity-provider-certificate: null
+    saml-identity-provider-issuer: null
+    saml-identity-provider-uri: null
+    saml-keystore-alias: metabase
+    saml-keystore-password: changeit
+    saml-keystore-path: null
+    saml-slo-enabled: false
+    saml-user-provisioning-enabled: true
+    scim-enabled: null
+    search-engine: in-place
+    search-typeahead-enabled: true
+    send-new-sso-user-admin-email: null
+    session-cookie-samesite: lax
+    session-cookies: null
+    session-timeout: null
+    setup-embedding-autoenabled: false
+    setup-license-active-at-setup: false
+    show-database-syncing-modal: null
+    show-homepage-data: true
+    show-homepage-xrays: true
+    show-metabase-links: true
+    show-metabot: true
+    show-static-embed-terms: true
+    site-locale: en
+    site-name: Metabase
+    site-url: null
+    slack-app-token: null
+    slack-bug-report-channel: metabase-bugs
+    slack-files-channel: metabase_files
+    source-address-header: X-Forwarded-For
+    sql-jdbc-fetch-size: 500
+    sql-parsing-enabled: true
+    ssh-heartbeat-interval-sec: 180
+    start-of-week: sunday
+    subscription-allowed-domains: null
+    surveys-enabled: true
+    synchronous-batch-updates: false
+    unaggregated-query-row-limit: null
+    update-channel: latest
+    uploads-settings: null
+    user-visibility: all
+```

docs/configuring-metabase/email.md

@@ -1,10 +1,10 @@
 ---
-title: Email
+title: Set up email
 redirect_from:
   - /docs/latest/administration-guide/02-setting-up-email
 ---
 
-# Email
+# Set up email
 
 Once you connect your database to Metabase, you'll want to configure an email account to send system notifications to your organization's users. Metabase uses email to reset passwords, onboard new users, and notify you when something happens.
 

docs/configuring-metabase/environment-variables.md

@@ -43,6 +43,10 @@ Docker:
 docker run -d -p 3000:3000 -e MB_SITE_NAME="Awesome Company" --name metabase metabase/metabase
 ```
 
+## Environment variables on Metabase Cloud
+
+If you're running Metabase Cloud, you can [contact support](https://www.metabase.com/help/premium) to adjust environment variables for your Metabase.
+
 ---
 
 ## List of environment variables
@@ -107,6 +111,17 @@ Allowed iframe hosts.
 
 Enable the collection of anonymous usage data in order to help Metabase improve.
 
+### `MB_API_KEY`
+
+- Type: string
+- Default: `null`
+
+When set, this API key is required for all API requests.
+
+Middleware that enforces validation of the client via the request header X-Metabase-Apikey.
+        If the header is available, then it’s validated against MB_API_KEY.
+        When it matches, the request continues; otherwise it’s blocked with a 403 Forbidden response.
+
 ### `MB_APPLICATION_COLORS`
 
 > Only available on Metabase [Pro](https://www.metabase.com/product/pro) and [Enterprise](https://www.metabase.com/product/enterprise) plans.
@@ -288,6 +303,15 @@ Object keyed by type, containing formatting settings.
 
 JSON containing information about custom GeoJSON files for use in map visualizations instead of the default US State or World GeoJSON.
 
+### `MB_CUSTOM_GEOJSON_ENABLED`
+
+- Type: boolean
+- Default: `true`
+- [Exported as](../installation-and-operation/serialization.md): `custom-geojson-enabled`.
+- [Configuration file name](./config-file.md): `custom-geojson-enabled`
+
+Whether or not the use of custom GeoJSON is enabled.
+
 ### `MB_CUSTOM_HOMEPAGE`
 
 - Type: boolean
@@ -328,6 +352,15 @@ Timeout in minutes for databases query execution, both Metabase application data
   Adjusting the timeout does not impact Metabase’s frontend.
   Please be aware that other services (like Nginx) may still drop long-running queries.
 
+### `MB_DEFAULT_MAPS_ENABLED`
+
+- Type: boolean
+- Default: `true`
+- [Exported as](../installation-and-operation/serialization.md): `default-maps-enabled`.
+- [Configuration file name](./config-file.md): `default-maps-enabled`
+
+Whether or not the default GeoJSON maps are enabled.
+
 ### `MB_DOWNLOAD_ROW_LIMIT`
 
 - Type: integer
@@ -382,6 +415,16 @@ The email address you want to use for the sender of emails.
 
 The name you want to use for the sender of emails.
 
+### `MB_EMAIL_MAX_RECIPIENTS_PER_SECOND`
+
+- Type: integer
+- Default: `null`
+- [Exported as](../installation-and-operation/serialization.md): `email-max-recipients-per-second`.
+- [Configuration file name](./config-file.md): `email-max-recipients-per-second`
+
+The maximum number of recipients, summed across emails, that can be sent per second.
+                Note that the final email sent before reaching the limit is able to exceed it, if it has multiple recipients.
+
 ### `MB_EMAIL_REPLY_TO`
 
 - Type: json
@@ -501,6 +544,15 @@ Allow admins to embed Metabase via static embedding?
 
 Allow logging in by email and password.
 
+### `MB_ENABLE_PIVOTED_EXPORTS`
+
+- Type: boolean
+- Default: `true`
+- [Exported as](../installation-and-operation/serialization.md): `enable-pivoted-exports`.
+- [Configuration file name](./config-file.md): `enable-pivoted-exports`
+
+Enable pivoted exports and pivoted subscriptions.
+
 ### `MB_ENABLE_PUBLIC_SHARING`
 
 - Type: boolean
@@ -533,13 +585,6 @@ Allow users to explore data using X-rays.
 
 Enumerated field values with cardinality at or below this point are treated as enums in the pseudo-ddl used in some model prompts.
 
-### `MB_EXPERIMENTAL_FULLTEXT_SEARCH_ENABLED`
-
-- Type: boolean
-- Default: `false`
-
-Enables search engines which are still in the experimental stage.
-
 ### `MB_FOLLOW_UP_EMAIL_SENT`
 
 - Type: boolean
@@ -593,7 +638,7 @@ Keyword setting to control whitelabeling of the help link. Valid values are `:me
 > Only available on Metabase [Pro](https://www.metabase.com/product/pro) and [Enterprise](https://www.metabase.com/product/enterprise) plans.
 
 - Type: string
-- Default: `null`
+- Default: `https://www.metabase.com/help/premium`
 - [Configuration file name](./config-file.md): `help-link-custom-destination`
 
 Custom URL for the help link.
@@ -711,7 +756,7 @@ Enable group membership synchronization with JWT.
 - Default: `null`
 - [Configuration file name](./config-file.md): `jwt-identity-provider-uri`
 
-URL of JWT based login page.
+URL for JWT-based login page. Optional if using JWT SSO only with the embedded analytics SDK.
 
 ### `MB_JWT_SHARED_SECRET`
 
@@ -919,7 +964,7 @@ don't have one.
 - [Exported as](../installation-and-operation/serialization.md): `loading-message`.
 - [Configuration file name](./config-file.md): `loading-message`
 
-Choose the message to show while a query is running.
+Choose the message to show while a query is running. Possible values are "doing-science", "running-query", or "loading-results".
 
 ### `MB_LOGIN_PAGE_ILLUSTRATION`
 
@@ -1042,6 +1087,13 @@ Options for displaying the illustration when there are no results after searchin
 
 The custom illustration for when there are no results after searching.
 
+### `MB_NOT_BEHIND_PROXY`
+
+- Type: boolean
+- Default: `false`
+
+Indicates whether Metabase is running behind a proxy that sets the source-address-header for incoming requests.
+
 ### `MB_NOTIFICATION_LINK_BASE_URL`
 
 > Only available on Metabase [Pro](https://www.metabase.com/product/pro) and [Enterprise](https://www.metabase.com/product/enterprise) plans.
@@ -1057,7 +1109,7 @@ The base URL where dashboard notitification links will point to instead of the M
 ### `MB_NOTIFICATION_THREAD_POOL_SIZE`
 
 - Type: integer
-- Default: `10`
+- Default: `2`
 
 The size of the thread pool used to send notifications.
 
@@ -1377,6 +1429,13 @@ don't have one.
 
 Is SCIM currently enabled?
 
+### `MB_SEARCH_ENGINE`
+
+- Type: keyword
+- Default: `:in-place`
+
+Which engine to use when performing search. Supported values are :in-place and :appdb.
+
 ### `MB_SEARCH_TYPEAHEAD_ENABLED`
 
 - Type: boolean
@@ -1540,6 +1599,14 @@ This URL is critical for things like SSO authentication, email links, embedding
 
 Bot user OAuth token for connecting the Metabase Slack app. This should be used for all new Slack integrations starting in Metabase v0.42.0.
 
+### `MB_SLACK_BUG_REPORT_CHANNEL`
+
+- Type: string
+- Default: `metabase-bugs`
+- [Configuration file name](./config-file.md): `slack-bug-report-channel`
+
+The name of the channel where bug reports should be posted.
+
 ### `MB_SLACK_FILES_CHANNEL`
 
 - Type: string
@@ -1828,6 +1895,15 @@ Default: `null`
 
 Used during development of third-party drivers. Set the value to have that plugin manifest get loaded during startup. Specify multiple plugin manifests by comma-separating them.
 
+### `MB_DISABLE_SCHEDULER`
+
+Type: boolean<br>
+Default: `false`
+
+When `true`, Metabase will turn off Metabase’s scheduled jobs, which include syncs, fingerprinting, and scanning, as well as dashboard subscriptions, alerts, and model caching.
+
+Can be useful for testing, or when setting up a [git-based workflow](https://www.metabase.com/learn/metabase-basics/administration/administration-and-operation/git-based-workflow).
+
 ### `MB_DISABLE_SESSION_THROTTLE`
 
 Type: boolean<br>
@@ -1887,11 +1963,9 @@ Since: v51.3
 
 If `true`, log a stack trace for any connections killed due to exceeding the timeout specified in [MB_JDBC_DATA_WAREHOUSE_UNRETURNED_CONNECTION_TIMEOUT_SECONDS](#mb_jdbc_data_warehouse_unreturned_connection_timeout_seconds).
 
-Note: In addtion to enabling this variable, you need to update the com.mchange log level to INFO or higher via a custom log4j configuration in order to see the stack traces in the logs.
+In order to see the stack traces in the logs, you'll also need to update the com.mchange log level to "INFO" or higher via a custom log4j configuration. For configuring log levels, see [Metabase log configuration](./log-configuration.md).
 
-See the [Metabase log configuration](./log-configuration.md) documentation for how to configure log levels.
-
-See [MB_JDBC_DATA_WAREHOUSE_UNRETURNED_CONNECTION_TIMEOUT_SECONDS](#mb_jdbc_data_warehouse_unreturned_connection_timeout_seconds) for setting the timeout after which connections will be killed.
+To set a timeout for how long Metabase should wait before it kills unreturned connections, see [MB_JDBC_DATA_WAREHOUSE_UNRETURNED_CONNECTION_TIMEOUT_SECONDS](#mb_jdbc_data_warehouse_unreturned_connection_timeout_seconds).
 
 ### `MB_JETTY_ASYNC_RESPONSE_TIMEOUT`
 
@@ -2165,3 +2239,4 @@ Type: string<br>
 Default: `null`
 
 Base-64 encoded public key for this sites SSL certificate. Specify this to enable HTTP Public Key Pinning. Using HPKP is no longer recommended. See http://mzl.la/1EnfqBf for more information.
+

docs/configuring-metabase/localization.md

@@ -16,37 +16,47 @@ Here you can set the default language (also called the "instance language") acro
 
 Thanks to our amazing user community, Metabase has been translated into many different languages. Due to [the way we collect translations](#translations), languages may be added or removed during major releases depending on translation coverage.
 
-The languages you can currently pick from are:
+Supported languages include:
 
-- English (default)
-- Albanian
-- Arabic
-- Bulgarian
-- Catalan
-- Chinese (simplified)
-- Chinese (traditional)
-- Czech
-- Dutch
-- Farsi/Persian
-- Finnish
-- French
-- German
-- Indonesian
-- Italian
-- Japanese
-- Korean
-- Latvian
-- Norwegian Bokmål
-- Polish
-- Portuguese
-- Russian
-- Serbian
-- Slovak
-- Spanish
-- Swedish
-- Turkish
-- Ukrainian
-- Vietnamese
+| Language               | Code    |
+| ---------------------- | ------- |
+| English                | `en`    |
+| Albanian               | `sq`    |
+| Arabic                 | `ar`    |
+| Arabic (Saudi Arabia)  | `ar-SA` |
+| Bulgarian              | `bg`    |
+| Catalan                | `ca`    |
+| Chinese (Traditional)  | `zh`    |
+| Chinese (Taiwanese)    | `zh-TW` |
+| Chinese (Hong Kong)    | `zh-HK` |
+| Chinese (Simplified)   | `zh-CN` |
+| Czech                  | `cs`    |
+| Dutch                  | `nl`    |
+| Farsi/Persian          | `fa`    |
+| Finnish                | `fi`    |
+| French                 | `fr`    |
+| German                 | `de`    |
+| Hebrew                 | `he`    |
+| Hungarian              | `hu`    |
+| Indonesian             | `id`    |
+| Malay                  | `ms`    |
+| Italian                | `it`    |
+| Japanese               | `ja`    |
+| Korean                 | `ko`    |
+| Latvian                | `lv`    |
+| Norwegian Bokmål       | `nb`    |
+| Polish                 | `pl`    |
+| Portuguese (Brazilian) | `pt-BR` |
+| Russian                | `ru`    |
+| Serbian                | `sr`    |
+| Slovak                 | `sk`    |
+| Spanish                | `es`    |
+| Swedish                | `sv`    |
+| Turkish                | `tr`    |
+| Ukrainian              | `uk`    |
+| Vietnamese             | `vi`    |
+
+The locale codes are relevant for setting the language in [static embeds](../embedding/static-embedding-parameters.md#setting-the-language-for-a-static-embed).
 
 > While Metabase can support languages that read right to left, the Metabase UI is designed around languages that read left to right.
 

docs/configuring-metabase/slack.md

@@ -1,10 +1,10 @@
 ---
-title: Slack
+title: Set up Slack
 redirect_from:
   - /docs/latest/administration-guide/09-setting-up-slack
 ---
 
-# Slack
+# Set up Slack
 
 If you want to have your [dashboard subscriptions](../dashboards/subscriptions.md) or [alerts](../questions/sharing/alerts.md) sent to Slack channels (or people on Slack), an admin must first integrate your Metabase with Slack.
 

docs/dashboards/interactive.md

@@ -1,10 +1,10 @@
 ---
-title: Interactive dashboards
+title: Dashboard interactivity
 redirect_from:
   - /docs/latest/users-guide/interactive-dashboards
 ---
 
-# Interactive dashboards
+# Dashboard interactivity
 
 You can customize what happens when people click on questions in your dashboard.
 

docs/dashboards/introduction.md

@@ -293,6 +293,10 @@ For [questions](../questions/start.md), dashboards, and [models](../data-modelin
 
 See [History](../exploration-and-organization/history.md).
 
+## Verifying a dashboard
+
+See [content verification](../exploration-and-organization/content-verification.md).
+
 ## Deleting a dashboard
 
 You can move a dashboard to Trash or permanently delete a dashboard that you no longer need.

docs/data-modeling/json-unfolding.md

@@ -68,4 +68,5 @@ For example, if you upload a CSV with JSON in it, you might need to update the d
 - [PostgreSQL](../databases/connections/postgresql.md)
 - [MySQL](../databases/connections/mysql.md)
 - [Druid (JDBC)](../databases/connections/druid.md)
-- [BigQuery](../databases/connections/bigquery.md) (always enabled)
+
+A note on [BigQuery](../databases/connections/bigquery.md): Metabase supports the [STRUCT data type](https://cloud.google.com/bigquery/docs/reference/standard-sql/data-types#struct_type) in BigQuery, but it won't unfold JSON stored in BigQuery as the `JSON` type. If your data is stored in the `STRUCT` type in BigQuery, you can query the table's nested fields. Some background here: BigQuery differs from other databases in that nested fields are _part of the table definition itself_. So when Metabase syncs with your BigQuery database, it'll be able to get metadata about any of your tables, including tables with nested fields. Querying nested fields, however, doesn't extend to arrays (REPEATED (STRUCT)) in BigQuery.

docs/data-modeling/metrics.md

@@ -21,7 +21,7 @@ You can:
 - Add metrics to [dashboards](../dashboards/introduction.md).
 - View metrics in the [database browser](../exploration-and-organization/exploration.md#browse-your-databases).
 - Pick metrics as aggregation columns in the Summarize block when creating questions, modify them or combine.
-- [Pro](https://www.metabase.com/product/pro) and [Enterprise](https://www.metabase.com/product/enterprise) plans include the ability to mark metrics as verified.
+- [Pro](https://www.metabase.com/product/pro) and [Enterprise](https://www.metabase.com/product/enterprise) plans include the ability to [mark metrics as verified](../exploration-and-organization/content-verification.md).
 
 ### Metrics in the query builder
 
@@ -86,6 +86,10 @@ By "editing" a metric, we mean [editing the metric's query definition](#editing-
 
 These collection permissions also interact with the group's [data permissions](../permissions/data.md), which define whether the group can view or query the metric's source data.
 
+## Verifying a metric
+
+See [content verification](../exploration-and-organization/content-verification.md).
+
 ## Further reading
 
 - [Models](./models.md)

docs/data-modeling/models.md

@@ -174,9 +174,7 @@ See [Deleting and restoring items](../exploration-and-organization/delete-and-re
 
 ## Verifying a model
 
-{% include plans-blockquote.html feature="Model verification" %}
-
-Just like with a question, admins can verify models. Verifying a model will give it a check mark to let others know an admin vetted the model. If anyone makes any changes to the model, the check mark will disappear. An admin will have to verify the question again to restore the check mark.
+See [content verification](../exploration-and-organization/content-verification.md).
 
 ## Model persistence
 

docs/databases/connections/databricks.md

@@ -14,22 +14,30 @@ The display name for the database in the Metabase interface.
 
 ## Host
 
-Your database's IP address, or its domain name (e.g., esc.mydatabase.com). This is the value of your Databrick's compute resource's Server Hostname.
+Your database's IP address, or its domain name (e.g., `xxxxxxxxxx.cloud.databricks.com` or `adb-xxxxx.azuredatabricks.net`). This is the value of your Databrick's compute resource's Server Hostname.
 
 See [Compute settings for the Databricks JDBC Driver](https://docs.databricks.com/en/integrations/jdbc/compute.html).
 
 ## HTTP path
 
-This is the Databrick's compute resources HTTP Path value.
+This is the Databrick's compute resources HTTP Path value. This value is often a SQL warehouse endpoint in the format `/sql/1.0/endpoints/abcdef1234567890`. See [Connect to a SQL warehouse](https://docs.databricks.com/en/compute/sql-warehouse/index.html).
 
-See [Compute settings for the Databricks JDBC Driver](https://docs.databricks.com/en/integrations/jdbc/compute.html).
+Additionally, see [Compute settings for the Databricks JDBC Driver](https://docs.databricks.com/en/integrations/jdbc/compute.html).
 
-## Personal access token
+## Authentication
 
+There are two ways to authenticate with Databricks. You can use a personal access token (PAT) or a service principal using OAuth (OAuth M2M).
+
+The Databricks driver supports both options. Use the toggle to select the authentication method you want to use.
+
+### Personal access token authentication
 See [Personal Access Token (PAT)](https://docs.databricks.com/en/dev-tools/auth/pat.html).
 
-## Catalog
+### Authenticate access with a service principal using OAuth (OAuth M2M)
 
+See [Authenticate access with a service principal using OAuth](https://docs.databricks.com/en/dev-tools/auth/oauth-m2m.html).
+
+## Catalog
 For now, you can only select one catalog. Metabase doesn't support multi-catalog connections. If you want to use more than one catalog in Metabase, you can set up multiple connections, each selecting a different catalog.
 
 You can't sync Databricks's legacy catalogs, however, including the `samples` or `hive_metastore` catalogs.
@@ -62,3 +70,45 @@ Note that only the `*` wildcard is supported; you can't use other special charac
 You can append options to the connection string that Metabase uses to connect to your database. E.g., `IgnoreTransactions=0`.
 
 See [Compute settings for the Databricks JDBC Driver](https://docs.databricks.com/en/integrations/jdbc/compute.html).
+
+## Re-run queries for simple explorations
+
+Turn this option **OFF** if people want to click **Run** (the play button) before applying any [Summarize](../../questions/query-builder/introduction.md#grouping-your-metrics) or filter selections.
+
+By default, Metabase will execute a query as soon as you choose an grouping option from the **Summarize** menu or a filter condition from the [drill-through menu](https://www.metabase.com/learn/metabase-basics/querying-and-dashboards/questions/drill-through). If your database is slow, you may want to disable re-running to avoid loading data on each click.
+
+## Choose when Metabase syncs and scans
+
+Turn this option **ON** to manage the queries that Metabase uses to stay up to date with your database. For more information, see [Syncing and scanning databases](../sync-scan.md).
+
+### Database syncing
+
+If you've selected **Choose when syncs and scans happen** > **ON**, you'll be able to set:
+
+- The frequency of the [sync](../sync-scan.md#how-database-syncs-work): hourly (default) or daily.
+- The time to run the sync, in the timezone of the server where your Metabase app is running.
+
+### Scanning for filter values
+
+Metabase can scan the values present in each field in this database to enable checkbox filters in dashboards and questions. This can be a somewhat resource-intensive process, particularly if you have a very large database.
+
+If you've selected **Choose when syncs and scans happen** > **ON**, you'll see the following options under **Scanning for filter values**:
+
+- **Regularly, on a schedule** allows you to run [scan queries](../sync-scan.md#how-database-scans-work) at a frequency that matches the rate of change to your database. The time is set in the timezone of the server where your Metabase app is running. This is the best option for a small database, or tables with distinct values that get updated often.
+- **Only when adding a new filter widget** is a great option if you want scan queries to run on demand. Turning this option **ON** means that Metabase will only scan and cache the values of the field(s) that are used when a new filter is added to a dashboard or SQL question.
+- **Never, I'll do this manually if I need to** is an option for databases that are either prohibitively large, or which never really have new values added. Use the [Re-scan field values now](../sync-scan.md#manually-scanning-column-values) button to run a manual scan and bring your filter values up to date.
+
+### Periodically refingerprint tables
+
+> Periodic refingerprinting will increase the load on your database.
+
+Turn this option **ON** to scan a sample of values every time Metabase runs a [sync](../sync-scan.md#how-database-syncs-work).
+
+A fingerprinting query examines the first 10,000 rows from each column and uses that data to guesstimate how many unique values each column has, what the minimum and maximum values are for numeric and timestamp columns, and so on. If you leave this option **OFF**, Metabase will only fingerprint your columns once during setup.
+
+## Further reading
+
+- [Managing databases](../../databases/connecting.md)
+- [Metadata editing](../../data-modeling/metadata-editing.md)
+- [Models](../../data-modeling/models.md)
+- [Setting data access permissions](../../permissions/data.md)

docs/databases/connections/mysql.md

@@ -136,6 +136,8 @@ Remember to drop the old user:
 DROP USER 'metabase'@'localhost';
 ```
 
+If you can't connect to the database, but the user, host, and password are correct, try adding `trustServerCertificate=true` to the additional JDBC options. This option will tell the Metabase driver to trust the server certificate even though it doesn't have a root certificate installed, and it should establish a secure connection.
+
 ## Syncing records that include JSON
 
 **Metabase will infer the JSON "schema" based on the keys in the first five hundred rows of a table.** MySQL JSON fields lack schema, so Metabase can't rely on table metadata to define which keys a JSON field has. To work around the lack of schema, Metabase will get the first five hundred records and parse the JSON in those records to infer the JSON's "schema". The reason Metabase limits itself to five hundred records is so that syncing metadata doesn't put unnecessary strain on your database.

docs/databases/connections/sql-server.md

@@ -89,6 +89,7 @@ A fingerprinting query examines the first 10,000 rows from each column and uses
 
 ## Further reading
 
+- [Microsoft JDBC Driver for SQL Server support matrix](https://learn.microsoft.com/en-us/sql/connect/jdbc/microsoft-jdbc-driver-for-sql-server-support-matrix)
 - [Managing databases](../../databases/connecting.md)
 - [Metadata editing](../../data-modeling/metadata-editing.md)
 - [Models](../../data-modeling/models.md)

docs/databases/ssl-certificates.md

@@ -4,7 +4,7 @@ redirect_from:
   - /docs/latest/administration-guide/secure-database-connections-with-ssl-certificates
 ---
 
-## SSL certificate
+# SSL certificate
 
 If you'd like to connect your Metabase Cloud or self-hosted instance to a database, you can secure the connection using Secure Socket Layer (SSL) encryption with a certificate.
 
@@ -15,11 +15,11 @@ Why you'd want to do this:
 
 If you're using Metabase Cloud, the application database is handled for you, so you'd only need to secure connections to data warehouses that you add to your Metabase.
 
-### Prerequisites
+## Prerequisites
 
 A database that allows a JDBC connection, as you'll need to use a connection string to specify the certificate you want to use.
 
-### Step 1: Download the root certificate from your provider
+## Step 1: Download the root certificate from your provider
 
 If you're running Metabase via a Docker container, you should already have the certificates for AWS and Azure.
 
@@ -30,7 +30,7 @@ You'll find the certificates in the `/app/certs/` directory in Metabase's Docker
 
 If you need a different certificate, you can build your own Docker image. Visit your external provider's page for your database and find a link to download the root certificate for connecting to your database.
 
-### Step 2: Save the certificate
+## Step 2: Save the certificate
 
 **Self-hosted**
 
@@ -42,15 +42,15 @@ You'll need to complete [Step 3: Add your database](#step-3-add-your-database) f
 
 Once you've done that, you can go to **Admin** > **Databases** and select your database. Find the section named **SSL Client Certificate** and click **Select a file** to upload your downloaded certificate.
 
-### Step 3: Add your database
+## Step 3: Add your database
 
 For example, let's say you want to secure a connection to a PostgreSQL database. Follow the instructions in the app to add the database. For more on setting up a database connection, check out our docs for [adding a database](./connecting.md).
 
-### Step 4: Toggle on the "Use a secure connection (SSL)" option
+## Step 4: Toggle on the "Use a secure connection (SSL)" option
 
 If your database supports a JDBC connection, Metabase will provide you with a field to input additional parameters to your connection string. Metabase will use parameters in the connection string to establish a secure connection.
 
-### Step 5: Add additional connection string options
+## Step 5: Add additional connection string options
 
 You'll need to specify the location of the certificate on the server that's running Metabase.
 

docs/databases/sync-scan.md

@@ -86,7 +86,7 @@ To prevent Metabase from running syncs and scans against a specific table, chang
 
 ## Syncing and scanning using the API
 
-Metabase syncs and scans regularly, but if the database administrator has just changed the database schema, or if a lot of data is added automatically at specific times, you may want to write a script that uses the [Metabase API](https://www.metabase.com/learn/metabase-basics/administration/administration-and-operation//metabase-api) to force a sync or scan. [Our API](../api-documentation.md) provides two ways to initiate a sync or scan of a database:
+Metabase syncs and scans regularly, but if the database administrator has just changed the database schema, or if a lot of data is added automatically at specific times, you may want to write a script that uses the [Metabase API](https://www.metabase.com/learn/metabase-basics/administration/administration-and-operation/metabase-api) to force a sync or scan. [Our API](../api-documentation.md) provides two ways to initiate a sync or scan of a database:
 
 1. Using a session token: the `/api/database/:id/sync_schema` or `api/database/:id/rescan_values` endpoints. These endpoints do the same things as going to the database in the Admin Panel and choosing **Sync database schema now** or **Re-scan field values now** respectively. To use these endpoints, you have to authenticate with a user ID and pass a session token in the header of your request.
 2. Using an API key: `/api/notify/db/:id`. We created this endpoint so that people could notify their Metabase to sync after an [ETL operation](https://www.metabase.com/learn/grow-your-data-skills/data-landscape/etl-landscape) finishes. To use this endpoint, you must pass an API key by defining the `MB_API_KEY` environment variable.

docs/databases/uploads.md

@@ -1,10 +1,10 @@
 ---
-title: Uploading data
+title: Setting up data uploads
 ---
 
-# Uploading data
+# Setting up data uploads
 
-Once you've [enabled uploads](#setting-up-uploads), you can [upload files](../exploration-and-organization/uploads.md) in CSV format to a collection in Metabase.
+This page covers how admins can set up data uploads so people can upload CSVs to your Metabase. For _how_ to upload data once this is set up, check out [Uploading data](../exploration-and-organization/uploads.md).
 
 ![Upload CSV data to a collection in Metabase](./images/upload-to-collection.png)
 

docs/developers-guide/api-changelog.md

@@ -9,6 +9,8 @@ title: API changelog
 - `POST /api/user/:id/send_invite` has been removed.
 - `GET /:id/fields` now includes the Table ID.
 
+- APIs under `/api/pulse` and `/api/alert` will be removed in a future version as we're tranitioning to a new architecture.
+
 ## Metabase 0.51.0
 
 - `GET /api/dashboard/:id/query_metadata`

docs/developers-guide/driver-changelog.md

@@ -19,6 +19,16 @@ title: Driver interface changelog
   when running Metabase to disable some of these new security checks. If your tests run into issues with Java 21
   without the flag set, try running with it set -- this might fix the problems.
 
+## Metabase 0.51.4
+
+- Another driver feature has been added: `describe-indexes`. If a driver opts-in to supporting this feature, The
+  multimethod `metabase.driver/describe-indexes` must be implemented, as a replacement for
+  `metabase.driver/describe-table-indexes`.
+
+- The multimethod `metabase.driver.sql-jdbc.sync.describe-table/describe-indexes-sql` has been added. The method needs
+  to be implemented if the driver supports `describe-indexes` and you want to use the default JDBC implementation of
+  `metabase.driver/describe-indexes`.
+
 ## Metabase 0.51.0
 
 - New optional method `metabase.driver/query-result-metadata` has been added for efficiently calculating metadata for

docs/developers-guide/drivers/driver-tests.md

@@ -194,7 +194,7 @@ There's a few other things Metabase needs to know when comparing test results. F
 
 This is actually a common problem, and luckily we have figured out how to work around it. The solution is usually something like using different _schemas_ in place of different databases, or prefixing table names with the database name, and creating everything in the same database. For SQL-based databases, you can implement `sql.tx/qualified-name-components` to have tests use a different identifier instead of what they would normally use, for example `"shared_db"."test-data_venues".id` instead of `"test-data".venues.id`. The SQL Server and Oracle test extensions are good examples of such black magic in action.
 
-# Setting up CI
+## Setting up CI
 
 Once you have all the tests passing, you'll need to set up GitHub Actions to run those tests against your driver. You'll need to add a new job to [`.github/workflows/drivers.yml`](https://github.com/metabase/metabase/blob/master/.github/workflows/drivers.yml) to run tests against your database.
 

docs/developers-guide/internationalization.md

@@ -27,7 +27,7 @@ and in the backend using `trs` (to use the site language) or `tru` (to use the c
 
 If you see incorrect or missing strings for your language, please visit our [POEditor project](https://poeditor.com/join/project/ynjQmwSsGh) and submit your fixes there.
 
-# Backend Translation Guide
+## Backend Translation Guide
 
 Metabase allows for translations into many languages. An authoritative list can be found in `resources/locales.clj`.
 

docs/developers-guide/sdk.md

@@ -1,77 +0,0 @@
----
-title: Developing the Embedded analytics SDK
----
-
-# Developing the Embedded analytics SDK
-
-These docs are for developing the SDK. For using the SDK in your app, see our [SDK docs](../embedding/sdk/introduction.md).
-
-## Building locally
-
-First you need to build the Metabase Embedding SDK for React locally:
-
-```bash
-yarn build-release:cljs
-```
-
-## Build and watch
-
-And then run:
-
-```bash
-yarn build-embedding-sdk:watch
-```
-`build-embedding-sdk:watch` is the original command, the js output is fast, but the dts output is extremely slow and is not fixed by the fixup script on watch.
-
-## Build incrementally
-
-```bash
-yarn build-embedding-sdk:dev
-```
-
-This is an _experimental_ command that should be much faster, it uses `tsc --incremental` to to generate the dts files and fixes them automatically by running the fixup script on watch.
-
-The `tsc` command will output a lot of errors, to keep the terminal output under control you may want to run the three different `embedding-sdk:dev:*` commands on different terminals.
-There is a VS code task named `Run embedding sdk dev commands` that does that
-
-## Storybook
-
-You can use storybook to run SDK components during local development.
-
-When you have Metabase instance running:
-
-```bash
-yarn storybook-embedding-sdk
-```
-
-## Initial configuration
-
-1. Set JWT secret to be "`0000000000000000000000000000000000000000000000000000000000000000`" in Admin > Authentication >
-   JWT > String used by the JWT signing key
-1. Make sure "User Provisioning" setting is set to "`on`".
-1. Set Authorized Origins to "`*`" in Admin > Embedding > Interactive embedding
-
-## Using the local build
-
-After that you need to add this built SDK package location to your package.json. In this example we assume that your
-application is located in the same directory as Metabase directory:
-
-```json
-"dependencies": {
-"@metabase/embedding-sdk-react": "file:../metabase/resources/embedding-sdk"
-}
-```
-
-And then you can install the package using npm or yarn:
-
-```bash
-npm install
-# or
-yarn
-```
-
-## Releases
-
-Embedding SDK package build happens with Github actions if `embedding-sdk-build` label has been set on the PR.
-
-Published package will use a version from `package.template.json` + current date and commit short hash.

docs/developers-guide/start.md

@@ -10,7 +10,7 @@ This guide contains detailed information on how to work on Metabase codebase.
 
 ## Contributing
 
-- [How to contribute back to the Metabase project](contributing.md)
+- [How to contribute back to the Metabase project](../CONTRIBUTING.md)
 
 ## Setup and build
 
@@ -33,7 +33,7 @@ This guide contains detailed information on how to work on Metabase codebase.
 ## API documentation
 
 - [Autogenerated API docs](../api-documentation.md)
-- [Working with the Metabase API](https://www.metabase.com/learn/metabase-basics/administration/administration-and-operation//metabase-api.html)
+- [Working with the Metabase API](https://www.metabase.com/learn/metabase-basics/administration/administration-and-operation/metabase-api)
 - [Driver Interface Changelog](driver-changelog.md)
 - [MBQL Library Changelog](mbql-library-changelog.md)
 

docs/embedding/interactive-embedding-quick-start-guide.md

@@ -8,6 +8,8 @@ redirect_from:
 
 You'll embed the full Metabase application in your app. Once logged in, people can view a Metabase dashboard in your web app, and be able to use the full Metabase application to explore their data, and only their data.
 
+{% include shared/in-page-promo.html %}
+
 ## Prerequisites
 
 - You have an app that you can embed Metabase in.

docs/embedding/interactive-embedding.md

@@ -9,6 +9,8 @@ redirect_from:
 
 {% include plans-blockquote.html feature="Interactive embedding" %}
 
+{% include shared/in-page-promo.html %}
+
 **Interactive embedding** is what you want if you want to offer [multi-tenant, self-service analytics](https://www.metabase.com/learn/metabase-basics/embedding/multi-tenant-self-service-analytics).
 
 Interactive embedding is the only type of embedding that integrates with your [permissions](../permissions/introduction.md) and [SSO](../people-and-groups/start.md#authentication) to give people the right level of access to [query](https://www.metabase.com/glossary/query_builder) and [drill-down](https://www.metabase.com/learn/metabase-basics/querying-and-dashboards/questions/drill-through) into your data.
@@ -273,13 +275,13 @@ To hide a question or dashboard's title, [additional info](#additional_info), an
 
 ### `locale`
 
-You can localize the user interface via a parameter. For example, to set the locale to Spanish:
+You can change the language of the user interface via a parameter. For example, to set the locale to Spanish:
 
 ```
-locale=es-ES
+locale=es
 ```
 
-Check out the [locales Metabase supports](https://github.com/metabase/metabase/tree/master/locales). And read more about [localization](../configuring-metabase/localization.md).
+Read more about [localization](../configuring-metabase/localization.md).
 
 ### `logo`
 

docs/embedding/introduction.md

@@ -10,6 +10,8 @@ You can embed Metabase tables, charts, and dashboards—even Metabase's query bu
 
 Here are the different ways you can embed Metabase.
 
+{% include shared/in-page-promo.html %}
+
 ## Embedding SDK with React (BETA)
 
 With the [Embedding SDK](./sdk/introduction.md), you can embed individual Metabase components with React (like standalone charts, dashboards, the query builder, and more). You can manage access and interactivity per component, and you have advanced customization for seamless styling.
@@ -26,7 +28,7 @@ Interactive embedding is the only kind of embedding that [integrates with SSO an
 
 Also known as signed embedding, [static embedding](./static-embedding.md) is a secure way to embed charts and dashboards.
 
-**When to use static embedding**: you don’t want to give people ad hoc query access to their data for whatever reason, or you want to present data that applies to all of your tenants at once. For example, say you want to showcase some benchmarking stats: if you just want to make those stats available exclusively to your customers, you could use a signed embed.
+**When to use static embedding**: you don't want to offer ad-hoc querying or chart drill-through. To filter data relevant to the viewer, you can use static embeds with [locked parameters](./static-embedding-parameters.md#locked-parameters-limit-the-values-available-to-other-editable-parameters).
 
 ## Public links and embeds
 

docs/embedding/sdk/appearance.md

@@ -6,16 +6,16 @@ title: "Embedded analytics SDK - appearance"
 
 {% include beta-blockquote.html %}
 
-{% include plans-blockquote.html feature="Embedded analytics SDK" sdk=true %}
+{% include plans-blockquote.html feature="Embedded analytics SDK" sdk=true enterprise-only=true %}
 
 You can style your embedded Metabase components with a theme.
 
 Here's an example that includes the various styling options available:
 
 ```js
-import {defineEmbeddingSdkTheme} from "@metabase/embedding-sdk-react";
+import { defineMetabaseTheme } from "@metabase/embedding-sdk-react";
 
-const theme = defineEmbeddingSdkTheme({
+const theme = defineMetabaseTheme({
   // Specify a font to use from the set of fonts supported by Metabase.
   // You can set the font to "Custom" to use the custom font
   // configured in your Metabase instance.
@@ -97,6 +97,10 @@ const theme = defineEmbeddingSdkTheme({
       // Background color for all dashboards
       backgroundColor: "#2F3640",
 
+      // Border color of the dashboard grid, shown only when editing dashboards.
+      // Defaults to `colors.border`
+      gridBorderColor: "#EEECEC",
+
       card: {
         // Background color for all dashboard cards
         backgroundColor: "#2D2D30",
@@ -113,6 +117,21 @@ const theme = defineEmbeddingSdkTheme({
       backgroundColor: "#2D2D30",
     },
 
+    // Tooltips
+    tooltip: {
+      // Tooltip text color.
+      textColor: "#FFFFFF",
+
+      // Secondary text color shown in the tooltip, e.g. for tooltip headers and percentage changes.
+      secondaryTextColor: "#949AAB",
+
+      // Tooltip background color.
+      backgroundColor: "#2E353B",
+
+      // Tooltip background color for focused rows.
+      focusedBackgroundColor: "#0A0E10",
+    },
+
     // Data table
     table: {
       cell: {
@@ -188,13 +207,15 @@ const theme = defineEmbeddingSdkTheme({
 
 ### Customizing loader and error components
 
-You can provide your own components for loading and error states by specifying `loaderComponent` and `errorComponent` in the config.
+You can provide your own components for loading and error states by specifying `loaderComponent` and `errorComponent` as props to `MetabaseProvider`.
 
 ```tsx
-import { defineEmbeddingSdkConfig } from "@metabase/embedding-sdk-react";
+import { MetabaseProvider, StaticDashboard } from "@metabase/embedding-sdk-react";
 
-const config = defineEmbeddingSdkConfig({
-  loaderComponent: () => <div>Analytics is loading...</div>,
-  errorComponent: ({ message }) => <div>There was an error: {message}</div>,
-});
+<MetabaseProvider
+  loaderComponent={() => <div>Analytics is loading...</div>}
+  errorComponent={({ message }) => <div>There was an error: {message}</div>}
+>
+  <StaticDashboard dashboardId={1} />
+</MetabaseProvider>
 ```

docs/embedding/sdk/authentication.md

@@ -6,7 +6,7 @@ title: Embedded analytics SDK - authentication
 
 {% include beta-blockquote.html %}
 
-{% include plans-blockquote.html feature="Embedded analytics SDK" sdk=true %}
+{% include plans-blockquote.html feature="Embedded analytics SDK" sdk=true enterprise-only=true %}
 
 Notes on handling authentication when working with the SDK.
 
@@ -155,7 +155,7 @@ First, create an [API key](../../people-and-groups/api-keys.md).
 Then you can then use the API key to authenticate with Metabase in your application. All you need to do is include your API key in the config object using the key: `apiKey`.
 
 ```typescript
-const metabaseConfig = {
+const authConfig = {
     ...
     apiKey: "YOUR_API_KEY"
     ...
@@ -163,7 +163,7 @@ const metabaseConfig = {
 
 export default function App() {
   return (
-    <MetabaseProvider config={metabaseConfig} className="optional-class">
+    <MetabaseProvider authConfig={authConfig} className="optional-class">
       Hello World!
     </MetabaseProvider>
   );