ci: move the Bun trial lane and bun-types to 1.4.1 - #674
Merged
Merged
Conversation
Bun 1.4.1 shipped today. The trial lane in ci.yml follows it, and the root bun-types floor moves with it. Every other workflow keeps pinning the primary version (1.3.14); scripts/workflow-bun-version.test.ts enforces that and stays green. The lockfile was regenerated on 1.3.14 so the primary lane's --frozen-lockfile install is unchanged. Verified on 1.4.1: bun install --frozen-lockfile, build:clean, typecheck, test:bun (6495 pass / 0 fail), test:examples.
bun-types 1.4.1 restores the generic process.off signature that 1.4.0 shadowed with its memoryPressure overload (oven-sh/bun#40004), and the root floor now sits at ^1.4.1, so the EventEmitter cast in registerProcessTeardown has nothing left to work around. No runtime change; typecheck and the Application lifecycle tests stay green.
7nohe
force-pushed
the
claude/bun-1-4-1-upgrade-50c24a
branch
from
September 4, 2026 22:29
34d7d20 to
e93d7d1
Compare
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
1 participant
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
Bun 1.4.1 shipped on 2026-09-04. This moves the CI trial lane from 1.4.0 to 1.4.1 and the root
bun-typesfloor to^1.4.1. Every other workflow keeps pinning the primary version (1.3.14);scripts/workflow-bun-version.test.tsenforces that and stays green. The lockfile was regenerated on 1.3.14, so the primary lane's--frozen-lockfileinstall is unchanged.The second commit drops the
EventEmittercast inregisterProcessTeardown: bun-types 1.4.1 restores the genericprocess.offsignature that 1.4.0 shadowed (oven-sh/bun#40004), and with the floor at^1.4.1the workaround had nothing left to cover. No runtime change.Why not promote 1.4 to primary yet
On
main, the 1.4.0 lane is 20 green / 19 red over the last 40 runs. Every red is the same class: 30s timeouts in subprocess-heavy tests (publish-agent-catalog,audit: changeset gate) under the push-only--paralleltrial, not a runtime regression. Promotion is a separate decision once that flag's numbers settle; 1.4.1 lands 476 commits including a spawnSync/GC keep-alive fix (oven-sh/bun#40508), so the soak restarts here.Verification (Bun 1.4.1, local)
bun install --frozen-lockfilebun run build:cleanbun run typecheckbun run lintbun run test:bun(6495 pass / 0 fail / 98 skip, before the rebase onto build: add an oxlint gate with type-aware no-floating-promises #657)bun run test:examplesscripts/workflow-bun-version.test.tsafter the rebase