report no new version if a given package doesn't exist on any feed #10354
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
brettfo
force-pushed
the
dev/brettfo/nuget-analyze-no-package-exists
branch
from
0a257ab
to
6026b7d
Compare
JoeRobich
approved these changes
Aug 2, 2024
abdulapopoola
approved these changes
Aug 2, 2024
kbukum1
approved these changes
Aug 2, 2024
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
JamieMagee
approved these changes
Aug 2, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When analyzing the potential package upgrades, if the given package doesn't exsit on any feed, quit early and report that the current version is up-to-date.
Found during a manual scan of the logs.