fix: install Zod v4 in standalone MCP servers - #602
Merged
Conversation
creatornader
enabled auto-merge (squash)
July 29, 2026 07:22
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.
What changed
@atrib/attestand@atrib/summarizepnpm packfor publish-ready workspace dependency metadataWhy
Fresh npm installs resolved Zod v3 for the two schema-owning servers. MCP server v2 rejects those raw schemas before
server/discover, which also broke the emit, annotate, revise, and daemon packages that depend on attest. Workspace tests hid the defect because the monorepo resolved Zod v4.Verification