build(deps): bump zod 3.24 → 4.4#347
Merged
Merged
Conversation
Adopts Dependabot #332. Zod 4 required three code adaptations: - middleware/validation.ts: ZodError.errors → .issues (renamed in v4) - routes/admin.ts + routes/billing.ts: z.record(value) → z.record(z.string(), value) (v4 requires an explicit key schema; z.string() preserves v3 string-key behavior) The 18 schema-definition sites (regex/min/max/optional/enum) are v3/v4-identical. Lockfile churn is peer-context re-resolution + zod-4 dedup (4 variants → 2); installed package set unchanged (1950 entries; ws/utf-8-validate versions identical to main). Verified: typecheck green (all 4 workspace projects), root suite 563/563, agent suite 1718 passed.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Adopts Dependabot #332 (zod 3→4), which CI-failed as a bare bump because v4 has breaking changes. Verified-then-adopted with the required code adaptations.
Zod 4 breaking changes handled
src/middleware/validation.ts:29ZodError.errors→.issues(renamed in v4)src/routes/admin.ts:25,src/routes/billing.ts:34z.record(value)→z.record(z.string(), value)(v4 requires an explicit key schema;z.string()preserves v3 string-key behavior)The 18 schema-definition sites (
z.string().regex/min/max/optional,z.enum) are v3/v4-identical and unchanged.Lockfile
Churn is pnpm peer-context re-resolution + zod-4 dedup (4 variants → 2). Verified the installed package set is unchanged vs
main: 1950 entries both,wsandutf-8-validateversion sets identical. Only real version change is rootzod 3.25.76 → 4.4.3.Verification
pnpm typecheck— green across all 4 workspace projectspackages/agentsuite — 1718 passed, 2 skipped (one pre-existing order-dependent CORS flake, passes in isolation + on re-run; unrelated to zod)Supersedes #332.