Benoit Daloze

I fixed this for CRuby 3.0.x with https://github.com/ruby/ruby-builder/actions/runs/11825221988/job/32948504823 https://github.com/ruby/ruby-builder/actions/runs/11825503027 and verified that works in https://github.com/ruby/setup-ruby/actions/runs/11826456846/job/32952496665#step:15:7 Note that 3.0.7 is in the hostedtoolcache and so there it still uses 1.1 from...

As far as I can tell from https://github.com/actions/runner-images/issues/10817 [email protected] will remain on runners where it's installed, so it will keep working and there is nothing to change here.

FWIW TruffleRuby uses `--no-cache` for testing and it uses a set of pre-downloaded `.gem` files: https://github.com/search?q=repo%3Aoracle%2Ftruffleruby+%2F--no-cache%2F&type=code It's used in combination with `--local` like `bundle install --local --no-cache`. I think the...

Also potentially removing all previews and RCs (except 3.5.0-preview1 since 3.5.0 is not out yet) since those seem useless once the real corresponding release is out (i.e., nobody should use...

Maybe the rule to be simpler should be "remove every EOL Ruby" which would almost match the above but also include Ruby 2.3 - 3.1 (which is maybe too aggressive)....

> What's the reason for removing old Rubies? * Removing known broken builds like 2.2 and other old suspected-(partially maybe)-broken builds. * 1.9 is only built on very few images,...

Uploading new releases now gives: https://github.com/ruby/ruby-builder/actions/runs/17772707458/job/50512700348 ``` Run gh release upload "toolcache" "truffleruby+graalvm-25.0.0-macos-13-arm64.tar.gz" HTTP 422: Validation Failed (https://uploads.github.com/repos/ruby/ruby-builder/releases/33599578/assets?label=&name=truffleruby%2Bgraalvm-25.0.0-macos-13-arm64.tar.gz) file_count limited to 1000 assets per release ``` So this is becoming...

> Also potentially removing all previews and RCs (except 3.5.0-preview1 since 3.5.0 is not out yet) since those seem useless once the real corresponding release is out (i.e., nobody should...

@ntkme Yes, that seems a simple-ish way, however it then loses the ability to version per "kind of builds", for example in the past we have tried: * --enable-shared vs...

One more thought is we could use the downloads stats to find out little-used builds: https://tooomm.github.io/github-release-stats/?username=ruby&repository=ruby-builder 99 are `Downloaded 0 times`, many seem cases of a new runner (ubuntu-*-arm64) and...