-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Resolve latest version via gem contents
#3149
Conversation
Thanks for opening a pull request and helping make RubyGems better! Someone from the RubyGems team will take a look at your pull request shortly and leave any feedback. Please make sure that your pull request has tests for any changes or added functionality. We use Github Actions to test and make sure your change works functionally and uses acceptable conventions, you can review the current progress of Github Actions in the PR status window below. If you have any questions or concerns that you wish to ask, feel free to leave a comment in this PR or join our #rubygems channel on Slack. For more information about contributing to the RubyGems project feel free to review our CONTRIBUTING guide |
c2f5437
to
e8747f0
Compare
gem contents
gem contents
e8747f0
to
ffbc424
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great, thanks for fixing this! 💜
@bundlerbot merge |
Build succeeded
|
Thanks, all, for the review! |
Description:
Issue
Scenario: I have two versions of gem
foo
installed.Current behavior:
gem contents foo
returns information about the older version.Expected behavior:
gem contents foo
returns information about the newer version.Tasks:
I will abide by the code of conduct.