chore(deps): upgrade Bun to 1.4.2 - #8315
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
|
This branch was successfully 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
packageManager, packageengines, CIsetup-bun, the app/realtime/db images, and the Pi sandbox pinAsyncLocalStorageregression where a timer created insidestore.exit()or a nestedstore.run()of the same store kept the outer store value alive until it fired.lib/core/network/context.server.tsswitches outbound scope with nestedrun()/exit(), so a long timer set under it could pin the enclosing request contextbun buildvar/let renaming andworker_threads'online'ordering, plus abun installlockfile hash-mismatch panic@types/bunstays at 1.4.1 (types-only, no runtime effect)Type of Change
Testing
run()/exit(), then forced GC: 1.4.1 collected 0/200 (RSS 103 MB), 1.4.2 collected 200/200 (RSS 48 MB)node:httpresstill emitscloseon client disconnect (so Nextrequest.signalstill aborts), and numericfetchtimeoutis still ignored as documented infetch-deadline.tsbun install --frozen-lockfile,bunx turbo run type-check(26/26),bun run lint, block registry check,bun run check:audits(51 audits),bun run docs-manifest:check,bun run images:check,bun run test:scripts(179 passed)bun run test: 34,280 passed; one test timed out at 10s under full-suite load and passes when rerun alone (vitest runs on Node, not Bun)oven/bun:1.4.2-alpine; both report Bun 1.4.2Checklist
test-auditauthoring gate)