Skip to content

build: upgrade to bun 1.4.2 - #475

Open
ilbertt wants to merge 5 commits into
mainfrom
claude/bun-v1-4-1
Open

build: upgrade to bun 1.4.2#475
ilbertt wants to merge 5 commits into
mainfrom
claude/bun-v1-4-1

Conversation

@ilbertt

@ilbertt ilbertt commented Sep 4, 2026

Copy link
Copy Markdown
Owner

Upgrade the pinned Bun toolchain and API Docker image to 1.4.2, and pin @types/bun exactly to 1.4.2.

@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Sep 4, 2026

Copy link
Copy Markdown

Deploying with  Cloudflare Workers  Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status Name Latest Commit Preview URL Updated (UTC)
✅ Deployment successful!
View logs
nibrun-www c53a5dc Commit Preview URL

Branch Preview URL
Sep 08 2026, 08:52 AM

@ilbertt ilbertt changed the title build: upgrade to bun 1.4.1 build: upgrade to bun 1.4.2 Sep 5, 2026
ilbertt added a commit that referenced this pull request Sep 6, 2026
… audit comes back empty (#508)

Closes #507.

`bun audit` reported 13 advisories, all transitive: js-yaml (the one the
issue names), fast-uri, nanoid and qs. Every one clears inside its
parent's existing range, so no override was needed — js-yaml lands on
4.3.2, which also carries the !!omap fix the report did not mention.
Audit is now clean.

Everything else moved to the head of its declared range too, plus the
SHA-pinned actions and the dev-only dozzle image.

**Biome stays on 2.5.6.** It was bumped here and had to come back:
2.5.12 does not terminate on this repo once `node_modules` exists. The
type-aware nursery rules (`noFloatingPromises`, `useAwaitThenable`) walk
it for declarations and never return — CI's `codestyle` job sat at 19
minutes on flat memory. Turning just those two rules off drops the same
run to 924ms, and 2.5.8 hangs identically while 2.5.7 is clean, which
places it in the series biomejs/biome#11310 tracks. 2.5.9–2.5.11 finish
but at 13–16s against 2.5.6's 4s, so the pathology is already there,
only bounded. Worth revisiting once that's fixed upstream.

Left alone: **bun 1.4.0 → 1.4.2**, already #475.
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