Published version (2.7.6) does not match the repo

[Pavel Gabriel]

Hey!

Guys, I have noticed that Mechanize 2.7.6 published on rubygems is missing (at least) this:

Mechanize#set_proxy accepts an HTTP URL/URI. (#513)

but https://github.com/sparklemotion/mechanize/blob/master/CHANGELOG.rdoc#276 clearly says it's in 2.7.6 version.

P.S. I checked it locally and checked gem file from rubygems.

[Lee Jarvis]

Thanks for reporting, what makes you think this change is not present in 2.7.6?

The change was merged in f176027 and it seems OK to me:

>> Mechanize::VERSION
=> "2.7.6"
>> Mechanize.new.set_proxy URI("https://google.com"), 80
=> #<URI::HTTPS https://google.com:80>

[Pavel Gabriel]

As far as I remember if you download the gem this change is not included in the code.

On Mon, 11 Feb 2019 at 17:02, Lee Jarvis ***@***.***> wrote: Thanks for reporting, what makes you think this change is not present in 2.7.6? The change was merged in f176027 <f176027> and it seems OK to me: >> Mechanize::VERSION => "2.7.6" >> Mechanize.new.set_proxy URI("https://google.com"), 80 => #<URI::HTTPS https://google.com:80> — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#531 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AABLIYvoSnWX8cD0AiKWsf7LWfslPkVWks5vMZQAgaJpZM4X3oF-> .

--

…

--- Best wishes, Pavel Gabriel Twitter: @alovak <http://twitter.com/#%21/alovak> Skype: pavel.gabriel Mobile: [phone]

[Lee Jarvis]

My example above was from downloading the gem, so I'm wondering if there's a specific issue you're having that I can investigate? Can you give me some steps to reproduce the problem? Thanks!

[Pavel Gabriel]

@leejarvis unfortunately I don't remember what was the issue. I wish I would add more details on it...

Let's close the issue until I find what was the reason behind it

[Pavel Gabriel]

Thanks for response!