Fix error if no matching packages found #587
Merged
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.
In the scenario where a project is using prerelease packages but specifies
--pre-release:Never
and there are no stable packages available, dotnet outdated would return an error and list blank versions to upgrade to.Instead, if no packages are found for upgrade, report the package itself as the latest version.
For example, running dotnet-outdated against martincostello/website@99fad95 (which is currently using .NET 9 RC1 and no stable version of .NET 9 is yet available) gives the following output:
With the change, the output is the following: