summaryrefslogtreecommitdiff
path: root/.github
diff options
context:
space:
mode:
authorDavid Rodríguez <deivid.rodriguez@riseup.net>2025-08-01 15:19:39 +0200
committerHiroshi SHIBATA <hsbt@ruby-lang.org>2025-08-18 12:31:51 +0900
commitbcc287fc6f33e5680ece7dd737e46fd7894d6ed7 (patch)
treebf23625c871eb251d3743eb2f9ae00f9e6826f28 /.github
parent813603994a388ad8f22ab831d2b554671dfd23b6 (diff)
[rubygems/rubygems] Fix `bundle update foo` not upgrading foo to latest in a specific case
If upgrading `foo` needs an indirect dependency to be downgraded, Bundler would not be able to upgrade foo. This is because when calculating the latest resolvable version of foo, Bundler was still adding lower bound requirements on the locked versions of all dependencies to avoid downgrades, effectively pinning foo to a version older than the latest. To fix this, instead of creating a second "unlocked" definition to figure out the latest resolvable version, create a second unlocked resolver, and DO NOT add lower bound requirements to it. https://github.com/rubygems/rubygems/commit/00cc0ecc69
Diffstat (limited to '.github')
0 files changed, 0 insertions, 0 deletions