summaryrefslogtreecommitdiff
path: root/spec/ruby/core/array/pack/shared/integer.rb
diff options
context:
space:
mode:
authorDavid Rodríguez <deivid.rodriguez@riseup.net>2023-03-23 20:33:44 +0100
committerHiroshi SHIBATA <hsbt@ruby-lang.org>2023-03-28 15:25:41 +0900
commited868f9a71707d5f51caddbf345e0fde8c940c42 (patch)
tree6f9d624cf89106bcf9e455e6ae463d17aff49fed /spec/ruby/core/array/pack/shared/integer.rb
parenteaddd386ecf3cf7efb0857e07dbcd66776dd4954 (diff)
[rubygems/rubygems] Fix unnecessary downgrade of top level dependency when unlocking
Bundler is very conservative by default, trying to preserve versions from the lockfile as possible, and never downgrading them. However, when it runs into a resolution error, it still tries to find a valid resolution. This fallback behavior was too "brute-force" though, completely unrestricting any gem found in the resolution conflict, and that could lead to direct dependencies being downgraded in some edge cases. Instead, unlock things a bit more carefully: * First try unlocking fully pinned indirect dependencies, but leave a lower bound requirement in place to prevent downgrades. * Then try unlocking any fully pinned dependency, also leaving a lower bound requirement in place. * Finally completely unrestrict dependencies if nothing else worked. https://github.com/rubygems/rubygems/commit/7f55ed8302
Diffstat (limited to 'spec/ruby/core/array/pack/shared/integer.rb')
0 files changed, 0 insertions, 0 deletions