Repository navigation
chore: pin forge-cli 0.28.0, and mark what shipped in it - #201
Merged
Merged
Conversation
- cli-version.json and every version claim the sweep flags move to 0.28.0; 0.7.6 stays the stable schema and 0.7.5 the quickstart scaffold. - The contract reference pages regenerate from 0.28.0 (version line only: no schema changed). - Every "on forge-cli main, not yet in a release" marker for #828, #830, #832, #833, #836 and #837 becomes "since 0.28.0", and the sentences written ahead of the install change describe it as released. - upgrading.md gains "Changes in 0.28.0": the install change first, then the pins, the dependency list, the Debezium dotenv names, the Iceberg catalogAuth checks, Databricks and the rest, each checked against the 0.28.0 CLI. - forge-cli-releases.json is reviewed through 0.28.0.
This branch was previously deployed
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.
Pins the site to
data-product-forge0.28.0 (on PyPI since 2026-11-06) and marks what shipped in it.cli-version.jsonand the 14 version claims the sweep flags move to 0.28.0. The stable schema stays 0.7.6 and the quickstart scaffold stays 0.7.5, as the 0.28.0 CLI reports. No schema changed, so the regenerated contract reference pages differ only in their version line.main, not yet in a release" marker for forge-cli #828, #830, #832, #833, #836 and #837 becomes*(since 0.28.0, …)*. The sentences written ahead of the install change now describe it as released.docs/upgrading.mdgains Changes in 0.28.0, in this order:[standard],[litellm](alias[ai]),[mcp],[lineage]and[aws], and which commands stop before doing work;catalogAuthchecks (#828, #830);fluid publishlocation (#840), and the rest.scripts/forge-cli-releases.jsonis reviewed through 0.28.0.Checks
data-product-forge==0.28.0from PyPI (Python 3.11), all exit 0:check_cli_docs.pycheck_providers.pycheck_cli_docs.py --markers-onlygen_contract_reference.py --checknpm ci && npm run docs:build && node scripts/check-dist-links.mjs: exit 0.fluid doctor, the dotenv names), and its corrections are applied. They were: the #823 marker (that PR shipped in 0.27.0), the exactJMX_*names, the hedged Databricks ASSIGN requirement, the narrower AWS account-id failure, the doctor notice condition, and thefluid ai setupandfluid forgeprovider wording.Not covered
docs/providers/databricks.mddoes not yet describe the 0.28.0 Unity Catalog comments, tags and certification beyond the upgrading summary, and the newdatabricks-*codes are not yet indocs/advanced/error-codes.md. That needs its own page update.