Properly handle missing package versions in new dependency resolver #6028
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.
Bug
Fixes: NuGet/Home#13788
Description
During restore, NuGet verifies that CPM requirements are met by verifying all packages have versions. However, when one project references another and the referenced project has a missing package, NuGet logs an error for the referenced project but restores the other. It restores this project by skipping the dependency.
This change updates the new dependency resolver to ignore packages with missing versions.
PR Checklist