Repository navigation
Conversation
frontend moves to zod ^4.6.7. Port: z.record gets an explicit key schema, ZodError.errors becomes .issues, createRefundSchema.innerType() is dropped (refine no longer wraps the object), and the env validator no longer reads issue.received. puppeteer-core override floor raised to 25.13 so the lighthouse chain pulls chromium-bidi 157, which uses zod 4.
…visory Both lines were flagged high by pnpm audit (reached through @lhci/cli express and appium base-driver) and would keep the Security Gate red after the zod bump. Override floors raised.
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.OpenSSF ScorecardScorecard details
Scanned Files
|
PR Checks Summary
✅ All checks passed! Ready for review. |
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
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.
What changed
frontend:zod^3.24.1->^4.6.7. Port (type-check drove it, then grepped forany-typed leftovers; none):z.record(x)->z.record(z.string(), x)(32 sites)ZodError.errors->.issues(110 sites in ~80 API routes and lib files)createRefundSchema.innerType()->createRefundSchema(refine no longer wraps the object)lib/env/validator.ts:issue.receivedis gone in v4; "missing" is now detected fromprocess.env[path] === undefined(the schema is parsed straight fromprocess.env)..uuid()/.email()/.url()left as is (deprecated, still work).package.jsonoverridepuppeteer-corefloor>=25.9.0->>=25.13.0: the other zod 3 in the tree waschromium-bidi@17.0.2(pinned by puppeteer-core 25.12, reached via @lhci/cli > lighthouse). puppeteer-core 25.16 uses chromium-bidi 157, which depends on zod ^4.6.5.eslint-plugin-react-hooksaccepts zod 3 or 4, so it now resolves to 4.6.7.grep zod pnpm-lock.yamlshows only zod 4.6.7.body-parseroverrides to 1.20.9 / 2.4.0. Both lines had a fresh high advisory (GHSA-27r3-jxmh-p828) that would keep the Security Gate red once zod was fixed.overrides:block matches package.json.Commands run (clean worktree off origin/main; TZ=America/New_York)
pnpm install --frozen-lockfileokpnpm audit --audit-level=high(frontend) exit 0; before: zod + 2x body-parser high.pnpm type-check(frontend) exit 0 (baseline origin/main also 0)--maxWorkers=3, CI env vars): 652 suites passed, 56 skipped, 1 failed:src/app/api/__tests__/config.test.ts(5 s timeout on the first test of the file). It fails the same way on a clean origin/main worktree (which test times out varies), so it is pre-existing and unrelated.Not run / left
pnpm build(next build) were not run locally; their failures on the Dependabot PR (chore(deps): bump zod from 3.25.76 to 4.6.6 #207) predate this and match the red gates tracked in hq debt D-1475. frontend-vite, packages/* and desktop have no zod imports.lhci autorunlocally.