Skip to content

Move @basou/core to zod 4.6.7 to clear GHSA-mrhx-c7xc-m3w5 from the production audit - #394

Merged
takashi-matsuyama merged 1 commit into
mainfrom
deps/zod-4.6.7
Oct 24, 2026
Merged

takashi-matsuyama merged 1 commit into
mainfrom
deps/zod-4.6.7

Conversation

@takashi-matsuyama

@takashi-matsuyama takashi-matsuyama commented Oct 24, 2026 •

Copy link
Copy Markdown
Member

Summary

Move @basou/core's zod from ^4.6.5 to ^4.6.7. The lockfile changes for zod alone (10 lines), and CHANGELOG.md gains an ## Unreleased entry.

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 on main and on every open pull request whose lockfile still resolves 4.6.5; the last main run 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.5 admits 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 main at f08e08f with this commit (pnpm 9.12.0, as pinned on main):

Check Result
pnpm install --frozen-lockfile passes
lockfile zod@4.6.7 integrity matches npm view zod@4.6.7 dist.integrity
pnpm -r run build, pnpm typecheck pass
pnpm lint passes (the same 5 warnings and 1 info as on main)
pnpm lint:lang, pnpm lint:paths, pnpm test:scripts pass
pnpm test core 2980 passed + 1 skipped, sdk 67, cli 1616 (all pass)
pnpm audit --audit-level=moderate --prod "No known vulnerabilities found"
pnpm --filter @basou/core gen:schemas the committed JSON Schema artifacts are unchanged

Checklist

  • Branch is rebased on main.
  • One commit per topic (split unrelated fixes into separate PRs).
  • Tests cover the change: no source changes; the existing suite and the schema regeneration run against zod 4.6.7 (table above).
  • pnpm lint, pnpm typecheck, and pnpm test are all green locally.
  • CHANGELOG.md ## Unreleased updated (or this PR is pure internals with no user-visible change -- say so below).
  • CLI stderr stays pathless: no CLI change.

Related

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
takashi-matsuyama merged commit 8324fd4 into main Oct 24, 2026
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant