Repository navigation
Correctly handle bundler 4 being available #827
Description
Activity
Bundler 4 was released today and I'm seeing the same message with Ruby 3.4.7
/opt/hostedtoolcache/Ruby/3.4.7/x64/bin/bundle config --local path /home/runner/work/projectname/projectname/vendor/bundle [DEPRECATED] Using the `config` command without a subcommand [list, get, set, unset] is deprecated and will be removed in the future. Use `bundle config set --local path /home/runner/work/projectname/projectname/vendor/bundle` instead.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
It's not that complicated IMO, but sure I can take care of that.
- added 3 commits that reference this issue
on Dec 4, 2025 Use
bundle config set --local path /home/runner/work/rubocop/rubocop/vendor/bundleinstead.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 :/
Andbundle config --local set path foobarresults in settingBUNDLE_SET: "path foobar"in.bundle/config, so local but not correct value.👍 @eregon thank you!
On actions that run against ruby-dev, it currently prints the following output (example workflow):
But ruby-head ships with bundler 4. There is also the following deprecation from bundler:
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