Prioritise gems with higher version for fetching metadata, and stop fetching once we find a valid candidate #4843
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.
What was the end-user or developer problem that led to this PR?
Github has an issue in which it will generate a misleading prerelease output in its RubyGems server API and returns a 0 version for the gem while it doesn't exist.
What is your fix for the problem, implemented in this PR?
Verifying metadata (which needs a network request to fetch the full gemspec) in order of priority until a valid gem is found, instead of fetching all gemspec candidates unconditionally, avoids the issue.
Fixes #4603.
Make sure the following tasks are checked