Repository navigation
chore: bump Bun to 1.4.4 - #58088
Merged
Merged
chore: bump Bun to 1.4.4#58088
Conversation
Co-authored-by: Test User <test@test.com> (cherry picked from commit 0caae60)
opencode-agent
Bot
requested review from
Brendonovich and
Hona
as code owners
October 22, 2026 11:15
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.
Bumps Bun from 1.3.14 to 1.4.4 on
v1, so v1 builds and ships on the same Bun asdev(#58087). This moves v1 from the last 1.3.x release to Bun 1.4.packageManager,bun-nodeand stats server images → 1.4.4@types/buncatalog 1.3.13 → 1.4.3 (latest published), plus abun-typesoverride pinned to 1.4.4 so types track the runtime, as ondevsince chore: upgrade Bun to 1.4.1 and re-enable bytecode #47271bun-typestominimumReleaseAgeExcludes: Oven publishes it alongside each Bun release, so the 3-day gate otherwise blocks a same-day bumpV=1.4.2override insetup-bun: it existed because 1.3.14 lacked the install: don't re-apply a patch per peer variant in isolated installs oven-sh/bun#33646 fix, and with 1.4.4 it would downgrade Windowsbun.lockregenerated with Bun 1.4.4. Only@types/bunandbun-typeschange in the resolved package set; the rest is re-hoistingBackports
dev's Bun 1.4 changes:nix/hashes.jsonafter mergePointer | bigint, and@ff-labs/fff-bun@0.9.4ships raw TypeScript source, so core failed typecheck. Upgrades to 0.10.5, the versiondevships, whose compiled type definitions avoid this. The core API is unchanged (no source edits; core typechecks), and lockfile integrity hashes matchdev. It also brings fff's wildcard gitignore fix (fix(core): honor wildcard gitignore rules in FFF #43988)Unexpected server response: 401. Under 1.4,wsno longer gets Bun's built-in WebSocket replacement; the codex proxy path still tunnels throughHTTP(S)_PROXYChecked with 1.3.14 and 1.4.4: fresh frozen install, ui 27/27, session-ui 83/83, app unit 724/724, and matching opencode plugin/provider/tool/util/session test results apart from the websocket message. Compiled linux-x64 binaries smoke the same before and after:
serveplus config/agent/project/session/doc endpoints,run --attach,runagainst a free model including a tool call,modelsandsession list. The binary grows 187.3 → 207.2 MB, mostly from the larger Bun runtime.Requested by: @Hona (Hona via Slack)