David Rodríguez 90085f62fb [rubygems/rubygems] Simulate Bundler 4 in a better way ... Overriding the version constant feels too magic and creates a set of problems. For example, Bundler will lock the simulated version, and that can cause issues when the lockfile is used under an environment not simulating Bundler 4 (it will try to auto-install and auto-switch to a version that does not exist). On top of that, it can only be configured with an ENV variable which is not too flexible. This commit takes a different approach of using a setting, which is configurable through ENV or `bundle config`, and pass the simulated version to `Bundler::FeatureFlag`. The real version is still the one set by `VERSION`, but anything that `Bundler::FeatureFlag` controls will use the logic of the "simulated version". In particular, all feature flags and deprecation messages will respect the simulated version, and this is exactly the set of functionality that we want users to be able to easily try before releasing it. 8129402193		2025-06-26 08:06:48 +09:00
..
git_spec.rb	[rubygems/rubygems] Prefer FileUtils.rm_r to FileUtils.rm_rf for specs	2025-03-12 18:02:09 +09:00
lockfile_spec.rb	[rubygems/rubygems] Simulate Bundler 4 in a better way	2025-06-26 08:06:48 +09:00