Relax server schema gate to unblock sync with older YAOS plugin schemas - #60
Merged
Conversation
Copilot
AI
changed the title
Fix unable-to-sync schema compatibility check
Relax server schema gate to unblock sync with older YAOS plugin schemas
Jul 8, 2026
Copilot created this pull request from a session on behalf of
kavinsood
July 8, 2026 08:40
View session
kavinsood
marked this pull request as ready for review
July 8, 2026 09:37
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.
Current server deployments can reject sync with
This server requires schema version 3 or newereven when clients are on the latest plugin release path, creating a hard compatibility stop. This change redefines server schema compatibility as a bounded range instead of an exact minimum-only gate.Schema compatibility change
SERVER_MIN_SCHEMA_VERSIONfrom3to1inserver/src/version.ts.SERVER_MAX_SCHEMA_VERSIONat3so the server still advertises the current schema ceiling.Guard logic updated for range semantics
scripts/guard-schema-version.mjsto enforce:SERVER_MAX_SCHEMA_VERSION === EXPECTED_SCHEMA_VERSIONSERVER_MIN_SCHEMA_VERSION <= EXPECTED_SCHEMA_VERSIONSERVER_MIN_SCHEMA_VERSION <= SERVER_MAX_SCHEMA_VERSIONEngineering docs aligned with runtime behavior
docs/engineering/schema-version-guard.mdto reflect range-based validation and new pass/fail expectations.