Antônio Paulino

Thanks.

Hey @ngan I looked in files and found `deprecate.rb` under `lib/rubygems` that has a method `rubygems_deprecate` which `Indicate something will be removed in the next major RubyGems version, and (optionally)...

Hey @deivid-rodriguez can I try to fix it? I'm happy to contribute.

Hey @deivid-rodriguez is there any way to debug tests? I looked on the contribution page but didn't find any information related to this. I still haven't been able to identify...

Sorry for that. I used `puts` to see if the version and it seems that there are nothing wrong with the `version_option.rb`. So far, I'm trying to reproduce this bug...

Yes, I tried something like that. ```rb def test_execute_remote_version spec_fetcher do |fetcher| #fetcher.spec "coolgem", "4.1.3" fetcher.spec "coolgem", "4.1.2" fetcher.spec "coolgem", "4.1.1" end @cmd.handle_options %w[info coolgem --remote --version 4.1.3] use_ui @stub_ui...

No...it expect version `4.1.2`

Hey @deivid-rodriguez I used `puts` to see the @options that are being used in the `handle_options` method and I've noticed this: ```console {:domain=>:remote, :details=>false, :versions=>true, :installed=>nil, :version=>#, :explicit_prerelease=>false, :prerelease=>false, :args=>["info",...

> By the way, be careful to add quotes when you write instance variables like `@options`, otherwise you're mentioning random people at GitHub laughing. OMG I miss that.

> That means that the CLI flag with the version is being correctly passed to the command. So the fact that it's being ignored lives in the command logic. >...