Fix bundler/inline failing in Ruby 3.2 due to conflicting securerandom versions
#7984
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 was the end-user or developer problem that led to this PR?
In Ruby 3.2, when using
bundler/inline, BundlerFetcherwill internally activate the default version ofsecurerandom(0.2.2). If the inline gemfile is using a different version ofsecurerandom, and activation conflict will be raised.See #7930.
What is your fix for the problem, implemented in this PR?
In the future we believe the ideal solution is to have
bundler/inlinereexec the original process once the install is done. However, re-exec'ing with original Ruby arguments is tricky, so for now we're vendoringsecurerandomin Bundler to skip this particular problem.Make sure the following tasks are checked