Repository navigation
The future of ruby-loco #972
Description
- For mingw based builds, it no longer makes sense to maintain support.
- For mswin based builds, ruby org is going to provide official builds for both arm64 and x64, covering both releases and head.
- For ucrt based builds,
ri2has already been consistently providing ruby-head builds for both arm64 and x64.
Given these conditions, I think it might be the time to retire the support of ruby-loco builds.
Now we have PRs like #969 and #971 already lined up, but before we proceed a bigger question is what would be the process of deprecating and/or removing support of ruby-loco. I'm opening this issue to start a discussion on what people want and what the process would look like.
There are a few considerations / questions:
- @MSP-Greg: are you still committed to maintain ruby-loco long term, and do you want to keep the support in setup-ruby?
- If we decided to commit the breaking change, we should probably have a deprecate warning period as discussed in the PRs. Is 1 month good?
- Please add other topics as needed...
Reacted by Benoit Daloze
Activity
eregon commentedon Nov 13, 2026
Thank you for opening this, I am not sure how to address this.
I would really like to hear from @MSP-Greg.
There is also no need to rush as nothing is broken right now (AFAIK), just old master builds are being used.
larskanis commentedon Nov 14, 2026
I never used ucrt or mingw builds, but was happy about the mswin binaries for CI usage and for local testing. IMHO mingw and ucrt builds don't have an advantage over ri2 builds.
The ruby-loco mswin build was simply the only one which was provided and regularly updated. Now that @hsbt provides the mswin stable branches and head builds, I think it makes sense to replace ruby-loco's mswin with mswin of @hsbt from the latest stable branch. I don't think we need deprecation warnings about mswin build, because it was latest development release, so one can expect breaking changes.