Repository navigation
Implement transactional type-pack contract evolution - #39
Merged
Merged
Conversation
This was referenced Aug 2, 2026
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.
What changed
mdbase.lock.yamlin canonical collection snapshots.Why
Contract changes previously left SDK consumers to infer collection state from failing operations. The engine now owns compatibility assessment and produces a deterministic migration plan that callers can explain before any write occurs.
Impact
This is intentionally breaking prerelease API work. The old install types/functions are removed in favor of structured assessment and application results.
Depends on mdbase-spec#44.
Validation