Repository navigation
ci(bun): Test the oldest supported Bun version and the newest 1.4 - #25203
Merged
JPeer264 merged 2 commits intoOct 12, 2026
Merged
Conversation
JPeer264
added this pull request to stack #25205
October 9, 2026 06:50
Member
Author
|
bugbot run |
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
✅ Bugbot reviewed your changes and found no new issues!
Comment @cursor review or bugbot run to trigger another review on this PR
Reviewed by Cursor Bugbot for commit a257569. Configure here.
![sentry[bot]](https://avatars.githubusercontent.com/in/12637?s=60&v=4){kind=small}
s1gr1d
approved these changes
Oct 9, 2026
andreiborza
approved these changes
Oct 9, 2026
The Bun unit and integration test jobs now run on Bun 1.3.14, the oldest supported version, and on `1.4`, which setup-bun resolves to the newest 1.4.x release on each run. Older 1.3.x releases are not supported: before 1.3.4 `bun:test` has no `jest.advanceTimersByTime`, and up to 1.3.13 an Anthropic stream that fails midway records its response text twice. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
JPeer264
force-pushed
the
jp/bun-ci-version-matrix
branch
from
October 12, 2026 11:19
e75d26b to
b1bee22
Compare
JPeer264
added a commit
that referenced
this pull request
Oct 12, 2026
…25204) > *Pro Tip*: It is better to review it with the option "Hide whitespaces": https://github.com/getsentry/sentry-javascript/pull/25204/changes?w=1 follow up to #25203 ## Description This adds a `bunMin` requirement to `supports` and moves the Node suites that pass only on Bun 1.4 from the Bun exclude lists to `runIf(supports({ bunMin: '1.4.0' }))`. The Bun 1.4 job now runs them, and the 1.3.14 job skips them. These are the outgoing `node:http` suites (#23881), `system-error` and `tracer-start-active-span-error`. ```ts describe.runIf(supports({ bunMin: '1.4.0' }))('outgoing http', () => {}); ``` Most of the diff is new indentation. Hide whitespace to review. ## Known issues - `system-error` stays excluded in the `@sentry/bun` project, because `@sentry/bun` does not include `nodeSystemErrorIntegration`. - `tracer-start-active-span-error` passed on Bun 1.3.14 on macOS, but the old exclude comment says that it fails there, so it keeps the 1.4 minimum. --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
47 tasks done
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
3 participants
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.
closes #23890
closes JS-3516
Description
This runs the Bun unit and integration tests on Bun 1.3.14 and on
1.4.setup-bunresolves1.4to the newest 1.4.x release on each run.Version decisions
CI pinned 1.3.14 before, and it stays the oldest version that CI tests, because older releases fail tests. On 1.3.4 to 1.3.13, an Anthropic stream that fails midway records its response text twice, and before 1.3.4,
bun:testhas nojest.advanceTimersByTime.1.4floats and blocks merges, so a broken Bun patch fails CI; the issue suggested a non-blockinglatestleg instead, which would run 1.4.2 twice until Bun 1.5 comes out.Known issues