Repository navigation
Conversation
bun audit --audit-level high fails on main after this week's advisories for undici (GHSA-xjj6-f33q-929c, GHSA-4w7w-5xrc-9h26, GHSA-2m5v-pch6-74hx, GHSA-qrxm-fqhp-jwvm), zod (GHSA-mrhx-c7xc-m3w5) and body-parser (GHSA-27r3-jxmh-p828). - zod 4.4.3 -> 4.6.6: the three exact pins move to the patched release, and a zod override covers cail-identity 5.2.6 and cail-log 0.6.4, which pin 4.4.3 exactly and have no newer release. - undici 7.29.1 -> 7.30.1 through a root override, as in cail-tools-admission #363. Miniflare pins 7.29.1 exactly and Bun 1.3.14 ignores nested overrides, so the override also applies to jsdom, which moves from undici 8.12.3 (already patched) to 7.30.1. jsdom runs only in the frontend Vitest suite, which passes on 7.30.1. - body-parser 2.3.0 -> 2.4.0 through an override. 2.4.0 is within express's ^2.2.1 range, but Bun has no in-range refresh for a transitive package. - qs override 6.16.0 -> 6.16.1: body-parser 2.4.0 requires ^6.16.1, and 6.16.1 also fixes GHSA-6pq8-jhm2-2vcw (moderate). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Wrangler 4.153.0 pins miniflare 5.20261023.0-beta, which pins undici 7.30.1 itself. The root override is no longer needed, so jsdom resolves its own undici 8.12.3 again instead of being forced below its declared range. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This branch has not been deployed
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
The CI step
bun audit --audit-level highfails on main because of advisories published this week:Packages changed
cloudflareandfrontendexact pins bumped. Azodoverride covers@cuny-ai-lab/cail-identity5.2.6 andcail-log0.6.4, which pin 4.4.3 exactly and have no newer release.cloudflare. Its miniflare 5.20261023.0-beta pins undici 7.30.1 itself.^2.2.1range.No direct dependency changes major version.
Notes for review:
^8.9.0. Wrangler 4.153.0 is the first release whose miniflare pins undici 7.30.1. It was published on 2026-10-26, inside the seven-daymin-release-agein~/.npmrc, and Stephen approved lifting that age limit for this one install (bun install --minimum-release-age=0).upload_source_mapsisn't set, so stack traces in logs point at the original source. This repo doesn't setupload_source_maps. The staging dry run uploads 9,172.57 KiB, or 1,914.70 KiB gzipped.bun update body-parseradds it as a root dependency, and deleting its lock entry re-resolves about 116 unrelated packages. So this uses an override, following the repo's existing pattern for patched transitive pins.qs ^6.16.1, so the existing 6.16.0 override had to move. 6.16.1 also fixes GHSA-6pq8-jhm2-2vcw (moderate).Verification
All commands ran with the repo-pinned Bun 1.3.14 (first on PATH, so package scripts used it too) and Node 22.23.4.
bun.lockstays at"lockfileVersion": 1.bun audit --audit-level high: exit 0 (on main: exit 1, with 6 high findings in body-parser, undici and zod).bun install --frozen-lockfileafter removing allnode_modules: exit 0.bun run check: exit 0. It covers lint, typecheck, backend tests (474 passed), frontend Vitest (43 files, 284 tests passed), tool tests (22 passed), build, and the stagingwrangler deploy --dry-run. Rerun after the wrangler update, from a frozen install of the new lockfile: exit 0, with the dry run on wrangler 4.153.0.bun run devplusbun run smoke, with the CI.dev.varsvalues): exit 0. Every step passed, including the isolated runtime and deletion of the synthetic workspace. This ran on the first commit; CI's process smoke job covers the wrangler update.The unfiltered
bun auditstill reports 18 moderate and 2 low findings, mostly in hono. They are outside this high-severity fix and don't fail the CI gate.🤖 Generated with Claude Code