Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Make sure bundle update <specific_gems> can always update to the latest resolvable version of each requested gem #7558

Merged
merged 3 commits into from Apr 29, 2024
Merged

Make sure bundle update <specific_gems> can always update to the latest resolvable version of each requested gem #7558

merged 3 commits into from Apr 29, 2024

Commits on Apr 29, 2024

  1. No need to reset version promoter here 

    Since resolution options don't change.
    @deivid-rodriguez
    deivid-rodriguez committed Apr 29, 2024
    Configuration menu
    Copy the full SHA
    5c5aa38 View commit details
    Browse the repository at this point in the history

  2. Keep track of gems requested for update explicitly

    @deivid-rodriguez
    deivid-rodriguez committed Apr 29, 2024
    Configuration menu
    Copy the full SHA
    ea43e4c View commit details
    Browse the repository at this point in the history

  3. Make sure to force latest resolvable version explicitly 

    To make sure we can always update to the latest resolvable version for
each gem explicitly requested for update, we first run a full update,
and then add explicit exact requirements to the resolved versions. This
may lead into conflicts, but our resolver already automatically parses
those and unlocks additional gems to fix them.
    @deivid-rodriguez
    deivid-rodriguez committed Apr 29, 2024
    Configuration menu
    Copy the full SHA
    01c0bf3 View commit details
    Browse the repository at this point in the history