dbt-plan v0.18.2 — keep separate warnings visible in summaries

dbt-plan v0.18.2 — keep separate warnings visible in summaries

Text and GitHub reports now put report-wide review status before model rows and
append it to the final summary. A safe model DDL operation no longer leaves the
reader with a final 0 warning count without the separate review status.

Upgrade

pip install --upgrade dbt-plan==0.18.2
# For the optional MCP server:
pip install --upgrade 'dbt-plan[mcp]==0.18.2'

What changes

• A report with safe replacement DDL and an unreadable downstream read starts
  with Review required: WARNING and ends with
  overall review: WARNING (before policy).
• Next actions cover unresolved SQL/columns, incomplete or mismatched artifacts,
  stale sources and missing/corrupt historical baselines. Repeated actions are
  deduplicated. Unknown evidence still requires review.
• Reports show ignored models as not checked and limit no-risk statements to
  supplied artifacts. This is not full project coverage accounting.

Compatibility

JSON fields, model DDL counts, canonical findings, graph evidence, MCP verdicts
and CLI exit policy retain their meaning. summary.warning counts model
predictions, not every finding. Human text gains a status section and a suffix
on its grepable dbt-plan: summary; machine consumers should use JSON.

The new status reuses the existing standard-library-only MCP/CI report consumer.
The base CLI does not require the optional MCP dependency. Acknowledging a risk
or choosing --fail-on never can permit exit 0 without changing raw review status.
Execution errors still exit 3 and do not produce a completed report.

No warehouse behavior, expanded adapter support, pilot adoption or usability
improvement is claimed. The package release does not move the Marketplace v1
tag. See reading review status.

Full changelog