Issue #21804 has been updated by mdalessio (Mike Dalessio).
https://github.com/ruby/setup-ruby/pull/844 got merged the same day, what would you expect?
A counter-example, though, is that the PR for windows support (https://github.com/ruby/setup-ruby/pull/847) took 3 days to get merged. I think @koic's original point is valid -- setup-ruby is an important foundational project depended upon by many (all?) downstream Ruby projects. A delay in releasing support in setup-ruby for new Rubies will cascade and multiply delays down the dependency chain in ways that are painful for other maintainers and users. In my case, because the Windows PR had not been merged, I was blocked from shipping Ruby-4-compatible native gems for sqlite3 and nokogiri. I eventually managed to ship these gems in a timely manner by forking setup-ruby and doing the work myself (see https://github.com/ruby/setup-ruby/pull/847). It wasn't _hard_ work, but it's work that's needlessly being imposed upon downstream maintainers. The community as a whole will benefit from faster turnaround time.
Maybe it'd make sense and possibly safe enough to automatically merge PRs by ruby-builder-bot, after they pass CI of course ... if someone is interested, please make a PR to setup-ruby.
I will take a look. ---------------------------------------- Misc #21804: Getting setup-ruby Earlier https://bugs.ruby-lang.org/issues/21804#change-115909 * 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/