From: "Eregon (Benoit Daloze) via ruby-core" Date: 2025-12-30T21:32:22+00:00 Subject: [ruby-core:124405] [Ruby Misc#21804] Getting setup-ruby Earlier Issue #21804 has been updated by Eregon (Benoit Daloze). Earlopain (Earlopain _) wrote in #note-6: > But I think the bigger issue here is that windows builds are not first-party. So even if the release process gets adapted, issues like what [@mdalessio (Mike Dalessio)](/users/443) wrote above will not be solved. Yeah, that's a good point, so then we'd need to e.g. give permission to @larskanis to merge & release setup-ruby then, since he does the RubyInstaller releases. I'd be OK with that, but it starts to be quite a few people and easy to forget, so currently I'm thinking the auto-merge + auto-release approach with appropriate guardrails is better and avoids adding even more work for Ruby releasers and myself, and I'm sure they are already very busy. ---------------------------------------- Misc #21804: Getting setup-ruby Earlier https://bugs.ruby-lang.org/issues/21804#change-115923 * Author: koic (Koichi ITO) * Status: Open ---------------------------------------- ruby/setup-ruby is commonly used for development in OSS projects and real-world Rails applications. https://github.com/ruby/setup-ruby This is not specific to Ruby 4.0.0. There is often a delay between a Ruby release and the availability of the corresponding version in setup-ruby. setup-ruby is maintained by the ruby organization and may take a few days to become available after a Ruby release. In contrast, ruby-build is maintained by the rbenv organization and tends to become available shortly after a Ruby release. This makes it easier to start using new Ruby versions immediately. If setup-ruby maintained by the ruby organization were released shortly after a Ruby release, users could start using new Ruby versions sooner. It is difficult to determine whether this issue should be registered on bugs.ruby-lang.org. Since setup-ruby is maintained by the ruby organization, this issue is being opened to raise awareness of the situation. If this is not appropriate, please feel free to close it. Thank you for your continued maintenance and for releasing Ruby. -- https://bugs.ruby-lang.org/ ______________________________________________ ruby-core mailing list -- ruby-core@ml.ruby-lang.org To unsubscribe send an email to ruby-core-leave@ml.ruby-lang.org ruby-core info -- https://ml.ruby-lang.org/mailman3/lists/ruby-core.ml.ruby-lang.org/