version ranges --update test #5336
Changelog: Fix: Improve the output to show the remote (or cache) that a version range is resolved to.
It also cached the local search result, which might make version ranges a bit faster, and fixed some weird implementation details in the caching of the remote searches.
referenced this pull request
Jun 11, 2019
From my point of view, the output when having several version ranges can get a bit confusing:
I would prefer the "resolved in..." to be added to the existing message:
I have improved the output message, but leaving the "pattern versions found in remote", because that is different to resolution, and the OP question. You can find versions in one remote that later do not satisfy the range.
@lasote, I have also removed the cache for local versions completely, as it turns out it doesn't work, as the installed packages change during the evaluation, and the logic changed, with some broken tests.