dbt docs selection can expand when compile is skipped

A selected documentation build should have a predictable scope. An open dbt issue reports that docs generate with select and no-compile queries all schemas and includes the full catalog, although the selected path without no-compile scopes correctly. For teams using docs builds as controlled publishing jobs, that difference matters.

Compare requested and generated scope

Run a small fixture with two unrelated model groups. Capture the command, dbt version, adapter, catalog entries, and warehouse queries for both the normal selected build and the no-compile variant. Check the generated artifact, not just a successful exit code.

Put an artifact gate before publishing

Assert the expected model and source set before copying generated docs to a shared location. A job that exits zero but publishes an overbroad catalog should fail the gate. Keep logs free of sensitive relation names where the audience is wider than the warehouse team.

Choose a temporary safe path

If the installed version reproduces the report, use a verified build mode or prebuilt scoped artifact. Track the upstream issue and test any fix against the same fixture. Document the additional compile cost rather than silently broadening the catalog.

Adovo’s view

Documentation is a data product with an audience and a boundary. A flag combination that changes that boundary deserves the same release gate as a table permission change. Publish what was selected, and prove the artifact says so.