ruby.git/lib/bundler/settings.rb, branch v4.0.2 The Ruby Programming Language [ruby/rubygems] Add support for BUNDLE_LOCKFILE environment variable 2025-11-20T23:01:03+00:00 Jeremy Evans code@jeremyevans.net 2025-11-11T02:23:58+00:00 010b23a7cfc4a20371d74406f9f0563331a233fd This specifies the lockfile location. This allows for easy support of different lockfiles per Ruby version or platform. https://github.com/ruby/rubygems/commit/b54d65bc0a Co-authored-by: Sutou Kouhei <kou@cozmixng.org> Co-authored-by: Colby Swandale <996377+colby-swandale@users.noreply.github.com> 
This specifies the lockfile location. This allows for easy support
of different lockfiles per Ruby version or platform.

https://github.com/ruby/rubygems/commit/b54d65bc0a

Co-authored-by: Sutou Kouhei <kou@cozmixng.org>
Co-authored-by: Colby Swandale <996377+colby-swandale@users.noreply.github.com>
[ruby/rubygems] Warn users that `bundle` now display the help: 2025-11-19T01:37:57+00:00 Edouard CHIN chin.edouard@gmail.com 2025-11-17T20:33:58+00:00 3b9539176bc37b3e95864b04b0eef1263f434eef - In https://github.com/ruby/rubygems/commit/31d67ecc056fb5a9193bc66a6e69e21576a87702 we enforced the new behaviour where running `bundle` no longer installs gems but displays the help. Users now have a way to configure their preferred default command using the `BUNDLE_DEFAULT_CLI_COMMAND` flag. With the preview of Ruby 4.0 now being released, some people will start to see this new change. The problem is that the previous behaviour had existed for like an eternity and we didn't warn users about this change in advance. I'd like to provide a deprecation/warning cycle because this is confusing users already and this breaks various CI setup that now needs to be changed immediately. https://github.com/ruby/rubygems/commit/e415480ac5 
- In https://github.com/ruby/rubygems/commit/31d67ecc056fb5a9193bc66a6e69e21576a87702
  we enforced the new behaviour where running `bundle` no longer
  installs gems but displays the help.
  Users now have a way to configure their preferred default command using
  the `BUNDLE_DEFAULT_CLI_COMMAND` flag.

  With the preview of Ruby 4.0 now being released, some people will
  start to see this new change.

  The problem is that the previous behaviour had existed for like an
  eternity and we didn't warn users about this change in advance.
  I'd like to provide a deprecation/warning cycle because this is
  confusing users already and this breaks various CI setup that now
  needs to be changed immediately.

https://github.com/ruby/rubygems/commit/e415480ac5
[rubygems/rubygems] Make update_requires_all_flag to settings 2025-10-10T10:12:35+00:00 Hiroshi SHIBATA hsbt@ruby-lang.org 2025-10-10T06:47:10+00:00 4bf14758336fd51c3c45a714c944b7d69ec9bed3 https://github.com/rubygems/rubygems/commit/631a55be91 
https://github.com/rubygems/rubygems/commit/631a55be91
[rubygems/rubygems] Make default_cli_command flag to settings 2025-10-10T07:59:34+00:00 Hiroshi SHIBATA hsbt@ruby-lang.org 2025-10-10T06:30:31+00:00 aac6f0681536c8ca58638714c2cc8d7e35aa6a37 https://github.com/rubygems/rubygems/commit/31d67ecc05 
https://github.com/rubygems/rubygems/commit/31d67ecc05
[rubygems/rubygems] Make global_gem_cache flag to settings 2025-10-10T06:27:47+00:00 Hiroshi SHIBATA hsbt@ruby-lang.org 2025-10-10T05:10:45+00:00 b38846db18c34213077a9efaa7b28683b42f12a3 https://github.com/rubygems/rubygems/commit/bfe15a4712 Co-authored-by: David Rodríguez <2887858+deivid-rodriguez@users.noreply.github.com> 
https://github.com/rubygems/rubygems/commit/bfe15a4712

Co-authored-by: David Rodríguez <2887858+deivid-rodriguez@users.noreply.github.com>
[rubygems/rubygems] Replaced Bundler.feature_flag.plugins? to Bundler.settings 2025-10-10T04:06:28+00:00 Hiroshi SHIBATA hsbt@ruby-lang.org 2025-10-10T02:30:41+00:00 282b0e3a8342de5fb5466f7b85ead83a9f5ac9f6 https://github.com/rubygems/rubygems/commit/ced8ef3a12 Co-authored-by: David Rodríguez <2887858+deivid-rodriguez@users.noreply.github.com> 
https://github.com/rubygems/rubygems/commit/ced8ef3a12

Co-authored-by: David Rodríguez <2887858+deivid-rodriguez@users.noreply.github.com>
[rubygems/rubygems] Switch `cache_all` to be `true` by default 2025-09-19T10:30:10+00:00 David Rodríguez 2887858+deivid-rodriguez@users.noreply.github.com 2025-09-09T17:19:31+00:00 a4c277733b10ff1ad484689c1a256032c39cea87 And make it a standard setting. https://github.com/rubygems/rubygems/commit/17e356fa94 
And make it a standard setting.

https://github.com/rubygems/rubygems/commit/17e356fa94
[rubygems/rubygems] Switch `lockfile_checksums` to be true by default 2025-09-19T10:30:10+00:00 David Rodríguez 2887858+deivid-rodriguez@users.noreply.github.com 2025-09-09T17:20:53+00:00 44a4f88159127e8d49bd3dfddcaa32233f57dd85 https://github.com/rubygems/rubygems/commit/47c3dc19ee Co-authored-by: Jonathan Barquero <jonbarlo@hotmail.com> 
https://github.com/rubygems/rubygems/commit/47c3dc19ee

Co-authored-by: Jonathan Barquero <jonbarlo@hotmail.com>
[rubygems/rubygems] Remove `allow_offline_install` setting 2025-09-16T08:17:32+00:00 David Rodríguez 2887858+deivid-rodriguez@users.noreply.github.com 2025-09-09T17:18:54+00:00 6b0af3135264351d0bbaaf5cf6b207a9c84b6e76 And let the feature always be enabled, so I'm not sure why we'd need this configurable. https://github.com/rubygems/rubygems/commit/5a27f0c1e3 
And let the feature always be enabled, so I'm not sure why we'd need
this configurable.

https://github.com/rubygems/rubygems/commit/5a27f0c1e3
[rubygems/rubygems] Complete remembered options removal 2025-09-11T02:54:49+00:00 David Rodríguez 2887858+deivid-rodriguez@users.noreply.github.com 2025-09-09T12:37:09+00:00 ecd1284bf246ae739890d154706f4f533bc8d77e https://github.com/rubygems/rubygems/commit/573ffad3ea 
https://github.com/rubygems/rubygems/commit/573ffad3ea