feat!: upgrade to Zod v4 #236
Open
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
Upgrades the project from Zod v3 to Zod v4, fixing all type errors caused by breaking changes in the new version.
Changes
zodfrom v3.25.76 to v4.1.13z.objectOutputType→z.infer<z.ZodObject<Params>>in mcp-helpers.tsz.record(z.unknown())→z.record(z.string(), z.unknown())in 9 filesz.enum()description from constructor options to.describe()methodscripts/validate-schemas.tsto work with Zod v4 internalsBreaking Changes
z.record()schemas now explicitly require string keys (z.record(z.string(), z.unknown())), and thez.enum()description is now set via.describe()method instead of constructor options. This affects TypeScript type inference for consumers using these schemas.While this is primarily a type-level breaking change (runtime behavior is unchanged), TypeScript consumers may need to update their types.
Verification
🤖 Generated with Claude Code