Issue #20004 has been updated by katei (Yuta Saito). If the problem will be solved by fixing tests and we will be able to confirm the problem is only for build-phase, re-landing the defaulting change would make sense to me. But if it's more complicated situation, it would be risky to re-land and would be better to postpone to next-next release. ---------------------------------------- Bug #20004: Release CI is broken with Ruby master https://bugs.ruby-lang.org/issues/20004#change-105377 * Author: hsbt (Hiroshi SHIBATA) * Status: Closed * Priority: Normal * Backport: 3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN ---------------------------------------- From 3 week ago, Release action of master is broken. https://github.com/ruby/actions/actions/runs/6599016994/job/17927644579#step... ``` Invoking `/Users/runner/work/actions/actions/snapshot-master/ruby -rrubygems /Users/runner/work/actions/actions/snapshot-master/bin/gem --backtrace build lib/bundler/bundler.gemspec` failed with output: ---------------------------------------------------------------------- dyld[42417]: Library not loaded: '/usr/local/lib/libruby.3.3.dylib' Referenced from: '/Users/runner/work/actions/actions/snapshot-master/ruby' Reason: tried: '/usr/local/lib/libruby.3.3.dylib' (no such file), '/usr/lib/libruby.3.3.dylib' (no such file) ---------------------------------------------------------------------- ``` It is related with #19422 -- https://bugs.ruby-lang.org/