dbt-core 2.0.2 - Docs UI Restored in Python Wheels

dbt-core tag v2.0.2 was published on 15 September 2026 at 16:08 UTC. The patch puts the bundled docs UI back into the Python wheel. With that bundle present, dbt docs generate produces a working docs site again for dbt installed with pip.

The full release notes and downloads are on the GitHub release page.

The changelog for this tag is one line. It restores the bundled docs UI in the Python wheel builds. The words “restore” and “again” mark a regression repair. The published text adds no docs feature, no CLI flag, and no change to how models are built or tested.

dbt docs generate writes the static site a reviewer opens for model descriptions, tests, and lineage. That site is the bundled UI plus the project metadata the command emits. With the UI files absent from the installed package, generate has no frontend to place beside that metadata, and the site stays unusable. The notes place the omission in the wheel build. Current pip selects that wheel when the index publishes one. A git tree can still hold the UI files. The wheel that pip fetches can omit them. Same dbt entry point, two different file sets on disk. This tag puts the UI files into the wheel.

The build backend, the include list, and the asset path are absent from the notes. Treat the layout of files inside the wheel as unpublished detail. The contract on the page is narrower. Wheel builds of this tag include the docs UI, and dbt docs generate produces a working site for dbt installed with pip.

The named audience is dbt installed with pip. That covers a direct pip install of the wheel. It also covers a lockfile that pins the same wheel. uv, Poetry, and pip-tools resolve to a wheel when the index serves one. A lockfile that still records a build from before this tag keeps the broken site until the pin moves to v2.0.2.

Source checkouts and editable installs read files from a working tree. This release rebuilds the wheel, so those layouts stay on whatever the tree already contained. A CI image that copies the repo and installs editable picks up the fix only after the image build starts installing the v2.0.2 wheel.

Commands outside docs generation sit outside this changelog. dbt run, dbt build, and dbt test go unmentioned. The notes talk about the docs site and leave catalog and manifest behavior unmentioned. People who open the site after generate are the ones who see the repair.

Pin the distribution as dbt-core==2.0.2. The git tag is v2.0.2, with a leading v. The version string pip matches is 2.0.2.

Install v2.0.2 into a clean environment, or purge the wheel cache before installing into an existing one. A warm cache is a common way to think you upgraded while the old wheel still runs. Check that the installed distribution reports 2.0.2 before you judge dbt docs generate.

Run dbt docs generate on a project whose last site would not open. Serve the result with dbt docs serve and load the page. A working UI means the wheel shipped the bundle and generate copied it into the output, usually under target/. A blank interface means the process is still on an older wheel, or a proxy is still serving one. Correct the artifact source before you open a follow up issue.

The rollout is a reinstall plus a fresh dbt docs generate. The notes list no dbt_project.yml edit and no profiles edit. No env var is part of the fix.

A docs job in CI is the practical canary. The job installs dbt-core, runs generate, and publishes the static output. Once the runner resolves 2.0.2, that artifact should open as a site. A job that only archives manifest.json for an external catalog has no new file called out in these notes. Keep that job on its current check. Spend the upgrade attention on the job that is supposed to serve HTML.

Putting the UI back into the wheel costs bytes. The artifact grows by the weight of the static frontend, and the notes publish no size. CI jobs that download dbt-core on every run pay those bytes on the install step. In return, generate can emit the site from files already inside the installed package. Air gapped runners beside a private warehouse can write the docs site without a second download at generate time.

mishamsk is the credited author. The notes stop at that credit and the one fix. The GitHub release page is the full public record for this tag.

The changelog URL is the dbt-labs/dbt release path above. The source tree is the dbt-labs/dbt-core repository linked in the list. Keep those two paths distinct when you script a fetch.