Make `mswin` tag use a stable release

[ianks]

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 a mswin-head tag for testing against Ruby head.

[MSP-Greg]

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)?

[MSP-Greg]

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...

[eregon]

FWIW there is now 3.4-asan, a stable version of the ASAN build, see https://github.com/ruby/setup-ruby/issues/682 and https://github.com/ruby/ruby-dev-builder/pull/15. I think 3.4-mswin would be a good name for it.

Obviously up to you for whether it's worth the effort, etc, it's just a name suggestion from my part.