ci: workaround for CI failure on Windows with Bun #277
Conversation
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
1 task
aladdin-add
approved these changes
Sep 24, 2025
This was referenced Oct 10, 2025
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.
Prerequisites checklist
What is the purpose of this pull request?
In this PR, I've fixed CI to work around a failure on Windows with Bun.
Currently, Bun CI on Windows is failing due to the newly released Rollup
4.52.0.As a workaround, I've pinned Rollup to
4.51.0.Here are the references:
https://github.com/eslint/rewrite/actions/runs/17956574548/job/51069303147
What changes did you make? (Give an overview)
In this PR, I've fixed CI to work around a failure on Windows with Bun.
Related Issues
Ref: eslint/json#154 (comment)
Is there anything you'd like reviewers to focus on?
It seems that
rollup4.52.2 has been released, but the issue above wasn't included, so I think we need to wait untilrollup4.53.0 is released.https://github.com/rollup/rollup/releases/tag/v4.52.2