CI failures for mingw builds related to Bundler 4
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 990
- Forks
- 369
- Avg merge
- 18m
- Merged PRs (30d)
- 3
Description
@MSP-Greg Hello, when you have some time could you check these CI failures for mingw?
https://github.com/ruby/setup-ruby/actions/runs/18399031835/job/52423942962?pr=817
https://github.com/ruby/setup-ruby/actions/runs/18399031835/job/52423942981?pr=817
C:\Windows\system32\cmd.exe /D /S /C "D:\ruby-mingw\bin\bundle.bat install --jobs 4"
[REMOVED] Found x64-mingw32 in lockfile, which is no longer supported as of
Bundler 4.0.
Error: The process 'D:\ruby-mingw\bin\bundle.bat' failed with exit code 9
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the two linked GitHub Actions jobs and reproduce the mingw bundle install failure shown in the log. Trace the Bundler 4 rejection of x64-mingw32 in the lockfile; done means the affected mingw CI jobs complete successfully without the exit-code-9 failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, ruby
- Domain
- build-system, ci-cd
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100