Issue #19886 has been updated by hsbt (Hiroshi SHIBATA). Thank you for reporting this. I confirmed it. It caused `bundle exec ruby` couldn't call `Bundler.setup`. It's working with that. ``` $ cat test.rb #!/usr/bin/env ruby require "base64" $ bundle exec test.rb test.rb:3: warning: base64 will be not part of the default gems since Ruby 3.4.0. Add base64 to your Gemfile. Also contact author of to add base64 into its gemspec. ``` `bundle exec` will call `Bundler.setup` only script that has ruby shebang. I'm considering how call `Bundler.setup` via `bundle exec ruby`. ---------------------------------------- Bug #19886: "default->bundled gem" warning is not shown under "bundle exec" https://bugs.ruby-lang.org/issues/19886#change-104656 * Author: mame (Yusuke Endoh) * Status: Assigned * Priority: Normal * Assignee: hsbt (Hiroshi SHIBATA) * Backport: 3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN ---------------------------------------- ``` $ cat Gemfile source "https://rubygems.org" $ cat test.rb require "base64" $ bundle exec ruby test.rb $ ``` In this situation, `bundle exec ruby test.rb` should print a warning: base64 which will be not part of the default gems since Ruby 3.4.0. Note that `ruby test.rb` shows the warning, which is not needed (see #19885). ``` $ ruby test.rb test.rb:1: warning: base64 which will be not part of the default gems since Ruby 3.4.0 ``` -- https://bugs.ruby-lang.org/