Repository navigation
Conversation
cache.ruby-lang.org publishes mswin builds of the 3.4 and 4.0 releases, so `mswin-X.Y` installs them and `mswin-head` the master build. `mswin` and `ruby-mswin` keep installing master until their known users move to `mswin-head`. 3.3 and older are left out because their mkmf ignores ENV['PKG_CONFIG'] and would not use the vcpkg pkgconf. mswin is CRuby built with MSVC, so it stays the ruby engine and the CRuby rules apply. `common.inputs.mswin` only selects the builds and keeps them out of the tool cache, where runners hold RubyInstaller builds of the same versions, and in their own bundler-cache key. Co-authored-by: なつき <i@ntk.me> Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The README said what mswin is but not when to use it, which leaves users unsure which of the two Windows builds to choose. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
14493a1 to
c82cc17
Compare
| | `ruby` | 1.9.3, 2.0.0, 2.1.9, 2.2, all versions from 2.3.0 until 4.1.0-preview1, head, debug, mingw, ucrt | | ||
| | `jruby` | 9.1.17.0 - 10.1.3.0, head | | ||
| | `truffleruby` | 19.3.0 - 40.0.0, head | | ||
| | `truffleruby+graalvm` | 21.2.0 - 40.0.0, head | |
There was a problem hiding this comment.
It might be easier to understand, if we add another row to the table naming mswin and a rough overview of the available versions, instead of most of the text below. Technically mswin is the same cruby interpreter, but it has a very different ecosystem.
There was a problem hiding this comment.
I'd like to explore the idea I posted in the earlier and see what's everyone's thought: #971 (comment)
There was a problem hiding this comment.
I'd keep mswin here, as it selects a platform build of CRuby rather than a VM variant like GraalVM. A common syntax for CRuby variants would also rename ruby-asan and ruby-debug, so I think it fits better in a separate issue.
There was a problem hiding this comment.
I shortened the paragraph and moved the version overview into its first sentence. I kept mswin out of the table, since its rows are interpreters.
The paragraph spent two sentences on what one can say. mswin stays out of the table, whose rows are interpreters. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This adds the release builds split out of #971. cache.ruby-lang.org publishes mswin builds of the 3.4 and 4.0 releases, so
mswin-3.4installs the latest 3.4.x andmswin-headthe master build.Nothing changes for existing users, as
mswinandruby-mswinstill install the master build. larskanis suggested in #972 (comment) thatmswinshould install the latest release. I'll do that in a follow-up, after sending PRs that move the public workflows testing master withmswintomswin-head. I'll take care of the ruby org repositories like ruby/openssl.The README now says when to pick
mswinover the default RubyInstaller builds. I build and publish the mswin packages in ruby/actions and will maintain their support here.mswin is CRuby built with MSVC, not another implementation, so it stays the
rubyengine and goes through every CRuby rule. A flag only selects the mswin builds and keeps them apart from the RubyInstaller builds of the same versions in the tool cache and the bundler-cache key.I ran the built
dist/index.json my x64 and arm64 Windows machines.mswin,ruby-mswinandmswin-headinstalled the master build,mswin-3.4installed 3.4.12, and the mswin steps oftest.ymlpassed.Generated with Claude Code