From 6c80ac58c110527413a12b3836dcea9043a7040e Mon Sep 17 00:00:00 2001 From: Speculator55005 <50082482+fas89@users.noreply.github.com> Date: Tue, 15 Sep 2026 10:01:51 +0200 Subject: [PATCH] docs: track 0.15.2, which is what `pip install` now gives you `data-product-forge` v0.15.2 is on PyPI. The pin moves after the release and never before it: `cli-consistency` runs `pip install data-product-forge==` on every pull request, so bumping ahead of publication fails that job on an install that cannot resolve. The version sweep did the work rather than a grep. Bumping the pin alone turned the gate red and it named every disagreeing line in turn - the repo-root README bullet, the landing page banner and its `pip install` sentence, the vision baseline, five provider and walkthrough "Docs Baseline" banners, the CLI and providers index lines, the getting-started pin and its tracking sentence, and three exact-pin examples under sdk-and-plugins. Fourteen files, none of which I would have found by hand. One mention of `0.15.1` is deliberately kept, on the landing page: it names `0.15.1` and `0.15.2` as the two front-door patches that have no release-notes page of their own. That is history, and history is not rewritten to match today. Verified: `check_cli_docs.py` green, including "every version claim in docs/ agrees with the pin (CLI 0.15.2)" and all 1093 documented `fluid` invocations against the newly pinned CLI. Build clean, and the artifact link gate clean at 219 pages and 107,738 absolute references with its canaries passing. --- README.md | 2 +- docs/.vuepress/cli-version.json | 4 ++-- docs/README.md | 9 +++++---- docs/cli/README.md | 2 +- docs/cli/mission.md | 2 +- docs/getting-started/README.md | 4 ++-- docs/providers/README.md | 2 +- docs/providers/aws.md | 2 +- docs/providers/gcp.md | 2 +- docs/providers/local.md | 2 +- docs/providers/snowflake.md | 2 +- docs/sdk-and-plugins/reference/companion-packages.md | 2 +- docs/sdk-and-plugins/reference/trust-model.md | 2 +- docs/vision.md | 2 +- docs/walkthrough/export-orchestration.md | 2 +- docs/walkthrough/universal-pipeline.md | 2 +- 16 files changed, 22 insertions(+), 21 deletions(-) diff --git a/README.md b/README.md index ed9ed86..279e6fa 100644 --- a/README.md +++ b/README.md @@ -15,7 +15,7 @@ Fluid Forge is a contract-first CLI for building, validating, and deploying data ## Current Versioning -- Current CLI release documented here: `0.15.1` +- Current CLI release documented here: `0.15.2` - Current scaffolded contract schema examples: `fluidVersion: 0.7.5` Those are different on purpose. `fluid version` reports the installed CLI release, while `fluidVersion` inside a contract selects the contract schema version. diff --git a/docs/.vuepress/cli-version.json b/docs/.vuepress/cli-version.json index 314514e..c19fc32 100644 --- a/docs/.vuepress/cli-version.json +++ b/docs/.vuepress/cli-version.json @@ -1,6 +1,6 @@ { - "supportedCliVersion": "0.15.1", - "supportedCliInstallSpec": "data-product-forge==0.15.1", + "supportedCliVersion": "0.15.2", + "supportedCliInstallSpec": "data-product-forge==0.15.2", "supportedFluidContractVersion": "0.7.5", "quickstartScaffoldVersion": "0.7.2", "supportedSdkVersion": "0.10.0", diff --git a/docs/README.md b/docs/README.md index 550b374..29a9025 100644 --- a/docs/README.md +++ b/docs/README.md @@ -80,7 +80,7 @@ fluid apply contract.fluid.yaml --yes This docs site currently tracks: -- CLI release `0.15.1` +- CLI release `0.15.2` - Contract schema `0.7.5` as the stable default, with `0.7.6` open as an opt-in preview Which `fluidVersion` a fresh scaffold actually writes depends on which scaffold path you took, and the quickstart is not the same as the factory. The rule, with the per-path numbers, lives in one place: [Understand the version numbers](/forge_docs/getting-started/#understand-the-version-numbers). Run `fluid version` for the authoritative list of accepted schema versions on the CLI you have installed. @@ -122,9 +122,10 @@ These are the groups `fluid --help` prints on `0.15.0`. Run it yourself to confi `--help` promotes a short surface, not the whole one. Commands such as `bundle`, `diff`, `verify`, `publish`, `runs`, `stats`, `ship` and [`mission`](/forge_docs/cli/mission.html) are real and documented, and `--help` itself names the production path as `bundle` → `validate` → `generate artifacts` → `diff` → `plan` → `apply` → `verify` → `publish`. See the [CLI Reference](/forge_docs/cli/) for everything. -:::: tip Current release — `0.15.1`, schema **0.7.5** stable (GA) -`pip install data-product-forge` gives you `0.15.1`. The `0.15.x` changes landed in `0.15.0`, which -documents them together with `0.14.1` in one baseline (there is no separate `0.15.1` page): +:::: tip Current release — `0.15.2`, schema **0.7.5** stable (GA) +`pip install data-product-forge` gives you `0.15.2`. The `0.15.x` changes landed in `0.15.0`, which +documents them together with `0.14.1` in one baseline (`0.15.1` and `0.15.2` are front-door patches with no +notes page of their own — dead documentation links in the CLI's own error output): [`0.15.0` release notes](/forge_docs/RELEASE_NOTES_0.15.0.html). **Coming from `0.14.1` or earlier? One thing can break you.** A contract that passed diff --git a/docs/cli/README.md b/docs/cli/README.md index cdbdcba..90a4f0b 100644 --- a/docs/cli/README.md +++ b/docs/cli/README.md @@ -8,7 +8,7 @@ The page you actually want is [**CLI by task →**](./tasks/) — narrative walk ## Read this first -- CLI release examples in this section use `0.15.1` +- CLI release examples in this section use `0.15.2` - Contract examples use `fluidVersion: 0.7.2` - `fluid version` and `fluidVersion` are different things - The pinned CLI version is recorded in [`docs/.vuepress/cli-version.json`](https://github.com/Agenticstiger/forge_docs/blob/main/docs/.vuepress/cli-version.json) and enforced by the [`cli-consistency`](https://github.com/Agenticstiger/forge_docs/actions/workflows/cli-consistency.yml) workflow. diff --git a/docs/cli/mission.md b/docs/cli/mission.md index e5377a5..49f1db5 100644 --- a/docs/cli/mission.md +++ b/docs/cli/mission.md @@ -222,7 +222,7 @@ cosmetics ([`0.13.0` security fixes](../RELEASE_NOTES_0.13.0.md#security)). ```yaml - name: Mission gate run: | - pip install data-product-forge==0.15.1 + pip install data-product-forge==0.15.2 fluid mission check quality-coverage contract.fluid.yaml ``` diff --git a/docs/getting-started/README.md b/docs/getting-started/README.md index 3351b72..c40ca8e 100644 --- a/docs/getting-started/README.md +++ b/docs/getting-started/README.md @@ -38,7 +38,7 @@ The current docs baseline is `0.15.0` — the stable tag was cut on `2026-09-14` ```bash pip install --upgrade data-product-forge -pip install "data-product-forge==0.15.1" # exact pin +pip install "data-product-forge==0.15.2" # exact pin ``` Pre-releases (when published) ship to PyPI as PEP 440 pre-releases — `pip install` skips them by default. The `--pre` flag opts in. @@ -58,7 +58,7 @@ fluid version fluid doctor ``` -This docs set tracks CLI release `0.15.1`. Docs updates land in lockstep with each release; if you're on an older CLI, some `--mode` / `--target` flags mentioned here won't be present yet — see the [CLI index](../cli/README.md) for what maps to what. +This docs set tracks CLI release `0.15.2`. Docs updates land in lockstep with each release; if you're on an older CLI, some `--mode` / `--target` flags mentioned here won't be present yet — see the [CLI index](../cli/README.md) for what maps to what. > **Extending the CLI?** Fluid Forge ships three plugin extension points and a companion SDK on PyPI. If your team has its own CI templates, scaffolding standards, or governance rules, see **[SDK & Plugins](../sdk-and-plugins/)**. diff --git a/docs/providers/README.md b/docs/providers/README.md index b66d9cf..a4ebc83 100644 --- a/docs/providers/README.md +++ b/docs/providers/README.md @@ -8,7 +8,7 @@ Fluid Forge uses one contract format across local and provider-backed execution ## Docs baseline -- CLI release covered by the primary docs: `0.15.1` +- CLI release covered by the primary docs: `0.15.2` - Default scaffold (`fluid init --quickstart`) emits `fluidVersion: 0.7.2` - Discovery-based scaffolds (`fluid init --discover`, `fluid forge`, `fluid product-new`) emit `fluidVersion: 0.7.5` — the latest bundled schema diff --git a/docs/providers/aws.md b/docs/providers/aws.md index 706cb70..34ee7db 100644 --- a/docs/providers/aws.md +++ b/docs/providers/aws.md @@ -3,7 +3,7 @@ Deploy data products to Amazon Web Services — S3, Glue, Athena — using the same contract and CLI commands as every other provider. **Status:** ✅ Production -**Docs Baseline:** CLI `0.15.1`
+**Docs Baseline:** CLI `0.15.2`
**Tested Services:** S3, Glue Data Catalog, Athena, IAM > **Why it matters** diff --git a/docs/providers/gcp.md b/docs/providers/gcp.md index d010b23..8272046 100644 --- a/docs/providers/gcp.md +++ b/docs/providers/gcp.md @@ -1,7 +1,7 @@ # GCP Provider **Status:** ✅ Production Ready -**Docs Baseline:** CLI `0.15.1`
+**Docs Baseline:** CLI `0.15.2`
**Services:** BigQuery, Cloud Storage, IAM, Cloud Run, Pub/Sub > **Why it matters** diff --git a/docs/providers/local.md b/docs/providers/local.md index ac49287..1cffabd 100644 --- a/docs/providers/local.md +++ b/docs/providers/local.md @@ -1,7 +1,7 @@ # Local Provider **Status:** ✅ Production Ready -**Docs Baseline:** CLI `0.15.1`
+**Docs Baseline:** CLI `0.15.2`
**Database:** DuckDB, SQLite > **Why it matters** diff --git a/docs/providers/snowflake.md b/docs/providers/snowflake.md index e55dc8c..3cf58bd 100644 --- a/docs/providers/snowflake.md +++ b/docs/providers/snowflake.md @@ -3,7 +3,7 @@ Deploy data products to Snowflake Data Cloud — databases, schemas, tables, RBAC grants — using the same contract and CLI commands as every other provider. **Status:** ✅ Production -**Docs Baseline:** CLI `0.15.1`
+**Docs Baseline:** CLI `0.15.2`
**Tested Services:** Databases, Schemas, Tables, Warehouses, RBAC Grants > **Why it matters** diff --git a/docs/sdk-and-plugins/reference/companion-packages.md b/docs/sdk-and-plugins/reference/companion-packages.md index 170fc03..5037510 100644 --- a/docs/sdk-and-plugins/reference/companion-packages.md +++ b/docs/sdk-and-plugins/reference/companion-packages.md @@ -48,7 +48,7 @@ The PyPI name reflects the product brand (`data-product-forge`). The import path ```toml dependencies = [ - "data-product-forge==0.15.1", # pin exact for reproducibility + "data-product-forge==0.15.2", # pin exact for reproducibility ] ``` diff --git a/docs/sdk-and-plugins/reference/trust-model.md b/docs/sdk-and-plugins/reference/trust-model.md index 9d45de0..2ef65f8 100644 --- a/docs/sdk-and-plugins/reference/trust-model.md +++ b/docs/sdk-and-plugins/reference/trust-model.md @@ -167,7 +167,7 @@ Plugins are tested, scanned, and approved by your platform team before showing u ```toml # In your deploy environment's pyproject.toml or requirements: -data-product-forge==0.15.1 +data-product-forge==0.15.2 data-product-forge-sdk==0.10.0 data-product-forge-custom-scaffold==0.4.1 my-org-validators==1.2.0 diff --git a/docs/vision.md b/docs/vision.md index d9915a2..c9a6609 100644 --- a/docs/vision.md +++ b/docs/vision.md @@ -147,7 +147,7 @@ fluid market --search "customer analytics" ## Versioning in the docs -- Current CLI release baseline: `0.15.1` +- Current CLI release baseline: `0.15.2` - Current scaffolded contract examples: `fluidVersion: 0.7.5` That split is intentional. The CLI release and the contract schema version move on related but different timelines. diff --git a/docs/walkthrough/export-orchestration.md b/docs/walkthrough/export-orchestration.md index 9852b09..d27d80f 100644 --- a/docs/walkthrough/export-orchestration.md +++ b/docs/walkthrough/export-orchestration.md @@ -1,6 +1,6 @@ # Generating Orchestration Code from Contracts -**Docs Baseline:** CLI `0.15.1`
+**Docs Baseline:** CLI `0.15.2`
**Status:** ✅ Production Ready ::: warning Compatibility note diff --git a/docs/walkthrough/universal-pipeline.md b/docs/walkthrough/universal-pipeline.md index 6c33d6f..00220a9 100644 --- a/docs/walkthrough/universal-pipeline.md +++ b/docs/walkthrough/universal-pipeline.md @@ -7,7 +7,7 @@ One Jenkinsfile. Every provider. Zero if/then logic. **Provider-specific logic:** None ::: warning Compatibility note -This walkthrough includes some older `0.7.1` contract-era examples. The primary docs baseline now tracks CLI `0.15.1`, current scaffolded contracts use `fluidVersion: 0.7.5`, and orchestration docs prefer `fluid generate schedule --scheduler airflow`. +This walkthrough includes some older `0.7.1` contract-era examples. The primary docs baseline now tracks CLI `0.15.2`, current scaffolded contracts use `fluidVersion: 0.7.5`, and orchestration docs prefer `fluid generate schedule --scheduler airflow`. ::: ---