Repository navigation
Conversation
Zod lists every z.object in an output schema with additionalProperties: false. SDK clients validate each result against the tools/list they cached at connect, so an output field added in a later deploy fails every call from a client holding the older list, even when the server-side call succeeded (MCP-SERVER-GQS, GRA, GT6). buildServer now wraps each output schema so its listed JSON Schema drops additionalProperties: false from objects, through a Zod override. Validation on the server still uses the Zod schema, and record value schemas are unchanged. Refs #2293 Co-Authored-By: Shayna Chambless <173110007+shayna-ch@users.noreply.github.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Making a field required does not break a client holding an older tools/list. Making a required field optional or nullable does, and so does widening a value, such as a new enum member. Co-Authored-By: Shayna Chambless <173110007+shayna-ch@users.noreply.github.com>
This branch was successfully deployed
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.
Zod lists every z.object in an output schema with
additionalProperties: false. SDK clients validate each result against the tools/list they cached at connect, so an output field added in a later deploy fails every call from a client holding the older list, even when the server-side call succeeded (MCP-SERVER-GQS, GRA, GT6).
buildServer now wraps each output schema so its listed JSON Schema drops additionalProperties: false from objects, through a Zod override. Validation on the server still uses the Zod schema, and record value schemas are unchanged.
Refs #2293