fix: enforce active schema compatibility on release publish - #694
Merged
Conversation
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
1 participant
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.
Summary
This implements Option B from the schema-orphaning decision in #585. Annotation writes continue to validate against the schema pinned to their batch, while publishing rejects candidate release content that the active schema does not describe before it writes a manifest or release. The refusal reports deterministic per-class blockers through the SDK, REST, CLI, and MCP.
The OpenAPI contract and generated TypeScript client now describe the REST refusal. Exporters retain pre-write checks for malformed, archival, or external manifests, including the lane formats. The shared CLI test harness now pins Typer and Rich rendering per invocation so tests do not inherit terminal colour or width settings.
Validation
bash scripts/check.shpassed under Node 24 with 3,962 Python tests and 24 skips, Ruff, mypy, import contracts, frontend build, tests and lint, OpenAPI and generated-client drift checks, and the Chromium e2e and real-server cycle suites.Found, not fixed
None.