Suggest alternatives in gem query
deprecation
#4021
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.
What was the end-user or developer problem that led to this PR?
gem query
was deprecated in rubygems 3.2. Prior to the command being deprecated, there was an injunction to uselist
orsearch
. While thequery
command is going away, the usefulness of this suggestion is still present, as pointed out in #3984.@deivid-rodriguez's comment on the linked issue suggested adding suggestions for the now-deprecated
query
command, along with adding information about the deprecation to rubygems.org.Note: since the described problem requires changes in two repositories, this is the first of two pull requests to address this issue.
Make sure he following tasks are checked