Repository navigation
Correctly handle bundler 4 being available #827
Description
On actions that run against ruby-dev, it currently prints the following output (example workflow):
Using Bundler 2 shipped with ruby-head
But ruby-head ships with bundler 4. There is also the following deprecation from bundler:
[DEPRECATED] Using the
configcommand without a subcommand [list, get, set, unset] is deprecated and will be removed in the future. Usebundle config set --local path /home/runner/work/rubocop/rubocop/vendor/bundleinstead.
There is a bit of code to handle bundler 1/2 for a variety of different configurations already, so I won't open a PR for this. It's a bit too complicated to really understand what is going on for me
Metadata
Metadata
Assignees
Labels
No labels
Activity
Petercopter commentedon Dec 4, 2025
Bundler 4 was released today and I'm seeing the same message with Ruby 3.4.7
eregon commentedon Dec 4, 2025
It's not that complicated IMO, but sure I can take care of that.
Account for Bundler 4
Account for Bundler 4
Account for Bundler 4
eregon commentedon Dec 4, 2025
Not that simple either, I'll admit, due to numerous Bundler/RubyGems bugs we have to work around and
required_ruby_versionnot working for many Ruby / RubyGems versions:#832
Account for Bundler 4
eregon commentedon Dec 4, 2025
Argh, on Bundler 1
bundle config set --local path foobarresults in settingBUNDLE_SET: "--local path foobar"in~/.bundle/config, so not local and not the correct value :/And
bundle config --local set path foobarresults in settingBUNDLE_SET: "path foobar"in.bundle/config, so local but not correct value.Account for Bundler 4
Account for Bundler 4
Petercopter commentedon Dec 5, 2025
👍 @eregon thank you!