Open ianks opened 6 months ago
That would be a big breaking change.
Other people have asked for mswin release builds. I'm wondering if it's time to have release builds, maybe starting with Ruby 3.2, as the current vcpkg OpenSSL is 3.2.1.
Maybe setup-ruby could use an ms
prefix or suffix, so something like ms-3.2
or 3.2-ms
(or ms-3.2.3
or 3.2.3-ms
)?
Re the workflow you linked to, have you thought about running an MSY2 head build (head
or ucrt
)?
Or, wondering if the failure is mswin specfic...
Testing against
ruby-head
is hard because it can introduce subtle changes that break CI. Overall, it can cause a lot of toil for developers.I propose that
mswin
reference on GitHub actions reference the latest stable ruby release, and we introduce amswin-head
tag for testing against Ruby head.