Repository navigation
[PR] fix(security): bump zod 4.1.8 -> 4.6.7 to clear GHSA-mrhx-c7xc-m3w5 (#4820) - #4880
Conversation
📦 Built Package ArtifactBranch: Latest build — install this exact versionnpm install -g billion-context@0.0.7325-pr.4880.7f9554bThis exact version is immutable and reproducible. The rolling Recent builds (commit → version)
Download artifact
tar xzf billion-context-pr4880.tgz
npm install -g packageInstall instructions are refreshed on each push. |
(ai: vllm-qwen/qwen3.8-27b) Merged origin/master into the branch (no conflicts, lockfile zod still 4.6.7) and pushed as 507d5eb — PR is now up-to-date with master; mergeable_state=blocked only while CI is still running (12 success / 9 skipped / 11 queued, no failures). |
[bot] 🏷 (ai: vllm-qwen/qwen3.8-27b) Merge-guard summary: round 1 was real — merged origin/master into |
[bot] 🏷 (ai: vllm-qwen/qwen3.8-27b) Merge-guard round 2: master had genuinely moved this time (→ 0cf53c8, #4854/#4817/#4849/#4825/#4866/#4864/#4863 + kernel 0.0.168 lock-sync); merged into |
|
@ranxianglei Friendly ping on this PR for #4820. The current checks show 37 successful and 14 skipped, with no failures. Could you please review it and merge if ready? If any additional validation (including the live OpenCode cross-instance e2e mentioned in the issue) is required before merging, please clarify what remains. Thanks! |
[bot] 🏷 (ai: vllm-qwen/qwen3.8-27b) Status on your ping — confirmed those numbers: head What remains before merge: nothing mandatory. The only open item is the optional live-OpenCode-host cross-instance e2e that the PR body explicitly defers to the owner ("if you want that e2e run before merge, say so") — everything else is done: targeted interop suite 28/28 on zod 4.6.7, build clean (zod stays external), typecheck clean, full regression green on the prior head. Also noted in the PR body as out-of-scope FYI: pre-existing kernel version drift on master ( On merging itself: I can't merge PRs — that's human-only per repo policy. Once CI goes green on |
…-4820 # Conflicts: # TECHNICAL-NOTES.md
📦 Merged Build PublishedThis merge to master was published as npm install -g billion-context@0.0.962-master.9d53c22 # this exact build
npm install -g billion-context@master # always the newest merged build
|
Closes #4820
Bumps the direct
zoddependency from 4.1.8 to 4.6.7 (latest patched release; the patched line for GHSA-mrhx-c7xc-m3w5 / CVE-2023-54404 starts at 4.6.6) and records the jimp nested-zod finding.What changed
package.json+package-lock.json:dependencies.zod4.1.8 -> 4.6.7. The pin stays exact (not a range), preserving the KDD fix: keep system prompt byte-stable for prefix cache #1 single-shared-instance intent. Only the top-levelnode_modules/zodentry moves; the 16 nested@jimp/*/node_modules/zodcopies are untouched (still 3.25.76, pinned by@jimp's own^3.23.8).AGENTS.md: KDD fix: keep system prompt byte-stable for prefix cache #1 line updated to 4.6.7 with the advisory reason.TECHNICAL-NOTES.md: new section recording the two-chain analysis — the direct-zod fix, and why the jimp nested-zod@3.x audit hit is a source-level false positive (the vulnerable$ZodArray.handleArrayResultexists only in zod's v4 implementation, never in v3;import "zod"in a 3.25.x install resolves to the v3 core;@jimp/*import plain"zod", neverzod/v4). We deliberately do not force-override jimp's zod 3->4.tests/opencode-native-v1.test.ts: comment version references 4.1.8 -> 4.6.7 (no logic change).Verification
tests/opencode-native-v1.test.ts: 28/28 pass on zod 4.6.7. Build clean (dist-external: OK— zod stays external per 197-master 发版最后 #3511); typecheck clean.Behavior change (disclosed)
zod 4.1.8 -> 4.6.7, same major (4.x). The only consumer in our tree issrc/agent/opencode-native.ts(OpenCode V1 plugin tools, lazy opaque import); it is not loaded in the Pi/proxy lanes. No wire/config/persistence change.Honest limits (per #4820 condition 1)
opencode-ai@1.19.4is self-contained (no declared zod dep), so its internal zod version isn't visible via registry metadata. If you want that e2e run before merge, say so and I'll trigger it.FYI (not fixed here, kept out of this diff)
kernel/package.jsonis0.0.165whilepackage-lock.jsonrecords0.0.163.npm installnormalized it; I reverted that hunk to keep this PR scoped to zod. Left as-is on master.