docs: 0.12.0 release baseline — dbt wave, 0.7.5 GA, lineage verify#93
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Brings the docs to the v0.12.0 CLI baseline. Every claim was verified against the
v0.12.0git 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.supportedFluidContractVersionstays0.7.5(now GA).docs/cli/import.md: new "Importing a dbt project" section (real flags from the tag; ImportReport shape;dbt parsefirst; 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) matchescli/verify.pyat the tag.docs/cli/generate-vector.md: preview framing → stable-since-0.12.0;vectorConfigis default-available.docs/advanced/environment-variables.md: header → v0.12.0; addedDBT_EXECUTABLEandFLUID_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.ymlpruned against the installed 0.12.0 wheel (see below).Allowlist prunes (verified by introspecting
register_core_commandsin the installed 0.12.0 wheel)docs_only_ok— now real top-level commands with existing pages:runs,retention,secrets,stats,contract,ship,mcp,memory,roadmap,scaffold-ide, andskills(the swapped-args registration bug noted in the old comment is fixed at 0.12.0).undocumented_ok— no longer registered at all:context(the hiddenconfigalias is gone),preview.export-odpsindocs_only_okwith a corrected comment: contrary to the old "remove once ≥0.8.4" note,export-odpsis NOT a registered command at 0.12.0 — the 0.10.0 provider→exporter reclassification retired it in favour offluid generate standard --format odps-v4.1; only the deprecatedexport-opdsalias still registers (kept inundocumented_ok).Verification
Drift gate against the real PyPI wheel (
data-product-forge==0.12.0in a clean python3.12 venv), with the pruned allowlist:docs/.vuepress/config.tsparses (node readFileSync sanity) and all relative links in the changed pages resolve.Inaccuracies found in existing pages (for the record)
docs/README.mdclaimed "Schema 0.7.5 remains the GA default" at 0.10.0 anddocs/RELEASE_NOTES_0.9.0.mdclaims 0.7.5 was "promoted to GA" in 0.9.0 — the CLI ground truth (schema_manager.pyat tags v0.10.0–v0.11.0) shows 0.7.5 stayed inPREVIEW_VERSIONSuntil v0.12.0. README fixed here; the historical 0.9.0 notes were left as-is.