Selective update resolves the graph for selected package #957
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR fixes the behavior of selective update (update specifying a package).
The current behavior is to pin the version for all packages, except the one specified, and resolve the whole graph.
This would cause the dependencies of the specified package to be pinned and the package would not be updated if it requires that one or more dependencies need to be updated as well.
For example:
Castle.Core-log4net 3.2.0
depends onCastle.Core >= 3.2.0
Castle.Core-log4net 3.3.3
depends onCastle.Core >= 3.3.3
If I try to update
Castle.Core-log4net
from3.2.0
to3.3.3
, it would not succeed becauseCastle.Core
is pinned to3.2.0
.This PR only resolve the specified package graph.