-
Notifications
You must be signed in to change notification settings - Fork 3
Update dependency zod to v4.1.1 #43
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -26,7 +26,7 @@ | |
| "mollitia": "0.2.0", | ||
| "octokit": "5.0.3", | ||
| "parse-diff": "0.11.1", | ||
| "zod": "4.1.0" | ||
| "zod": "4.1.1" | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Same suggestion here: switch to a caret range to reduce maintenance overhead on minor patch releases. For example: "zod": "^4.1.1"Additionally, if these two package.json files share many dependencies, consider hoisting common packages into a root workspace configuration to avoid duplication and keep versioning in sync. |
||
| }, | ||
| "devDependencies": { | ||
| "@eslint/js": "9.34.0", | ||
|
|
||
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.
It’s usually safer to allow patch upgrades without manual bumps by using a caret range. Instead of pinning to exactly “4.1.1”, you can specify:
This way, compatible bug fixes in newer 4.1.x releases are picked up automatically. It also stays consistent with how other dependencies are versioned.