v0.15.0 — safer verdicts and smoother contributions

dbt-plan v0.15.0 — safer verdicts and smoother contributions

Highlights

• Use custom target directories with run, the GitHub Action, and MCP.
• Get an explicit warning when a baseline cannot be read, and avoid false safe
  MCP verdicts when analysis refusals remain.
• Pipe run --format json into other tools without snapshot progress corrupting stdout.
• Catch deleted models even when old compiled files remain, and detect broken
  references through downstream SELECT * chains and aliased relations.
• Read shorter data-test names in human output while retaining full names in JSON.

Contributor experience

PRs to dbt-plan now get an automatically updated CI status comment with failure
links. Authors can use /ci to refresh status and /ci retry for transient
failures. External code still needs maintainer execution approval.
See the contribution guide.

Thanks to our contributors

Thank you for making dbt-plan more reliable and easier to use:

• @Akimbo92i — forward run acknowledgements to check (#125).
• @LuizPiccini — regression tests for cascade risk severity names (#126).
• @MuhammadWaleed12 — prevent false safe MCP verdicts (#137).
• @mikemikimike — custom target-directory support (#172).
• @proobker — parseable JSON stdout and explicit unreadable-baseline warnings (#175, #176).
• @1cbyc — explain missing verdicts in agent setup guidance (#178).
• @be-student — readable data-test names and the JSON output contract (#179, #180).
• @pushnanashi2 — run generated CI for every PR (#181).

Upgrade notes

Some cases that previously exited successfully now warn because analysis could
not establish safety. Review the warning rather than treating it as a regression.
Existing generated workflows must be regenerated to pick up the removal of path
filters. The contributor status bot is specific to this repository; it is not
installed into consumer projects.

pip install --upgrade dbt-plan==0.15.0

Full changelog: v0.14.0...v0.15.0