cap production bundler:install does not fetch new bundler version

[mohamedhafez]

When your Gemfile.lock was made with a version of bundler that is different from the one being used to execute bundle install, it is supposed to fetch that version of bundler, install it, and restart the command with that version of bundler. It works when I just go into my deployment directory and run bundle install, but for some reason when I run cap production bundler:install, it does not do that part, and just uses whatever the current bundler is.

bundler: 2.5.16 Gemfile.lock bundler 2.5.15 capistrano-bundler: 2.1.0 capistrano: 3.17.3

.bundle/config:

---
BUNDLE_DEPLOYMENT: "true"
BUNDLE_PATH__SYSTEM: "true"
BUNDLE_JOBS: "8"
BUNDLE_WITHOUT: "development:test"

I'm using jruby 9.4.8.0 (compatible with ruby 3.1.4)

[mohamedhafez]

Ah my bad I needed to turn off bundle_check_before_install, because the only thing that was changing was the bundler version when I was testing. Personally I think that might be a better default just so we can pick up any security patches in bundler itself, but those are rare anyway