Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions guides/developer/ai-writeback-self-hosting.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -42,12 +42,14 @@ Restart the backend. Users with AI Analyst access on a project connected to a su

## Supported dbt versions

The writeback sandbox runs `lightdash compile` using the dbt version configured on the project, so validation behaves the same way it would locally. The sandbox ships with dbt **1.8, 1.9, 1.10, and 1.11** preinstalled:
The writeback sandbox runs `lightdash compile` using the dbt version configured on the project, so validation behaves the same way it would locally. The sandbox ships with dbt **1.8, 1.9, 1.10, 1.11, and 1.12** preinstalled:

- Projects pinned to one of those versions compile against that exact version.
- Projects set to `latest` compile against the newest available version (currently 1.11).
- Projects set to `latest` compile against the newest version with full adapter coverage (currently 1.11). `latest` intentionally does not track 1.12 while some adapters — notably Databricks — lack a 1.12-compatible release; to use 1.12 today, pin the project to it explicitly.
- Projects pinned to a version below 1.8 (which is end-of-life upstream) are clamped up to 1.8 inside the sandbox.

At the time of writing, no stable `dbt-core` 1.12 is published to PyPI, so the 1.12 venv pins the latest pre-releases (`dbt-core==1.12.0rc1`, plus pre-release Snowflake and BigQuery adapters). Adapters without a 1.12-compatible release — including Databricks — stay on their existing 1.10/1.11-era pins inside the 1.12 venv.

You don't need to configure anything — the version is selected automatically from the project's dbt connection settings.

## Costs
Expand Down
Loading