Repository navigation
Re-vendor the 0.7.7 preview from forge-cli v0.31.0 - #55
Merged
Merged
Conversation
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.
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.
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
secretRef narrows in this preview
Checks (all exit 0)
For the maintainer
Keep the secretRef waiver, or ask upstream to accept a vault:// reference without a #field?