metabase · github-automation-metabase · Jul 23, 2025 · Jul 22, 2025
diff --git a/_docs/latest/databases/connections/bigquery.md b/_docs/latest/databases/connections/bigquery.md
@@ -170,6 +170,12 @@ If you're having trouble with your BigQuery connection, you can check out this [
 
 There aren't (yet) any model features available for BigQuery.
 
+## Database routing
+
+Database routing for BigQuery works between BigQuery **projects** with identical schemas.
+
+See [Database routing](../../permissions/database-routing).
+
 ## Danger zone
 
 See [Danger zone](../danger-zone).

diff --git a/_docs/latest/developers-guide/driver-changelog.md b/_docs/latest/developers-guide/driver-changelog.md
@@ -13,6 +13,29 @@ latest: true
 
 # Driver Interface Changelog
 
+## Metabase 0.56.0
+
+- Add the testing multi-method `tx/track-dataset` for shared cloud dbs to track loaded datasets for more efficient sharing.
+
+- Join alias escaping has been reworked; when compiling MBQL for a join please use
+  `metabase.driver-api.core/qp.add.alias` instead of `:join-alias`. (This is mostly relevant if you have a custom
+  `metabase.driver.sql.query-processor/join->honeysql` implementation.)
+
+  Join aliases are no longer globally unique by default, but instead unique within a given level of a query. If you
+  need globally unique join aliases, you can pass the new `{:globally-unique-join-aliases? true}` option to
+  `driver-api/add-alias-info`.
+
+  Also note that `driver-api/add-alias-info` only adds additional keys to field refs and join maps, and does not
+  replace existing keys like `:alias`, `:join-alias`, or `:name`; make sure you use `driver-api/qp.add.alias`,
+  `driver-api/qp.add.source-table`, and `driver-api/qp.add.source-alias` respectively.
+
+- Added the driver multi-method `driver/extra-info` for drivers to provide info such as db routing configuration details
+  from their `metabase-plugin.yaml` file.
+
+- Extend `datetime()` to accept UTF-8 encoded binary and numbers (unix timestamps) in addition to strings.
+
+- Added a feature `:expressions/today` for drivers that support generating a date for the current day.
+
 ## Metabase 0.55.0
 
 - Add the multi-method `->date` that allows the driver to control how to cast strings and temporal types to dates.

diff --git a/_docs/latest/embedding/sdk/upgrade.md b/_docs/latest/embedding/sdk/upgrade.md
diff --git a/_docs/latest/embedding/sdk/version.md b/_docs/latest/embedding/sdk/version.md
@@ -16,32 +16,35 @@ latest: true
 
 The SDK stable version tracks with the Metabase version.
 
-So, for example, if you're on Metabase 55 (`0.55.x`, `1.55.x`), _any_ version 0.55.x of the @metabase/embedding-sdk-react npm package will be compatible.
+So, for example, if you're on Metabase 53 (`0.53.x`, `1.53.x`), _any_ version 0.53.x of the @metabase/embedding-sdk-react npm package will be compatible.
 
-To simplify things, we publish dist-tags for each stable Metabase version. For example, to install the latest version of the SDK compatible with Metabase 55, run:
+To simplify things, we publish dist-tags for each stable Metabase version. For example, to install the latest version of the SDK compatible with Metabase 53, run:
 
 ```sh
-npm install @metabase/embedding-sdk-react@55-stable
+npm install @metabase/embedding-sdk-react@53-stable
 ```
 
 To grab the latest version of the SDK that works with Metabase nightly builds, use the `canary` dist-tag.
 
 ## Minimum SDK version
 
-Version 52 is the minimum version supported for the Embedded analytics SDK.
+52 is the minimum version supported for the Embedded analytics SDK.
 
-## Instances on Metabase Cloud will be pinned to a specific version
+## Version pinning when using the SDK with Metabase Cloud
 
-By default, if you're running on Metabase Cloud and using the Embedded analytics SDK, we'll pin your version to avoid breaking changes. 
+To pin your version of Metabase, go to **Admin settings > Settings > Embedding**. Go to the Embedded analytics SDK card and scroll to **Version pinning** and click **Request version pinning**.
 
-Normally, Metabase Cloud upgrades your Metabase as new versions roll out so you don't have to deal with upgrades. But if you're using the SDK with Metabase Cloud, you'll want to upgrade manually to make sure your embeds don't break when you upgrade both your Metabase and your SDK version.
+## Version pinning requirements
 
-### Manually pinning your instance version on Metabase Cloud
+To pin a version of Metabase, you must:
 
-To manually pin your version of Metabase:
+- Be on Metabase Cloud (obviously)
+- Be on the Pro or Enterprise plans
 
-1. Go to **Admin settings > Settings > Embedding**.
-2. Go to the Embedded analytics SDK card.
-3. Scroll to **Version pinning** and click **Request version pinning**.
+## Why you'd want to pin your Metabase Cloud version
 
-This will open a mailto link to our support team.
+Normally, Metabase Cloud upgrades your Metabase as new versions roll out so that you don't have to deal with upgrades.
+
+But if you're using the SDK with Metabase Cloud, you'll want to upgrade manually to make sure your embeds don't break when you upgrade both your Metabase and your SDK version.
+
+To upgrade manually, you can pin your Metabase version so that it stays in sync with the SDK version you're using. That way you can choose when to upgrade your Metabase.
diff --git a/_docs/latest/installation-and-operation/upgrading-metabase.md b/_docs/latest/installation-and-operation/upgrading-metabase.md
@@ -15,15 +15,11 @@ latest: true
 
 # Upgrading Metabase
 
-This page covers how to upgrade to a new Metabase release.
-
-- [Announcement posts for major releases](https://www.)
-- [Changelogs](/changelog).
-- [Release notes on GitHub](https://github.com/metabase/metabase/releases).
+This page covers how to upgrade to a new [Metabase release](https://github.com/metabase/metabase/releases).
 
 ## Upgrading Metabase Cloud
 
-If you're on a [Metabase Cloud](/pricing/) plan, we'll upgrade your Metabase automatically with each new release; no action needed on your end ([unless you're using the Embedded analytics SDK](#instances-using-the-embedded-analtyics-sdk-on-metabase-cloud-must-request-an-upgrade)).
+If you're on a [Metabase Cloud](/pricing/) plan, we'll upgrade your Metabase automatically with each new release; no action needed on your end. 
 
 How soon we upgrade you depends on the type of release:
 
@@ -32,14 +28,6 @@ How soon we upgrade you depends on the type of release:
 
 Cloud customers can request an early upgrade by emailing support at help@metabase.com. Include the URL of the Metabase you want us to upgrade.
 
-### Instances using the Embedded analtyics SDK on Metabase Cloud must request an upgrade
-
-If you're using the [Embedded analytics SDK](../embedding/sdk/introduction) on Metabase Cloud, we pin your version so that it doesn't upgrade automatically, as you should test the changes before upgrading. 
-
-To upgrade your Metabase, you'll need to request an upgrade by [contacting support](/help-premium).
-
-See our [upgrade guide for the Embedded analytics SDK](../embedding/sdk/upgrade).
-
 ## Upgrading a self-hosted Metabase
 
 Here are the steps for upgrading to a new Metabase version (major or minor):

diff --git a/_docs/latest/permissions/database-routing.md b/_docs/latest/permissions/database-routing.md
@@ -29,6 +29,7 @@ Database routing is useful for:
 
 ## Databases that support database routing
 
+- [BigQuery](../databases/connections/bigquery)
 - [Druid](../databases/connections/druid)
 - [MongoDB](../databases/connections/mongodb)
 - [MariaDB](../databases/connections/mariadb)

diff --git a/_docs/v0.55/databases/connections/bigquery.md b/_docs/v0.55/databases/connections/bigquery.md
@@ -168,6 +168,12 @@ If you're having trouble with your BigQuery connection, you can check out this [
 
 There aren't (yet) any model features available for BigQuery.
 
+## Database routing
+
+Database routing for BigQuery works between BigQuery **projects** with identical schemas.
+
+See [Database routing](../../permissions/database-routing).
+
 ## Danger zone
 
 See [Danger zone](../danger-zone).

diff --git a/_docs/v0.55/developers-guide/driver-changelog.md b/_docs/v0.55/developers-guide/driver-changelog.md
@@ -11,6 +11,29 @@ layout: new-docs
 
 # Driver Interface Changelog
 
+## Metabase 0.56.0
+
+- Add the testing multi-method `tx/track-dataset` for shared cloud dbs to track loaded datasets for more efficient sharing.
+
+- Join alias escaping has been reworked; when compiling MBQL for a join please use
+  `metabase.driver-api.core/qp.add.alias` instead of `:join-alias`. (This is mostly relevant if you have a custom
+  `metabase.driver.sql.query-processor/join->honeysql` implementation.)
+
+  Join aliases are no longer globally unique by default, but instead unique within a given level of a query. If you
+  need globally unique join aliases, you can pass the new `{:globally-unique-join-aliases? true}` option to
+  `driver-api/add-alias-info`.
+
+  Also note that `driver-api/add-alias-info` only adds additional keys to field refs and join maps, and does not
+  replace existing keys like `:alias`, `:join-alias`, or `:name`; make sure you use `driver-api/qp.add.alias`,
+  `driver-api/qp.add.source-table`, and `driver-api/qp.add.source-alias` respectively.
+
+- Added the driver multi-method `driver/extra-info` for drivers to provide info such as db routing configuration details
+  from their `metabase-plugin.yaml` file.
+
+- Extend `datetime()` to accept UTF-8 encoded binary and numbers (unix timestamps) in addition to strings.
+
+- Added a feature `:expressions/today` for drivers that support generating a date for the current day.
+
 ## Metabase 0.55.0
 
 - Add the multi-method `->date` that allows the driver to control how to cast strings and temporal types to dates.

diff --git a/_docs/v0.55/embedding/sdk/upgrade.md b/_docs/v0.55/embedding/sdk/upgrade.md
diff --git a/_docs/v0.55/embedding/sdk/version.md b/_docs/v0.55/embedding/sdk/version.md
@@ -15,32 +15,35 @@ layout: new-docs
 
 The SDK stable version tracks with the Metabase version.
 
-So, for example, if you're on Metabase 55 (`0.55.x`, `1.55.x`), _any_ version 0.55.x of the @metabase/embedding-sdk-react npm package will be compatible.
+So, for example, if you're on Metabase 53 (`0.53.x`, `1.53.x`), _any_ version 0.53.x of the @metabase/embedding-sdk-react npm package will be compatible.
 
-To simplify things, we publish dist-tags for each stable Metabase version. For example, to install the latest version of the SDK compatible with Metabase 55, run:
+To simplify things, we publish dist-tags for each stable Metabase version. For example, to install the latest version of the SDK compatible with Metabase 53, run:
 
 ```sh
-npm install @metabase/embedding-sdk-react@55-stable
+npm install @metabase/embedding-sdk-react@53-stable
 ```
 
 To grab the latest version of the SDK that works with Metabase nightly builds, use the `canary` dist-tag.
 
 ## Minimum SDK version
 
-Version 52 is the minimum version supported for the Embedded analytics SDK.
+52 is the minimum version supported for the Embedded analytics SDK.
 
-## Instances on Metabase Cloud will be pinned to a specific version
+## Version pinning when using the SDK with Metabase Cloud
 
-By default, if you're running on Metabase Cloud and using the Embedded analytics SDK, we'll pin your version to avoid breaking changes. 
+To pin your version of Metabase, go to **Admin settings > Settings > Embedding**. Go to the Embedded analytics SDK card and scroll to **Version pinning** and click **Request version pinning**.
 
-Normally, Metabase Cloud upgrades your Metabase as new versions roll out so you don't have to deal with upgrades. But if you're using the SDK with Metabase Cloud, you'll want to upgrade manually to make sure your embeds don't break when you upgrade both your Metabase and your SDK version.
+## Version pinning requirements
 
-### Manually pinning your instance version on Metabase Cloud
+To pin a version of Metabase, you must:
 
-To manually pin your version of Metabase:
+- Be on Metabase Cloud (obviously)
+- Be on the Pro or Enterprise plans
 
-1. Go to **Admin settings > Settings > Embedding**.
-2. Go to the Embedded analytics SDK card.
-3. Scroll to **Version pinning** and click **Request version pinning**.
+## Why you'd want to pin your Metabase Cloud version
 
-This will open a mailto link to our support team.
+Normally, Metabase Cloud upgrades your Metabase as new versions roll out so that you don't have to deal with upgrades.
+
+But if you're using the SDK with Metabase Cloud, you'll want to upgrade manually to make sure your embeds don't break when you upgrade both your Metabase and your SDK version.
+
+To upgrade manually, you can pin your Metabase version so that it stays in sync with the SDK version you're using. That way you can choose when to upgrade your Metabase.