1.4.0

Changed

• Use dbterd 1.28's built-in JSON ERD target instead of a custom registered target. The ERD now consumes dbterd's schema-validated {nodes, edges, metadata} contract directly, with short-name edge ids resolved back to unique_ids and missing foreign-key flags back-filled. (#4)

Full changelog: 1.3.0...1.4.0

1.3.0

Features

• Full-text search across the docs site — instant client-side search powered by the vendored MiniSearch.
• Complete dbt-project-evaluator health rule parity — the Health Check now covers all six DPE dimensions (testing, modeling, documentation, structure, performance, governance) via a configurable, pluggable rule engine. (#3)

Maintenance

• CI bumped to Node 24 majors (stale@v10, dpe-rules-watch checkout@v6 / setup-uv@v8.2.0).
• Project-docs polish: clearer "Why dbdocs?" section, streamlined features, consistent site naming.

1.2.0

What's Changed

Project Health Check — dbdocs now ships a Health Check page scoring your project across the six dbt-project-evaluator
dimensions (testing, modeling, documentation, structure, performance, governance), derived straight from your dbt artifacts.
The page renders a scorecard plus collapsible per-dimension findings; per-test pass/fail detail (from run_results.json) shows
on each model page. The rule engine is configurable and pluggable via the health: block in dbdocs.yml (thresholds,
rule/dimension disables, custom rules_module) and the dbdocs.health_rules entry point. Always built, fail-soft to empty when
run_results.json is absent. (#2)

Under the hood

• chore(ci): bump GitHub Actions to Node 24 runtimes by @il-dat in #1
• feat: add Project Health Check (six dbt-project-evaluator dimensions) by @il-dat in #2

New Contributors

• @il-dat made their first contribution in #1

Full Changelog: 1.1.0...1.2.0

1.1.0

What's new in 1.1.0

Improvements

• SPA refactored into 3-tier ES modules — the monolithic assets/app.js is replaced by a clean data.js → service.js → ui.js split; service.js is fully DOM-free for easier testing and future reuse.
• Performance at scale — the React Flow graph app now windows large graphs before layout so a project with 1000s of models no longer freezes the browser; an unfocused DAG over the cap shows a focus-node prompt instead of attempting a full layout.
• Column-level lineage parallelism — ColumnLineageExtractor fans out across a ProcessPoolExecutor for projects above the model-count threshold, and builds the sqlglot scope once per model (not once per column), cutting O(columns × parse) to O(parse + columns).
• E2E test suite — a Playwright suite (frontend/test/e2e/spa.spec.ts) now runs as an independent e2e job in CI against a real demo build, separate from the Python coverage gate.
• Branding support — generate() accepts optional logo and favicon overrides from dbdocs.yml; the SPA swaps the header mark and favicon, falling back to bundled defaults when unset.
• Improved inject pipeline — site/inject.py now has a well-defined INJECT_MARKER contract; the data payload is always external (never inlined into index.html).

Fixes

• Google Analytics property ID corrected in project docs config.

Docs

• Updated demo screenshots and navigation in the project documentation site.

Full changelog

1.0.2...1.1.0

1.0.2

Full Changelog: 1.0.1...1.0.2

1.0.1

Full Changelog: 1.0.0...1.0.1

1.0.0

Full Changelog: https://github.com/datnguye/dbt-docs/commits/1.0.0