Migrating to Zod v4, marking as peer dependency, and removing zod-to-json-schema #914
+289
−403
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.
Migrating to Zod v4, marking as peer dependency, and removing zod-to-json-schema
Note, due to changes in zod v4, I marked the
"preserves schema description"
test incompletable.test.ts
asit.skip
for now and left a comment pointing to an issue describing the change. We can still havecompletable
calldescribe
/meta
explicitly if we want it to behave differently from the rest of zod v4 and be backwards compatible.TODO:
completable
- the new zod v4 approach is much different. All tests pass, but want to do more end-to-end testing before calling it good.Motivation and Context
See: #555, #906, #891, #802, and (potentially) #809
It also is a first step to potentially moving to standard-schema in the future. See #164, #283
It also removes the dependency on
zod-to-json-schema
which is not actively maintained.How Has This Been Tested?
Breaking Changes
Requires migration to zod v4
Types of changes
Checklist
Additional context