Repository navigation
Move @basou/core to zod 4.6.7 to clear GHSA-mrhx-c7xc-m3w5 from the production audit - #394
Merged
Merged
Conversation
5 of 6 tasks
zod before 4.6.6 can exhaust memory while validating oversized constrained collections (GHSA-mrhx-c7xc-m3w5, high). The advisory now covers the 4.6.5 that the lockfile resolved, so the required dependency audit of the production graph fails on main and on every pull request whose lockfile still resolves 4.6.5. The declared range moves from ^4.6.5 to ^4.6.7, the latest patch, and the lockfile changes for zod alone. A fresh install of the published 0.74.1 already resolves to a fixed version, since ^4.6.5 admits it; the declared floor now says so. No source changes, and regenerating the committed JSON Schema artifacts with zod 4.6.7 leaves them byte-identical.
takashi-matsuyama
force-pushed
the
deps/zod-4.6.7
branch
from
October 24, 2026 13:59
97f6d26 to
59d6100
Compare
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.
Summary
Move
@basou/core'szodfrom^4.6.5to^4.6.7. The lockfile changes for zod alone (10 lines), andCHANGELOG.mdgains an## Unreleasedentry.Why
zod before 4.6.6 can exhaust memory while validating oversized constrained collections (GHSA-mrhx-c7xc-m3w5, high). The advisory was updated on 2026-10-23 at 18:26 UTC and now covers the 4.6.5 that the lockfile resolves, so the required "Dependency vulnerability audit" (
pnpm audit --audit-level=moderate --prod) fails onmainand on every open pull request whose lockfile still resolves 4.6.5; the lastmainrun before the update passed.4.6.7 is the latest patch. A fresh install of the published 0.74.1 already resolves to a fixed version, since
^4.6.5admits it; the declared floor now says so.This supersedes Dependabot's #374, which moves zod to the same version but also re-resolves unrelated packages of the development tree (a second rollup with its platform packages, postcss 8.5.31, picomatch, tinyglobby and others, +293/-23 lockfile lines). Dependabot should close #374 by itself once zod 4.6.7 is on
main.What was checked, on a copy of
mainat f08e08f with this commit (pnpm 9.12.0, as pinned onmain):pnpm install --frozen-lockfilezod@4.6.7integritynpm view zod@4.6.7 dist.integritypnpm -r run build,pnpm typecheckpnpm lintmain)pnpm lint:lang,pnpm lint:paths,pnpm test:scriptspnpm testpnpm audit --audit-level=moderate --prodpnpm --filter @basou/core gen:schemasChecklist
main.pnpm lint,pnpm typecheck, andpnpm testare all green locally.CHANGELOG.md## Unreleasedupdated (or this PR is pure internals with no user-visible change -- say so below).Related