Skip to content

Re-vendor the 0.7.7 preview from forge-cli v0.31.0 - #55

Merged
fas89 merged 1 commit into
mainfrom
chore/revendor-forge-0.31.0
Nov 18, 2026
Merged

fas89 merged 1 commit into
mainfrom
chore/revendor-forge-0.31.0

Conversation

@fas89

@fas89 fas89 commented Nov 18, 2026

Copy link
Copy Markdown
Collaborator

Moves the pin from forge-cli v0.27.0 to v0.31.0 (peeled commit 0b72fb1c327ae33acddfdf8bbf9f5d1e7849d19c). The vendored 0.7.7 was the v0.27.0 copy. 0.7.6 is byte-identical at the new tag and is not touched.

What changes

  • Schema: fluid-schema-0.7.7.json is replaced byte for byte from the tag (297351 bytes), and scripts/schema-versions.json moves ref and commit.
  • Generated output: specs/0.7.7 and schema-diffs/diff-0.7.6-to-0.7.7.md are regenerated with the locked renderer.
  • What 0.7.7 gained since the v0.27.0 copy:
    • rules about valid data: invariants, identifier formats, placeholders and shared attributes;
    • relationships and validity windows;
    • a schema registry definition;
    • stream trigger, watermark, checkpoint and startingOffsets;
    • maskAtIngest, parameters.spark and the lakeflow engine;
    • six packaging container kinds and Protobuf field numbers;
    • write-only password and token members.
  • Docs: docs/releases/0.7.7.md, docs/releases/README.md and docs/schema/changelog.md describe these from the schema's own descriptions.

secretRef narrows in this preview

  • secretRef is now one per-scheme grammar. A vault:// reference needs a #field: vault://secret/data/crm-db is refused, and vault://secret/data/crm-db#password is valid.
  • This is the only document that 0.7.6 accepts and 0.7.7 rejects. It is recorded as a waiver in scripts/compat-waivers.txt, and the 0.7.7 acquisition cases use the new form.
  • The release note and the changelog say the pair is no longer purely additive. 0.7.7 is a preview, and a contract reaches it only by declaring "0.7.7".
  • tests/meta_test.py changes in one place: its waiver test now inserts its entry in sorted position.

Checks (all exit 0)

  • meta_test: 50/50.
  • conformance/run.py: 1958/1958.
  • check-compat: compatible, 1 waived.
  • check-schema-drift: pass.
  • generate-docs.py --check and generate-schema-diffs.py --check: pass.
  • mutation_coverage: 0.7.7 at 41.4% (floor 40).
  • check_reference against data-product-forge 0.31.0: 0 disagree.
  • docs-links grep: clean.
  • npm run docs:build: clean.
  • data-product-forge 0.31.0 validates the release note's complete contract.

For the maintainer

Keep the secretRef waiver, or ask upstream to accept a vault:// reference without a #field?

The vendored 0.7.7 schema was the v0.27.0 copy. Replace it with the
reference implementation's current file, byte for byte, and regenerate
what derives from it: specs/0.7.7/ and schema-diffs/diff-0.7.6-to-0.7.7.md.

0.7.7 gained rules about valid data (invariants, identifier formats,
placeholders, shared attributes), relationships and validity windows, a
schema registry definition, stream trigger/watermark/checkpoint/offsets,
maskAtIngest, parameters.spark, the lakeflow engine, six packaging
container kinds, Protobuf field numbers, and a per-scheme secretRef
grammar. 0.7.6 is unchanged.

The secretRef grammar is the one narrowing against 0.7.6: a vault://
reference needs a #field. The 0.7.7 acquisition cases use the new form,
the narrowing is recorded in scripts/compat-waivers.txt, and meta_test
keeps the waiver file sorted when it adds its own entry. The release
note and changelog say so.

upstream.ref is v0.31.0 and upstream.commit is the tag's peeled commit,
0b72fb1c327ae33acddfdf8bbf9f5d1e7849d19c. data-product-forge 0.31.0 validates
the release note's complete contract and agrees with the corpus.
@fas89
fas89 merged commit 5da0052 into main Nov 18, 2026
7 checks passed
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