Change default to Bundler v2 when unsupported feature flag is on and Gemfile.lock exists #10617
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What are you trying to accomplish?
This PR updates the default behavior to use Bundler v2 when the
bundler_v1_unsupported_error
feature flag is enabled and a Gemfile.lock exists. If the Gemfile.lock does not specify the Bundler version, we will now default to Bundler v2 instead of v1 when the flag is active.Anything you want to highlight for special attention from reviewers?
This change affects how dependencies are handled when there is no explicit Bundler version in the Gemfile.lock. With the feature flag enabled, the failover will be Bundler v2. This ensures compatibility with newer versions and prevents issues with unsupported Bundler v1.
How will you know you've accomplished your goal?
bundler_v1_unsupported_error
flag is enabled and the Gemfile.lock exists but lacks version information.Checklist