Skip to content

Add mswin release builds as mswin-X.Y and mswin-head - #979

Open
hsbt wants to merge 3 commits into
masterfrom
claude/unruffled-montalcini-d4ed93
Open

hsbt wants to merge 3 commits into
masterfrom
claude/unruffled-montalcini-d4ed93

Conversation

@hsbt

@hsbt hsbt commented Nov 18, 2026 •

Copy link
Copy Markdown
Member

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.4 installs the latest 3.4.x and mswin-head the master build.

- uses: ruby/setup-ruby@v1
  with:
    ruby-version: mswin-3.4

Nothing changes for existing users, as mswin and ruby-mswin still install the master build. larskanis suggested in #972 (comment) that mswin should install the latest release. I'll do that in a follow-up, after sending PRs that move the public workflows testing master with mswin to mswin-head. I'll take care of the ruby org repositories like ruby/openssl.

The README now says when to pick mswin over 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 ruby engine 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.js on my x64 and arm64 Windows machines. mswin, ruby-mswin and mswin-head installed the master build, mswin-3.4 installed 3.4.12, and the mswin steps of test.yml passed.

Generated with Claude Code

@hsbt
hsbt requested review from larskanis and ntkme November 18, 2026 05:46
hsbt and others added 2 commits November 18, 2026 19:26
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>
@hsbt
hsbt force-pushed the claude/unruffled-montalcini-d4ed93 branch from 14493a1 to c82cc17 Compare November 18, 2026 10:26
@hsbt hsbt changed the title Add mswin release builds as ruby-version: mswin-X.Y Add mswin release builds as mswin-X.Y and mswin-head Nov 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants