generated from SAP/repository-template
-
Notifications
You must be signed in to change notification settings - Fork 30
chore(deps): [DO NOT MERGE] Bump zod from 3.25.76 to 4.0.5 #854
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
dependabot
wants to merge
6
commits into
v1-main
Choose a base branch
from
dependabot/npm_and_yarn/zod-4.0.5
base: v1-main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
3b57caf
chore(deps): Bump zod from 3.25.76 to 4.0.5
dependabot[bot] 5071e65
chore: update pnpm-lock.yaml
bd858fd
update zod to v4 except prompt-registry
ZhongpinWang 1995c29
Merge branch 'main' into dependabot/npm_and_yarn/zod-4.0.5
ZhongpinWang 24867e5
fix schema tests by using zod v3 for schema-tests package
ZhongpinWang 4a5ba6a
move ts-to-zod to individual packages
ZhongpinWang File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -33,6 +33,7 @@ | |
| }, | ||
| "dependencies": { | ||
| "@sap-ai-sdk/core": "workspace:^", | ||
| "ts-to-zod": "^3.15.0", | ||
| "zod": "^3.25.76" | ||
| } | ||
| } | ||
Oops, something went wrong.
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[q] I am confused, so we now use a mix of v4 and v3?
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We kind like have to. Let me explain this complex story:
In #837 ,
zod-to-json-schemafailed the pipeline with minor updates fromzodv3. We could either stop updatingzodand wait forzod-to-json-schema, or adoptzod/v4(by importing fromzod/v4in zod v3) as it has native support for zod to json. But since zod v4 has native support for this zod to json feature, I don't thinkzod-to-json-schemawill be actively continued anymore.Thus, the decision was to use
zod/v4(in zod v3).Recently, zod officially released v4 (we can import directly from
zodinstead ofzod/v4from v3), we have this dependabot PR. Butts-to-zodagain doesn't work with zod v4. At this point, we can either mix zod versions as they are used independently for different purposes in our overall project, or removets-to-zodin favour of supporting zod v4 fully, but I am not sure if we find a good alternative forts-to-zod.WDY think? I would hope eventually
ts-to-zodwill support zod v4, but no clear evidence that this will actually happen. In a worst case scenario, we eventually need to dropts-to-zod.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A potential good replacement could be https://orval.dev/guides/zod
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So even with the latest version we still have access to
zod/v3and updating imports like below works.import { z } from 'zod/v3';In the end, I don't have a strong opinion on if we use
zod/v3or the old dependency. However if we're pinning major versions for certain packages, then we'll probably need to ignore the updates in dependabot?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good to know that we can use
zod/v3! Maybe I go with this option for now and in the BLI we look for alternatives.