Skip to content

--resolution-strategy lowest with only lower bound specified #648

@tpgillam

Description

@tpgillam

If only a lower bound is specified along with "lowest" resolution strategy, the latest version is picked:

See:

The new test fails:

The problem is that the optimisation to pick the latest version if only a minimum bound is specified (from #598 ) is always applied, regardless of resolution strategy.

A separate issue, but a nice optimisation, would be to have a similar fast-path attempted for the lowest resolution strategy. Namely, if there is only a >= lower bound & resolution strategy is lowest, then:

  • if the bound itself exists, use that
  • otherwise resort to the slower checking of all available versions

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions