Repository navigation
docs: record the Vitest and Stryker runtime outcomes for the Bun migration - #4027
Merged
Merged
Conversation
fro-bot
approved these changes
Oct 20, 2026
fro-bot
left a comment
Owner
There was a problem hiding this comment.
Verdict: PASS
The recorded Node exceptions match the package scripts, CI commands, and mutation runner. Retaining Node after failed parity checks follows the plan's acceptance criteria.
Blocking issues
None
Non-blocking concerns
None
Missing tests
None. This PR changes only the migration record; it introduces no executable behavior requiring new tests. Historical runtime counts were not independently reproduced.
Risk assessment (LOW) + rationale
Documentation-only closure; no changes to dependencies, permissions, workflows, or runtime selection.
Run Summary
| Field | Value |
|---|---|
| Event | pull_request |
| Repository | fro-bot/.github |
| Run ID | 39470124773 |
| Cache | hit |
| Session | ses_ea58befc0ffeZTxM46gCPWrueJ |
| Verification | Reviewed the complete PR diff and runtime configuration; git diff --check passed. Test suites were not rerun. |
| Review coverage | Manual review; structured review helper references were unavailable due to filesystem access restrictions. |
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.
Closes out the pnpm → Bun migration plan (
docs/plans/2026-10-19-002-refactor-bun-migration-plan.md). This PR changes only the plan document. No code or guidance changes.Changes
completed, and all seven units are checked off.bun run installfetches re2's prebuilt binary, but that binary is built for Node's ABI (NODE_MODULE_VERSION137). Bun 1.4.3 requires 147, so RE2 loads only under Node andcheck:renovate-configstays on Node.bun --bun vitest run, the full suite matches Node on every file and test name (5648 passed, 43 skipped, 3 todo), and so does the release real-plugin suite (105). The three Renovate real-plugin suites fail 13 of 102 tests on Bun because of the same RE2 ABI mismatch. Vitest stays on Node.bunx --bun stryker run, Stryker instruments all 2,733 mutants but runs none, because it cannot load@stryker-mutator/vitest-runner. The cause is Vite 8.0.16 callingError.captureStackTraceon an object that is not anError; Node accepts that call and Bun 1.4.3 rejects it. Stryker stays on Node, where the baseline is clean.postUpgradeTasks, the Bun script shell and the droppedts-declaration-locationentry: all confirmed working.Error.captureStackTracecall.The guidance already lists Vitest and Stryker as Node exceptions.