v0.2.55
LATESTADOPTING DVT, ONE COMMAND
Found live, in the founder's own demo: a dbt project that existed before DVT has no dvt_project.yml — dvt init rightly refuses to touch an existing project, but config-checkup answered 'every config tells the truth' over a file that didn't exist at all, leaving every DVT decision (compute path, suite port, AI, telemetry) running on silent defaults with no written record. A missing key was always a finding; a missing file was invisible. Now the file itself is the finding, and one dvt config-fix writes the complete init scaffold — every key at its real default, each with the comment that teaches it, named after your project. Adopting DVT in an existing dbt project is now: install, config-fix, done.
FIXED
- ▸A project without dvt_project.yml produced no checkup finding — the missing-key detection only ran when the file existed. The absent file is now a finding of its own, stating exactly what runs on silent defaults while it's missing.
- ▸config-fix restores the whole file, not just keys: the complete dvt init scaffold from the same template init uses (one home — the two can never drift), written only if the file is still absent, and named from your dbt_project.yml.
Get it: pip install dvt-core==0.2.55 · wheels on PyPI for macOS (arm64 + x86_64) and Linux x86_64, Python 3.10–3.14 — the full platform matrix.