Skip to content

docs: 0.12.0 release baseline — dbt wave, 0.7.5 GA, lineage verify#93

Merged
fas89 merged 1 commit into
mainfrom
docs/release-0.12.0
Jul 18, 2026
Merged

docs: 0.12.0 release baseline — dbt wave, 0.7.5 GA, lineage verify#93
fas89 merged 1 commit into
mainfrom
docs/release-0.12.0

Conversation

@fas89

@fas89 fas89 commented Jul 18, 2026

Copy link
Copy Markdown
Collaborator

Brings the docs to the v0.12.0 CLI baseline. Every claim was verified against the v0.12.0 git tag of forge-cli (not main), and the drift gate was run against the real PyPI 0.12.0 wheel.

What changed

  • docs/RELEASE_NOTES_0.12.0.md (new, flagship): schema 0.7.5 promoted to stable/GA (default for untagged contracts; 0.7.6 opens as preview; one-time plan/bundle digest churn for untagged contracts called out under Compatibility), the full dbt wave (fluid import dbt, --model-contracts, MetricFlow semantic_models+metrics bridge, packages.yml + sources.yml freshness emission, run_results.json → run records + verify checks, Fusion/dbt Core v2 detection, --dbt-tests-key/FLUID_DBT_TESTS_KEY), fluid verify --reconcile-lineage, and the fixed/internal items (copilot enrichment slots, test-mapper consolidation, CI split, Docker CVE gate). Wired into the Project nav (newest first).
  • docs/.vuepress/cli-version.json: supportedCliVersion / supportedCliInstallSpec → 0.12.0. supportedFluidContractVersion stays 0.7.5 (now GA).
  • docs/cli/import.md: new "Importing a dbt project" section (real flags from the tag; ImportReport shape; dbt parse first; catalog.json overlay; manifest v9 floor). Also removed a stale "Coming in the next release" tip about the 0.8.3 ingestion importers.
  • docs/cli/verify.md: documented --reconcile-dbt (announced in the 0.11.0 notes but never added to this page), --reconcile-lineage (3 drift classes + severity table), --warn-only, and the new dbt transformation checks (dbt_tests_passed / no_error_severity_failures). The differing exit-code gating of the two reconcile legs (dbt drift gates independent of --strict; lineage criticals gate only under --strict) matches cli/verify.py at the tag.
  • docs/cli/generate-vector.md: preview framing → stable-since-0.12.0; vectorConfig is default-available.
  • docs/advanced/environment-variables.md: header → v0.12.0; added DBT_EXECUTABLE and FLUID_DBT_TESTS_KEY (flag > env > auto precedence verified at the tag).
  • docs/README.md: the "Current release" tip still said 0.10.0 and (incorrectly) that 0.7.5 was already GA — rewritten to the 0.12.0 baseline.
  • docs/RELEASE_NOTES_0.11.0.md: status line → "Superseded by 0.12.0".
  • scripts/cli-docs-allowlist.yml pruned against the installed 0.12.0 wheel (see below).

Allowlist prunes (verified by introspecting register_core_commands in the installed 0.12.0 wheel)

  • Pruned from docs_only_ok — now real top-level commands with existing pages: runs, retention, secrets, stats, contract, ship, mcp, memory, roadmap, scaffold-ide, and skills (the swapped-args registration bug noted in the old comment is fixed at 0.12.0).
  • Pruned from undocumented_ok — no longer registered at all: context (the hidden config alias is gone), preview.
  • Kept export-odps in docs_only_ok with a corrected comment: contrary to the old "remove once ≥0.8.4" note, export-odps is NOT a registered command at 0.12.0 — the 0.10.0 provider→exporter reclassification retired it in favour of fluid generate standard --format odps-v4.1; only the deprecated export-opds alias still registers (kept in undocumented_ok).

Verification

Drift gate against the real PyPI wheel (data-product-forge==0.12.0 in a clean python3.12 venv), with the pruned allowlist:

OK: fluid CLI version matches docs (0.12.0).
OK: `fluid init --quickstart` emits fluidVersion 0.7.2 (matches pin).
OK: all 68 CLI subcommands are documented (docs/cli/ has 68 pages).

docs/.vuepress/config.ts parses (node readFileSync sanity) and all relative links in the changed pages resolve.

Inaccuracies found in existing pages (for the record)

  • docs/README.md claimed "Schema 0.7.5 remains the GA default" at 0.10.0 and docs/RELEASE_NOTES_0.9.0.md claims 0.7.5 was "promoted to GA" in 0.9.0 — the CLI ground truth (schema_manager.py at tags v0.10.0–v0.11.0) shows 0.7.5 stayed in PREVIEW_VERSIONS until v0.12.0. README fixed here; the historical 0.9.0 notes were left as-is.
  • Older release-notes pages (0.10.0 and earlier) all still say "Current stable docs baseline" — only the immediately-superseded 0.11.0 page was corrected here.

@fas89
fas89 merged commit 820df43 into main Jul 18, 2026
7 checks passed
@fas89
fas89 deleted the docs/release-0.12.0 branch July 18, 2026 08:34
@fas89
fas89 temporarily deployed to github-pages July 18, 2026 08:36 — with GitHub Actions Inactive
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant