1.6.0 - 2026-11-18
Added
- Add opt-in direct-column rename documentation inheritance through SQLGlot lineage with the
use-sqlglot-lineagesetting (#466).
- DuckDB and Trino SQL dialects are supported conservatively; explicit descriptions and raw docs-block references are preserved.
- Expressions, aggregates and ambiguous donors do not automatically inherit descriptions. Trino coverage is offline, not a warehouse certification.
Fixed
- Restore staging-generator compatibility with dbt-core-interface output keys and honor generated model names (#451).
- Keep package-owned YAML patches outside default YAML management and distinguish shared ancestors from actual dependency cycles (#443, #452, #455).
- Resolve legacy source metadata correctly, preserve source-column configuration scope, and avoid trailing whitespace when wrapping plain YAML scalars (#456, #458).
- Validate supplied catalog artifacts and consumed database identifiers before YAML mutation, with actionable CLI diagnostics (#467, #469).
Changed
- Add blocking Python dbt Core 1.12 compatibility coverage and refresh validated Python, build and documentation dependencies (#459–#463).
- Document catalog input and engine-support boundaries (#471). Osmosis still requires the Python dbt runtime: accepting a compatible catalog is not a manifest-only/offline mode or broad Fusion certification.
Security
- Refresh Pillow and documentation dependencies and update the PyPI publishing action to its patched release (#457, #461, #463).
This is not a security-clean release: existing transitive advisories remain in the shipped uv.lock. The base wheel does not pin those transitive versions. The optional workbench on Python 3.10 cannot install the patched Pillow 13 release, which requires Python 3.11 or later; no Python support policy changes are made here.
The docs-only transitive picomatch advisory GHSA-fc5q-39xc-vjpf remains open with no patched release as of November 18. This release does not claim to remediate it; picomatch is not a Python wheel runtime dependency.