You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The reason will be displayed to describe this comment to others. Learn more.
@jonahoffline some we needed to yank, they were completely bogus, we don't want people trying to deploy them. But 2.0.10, I shouldn't have yanked. I'm sorry for that, we will be extremely more careful with it in the future.
b255bc3
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.
@mariokostelac OMG 😱 I'm a completely 🐴
I've wrongly yanked the version 2.0.10, and RubyGems does not let us to add it back:
I hope no one locked it in the Gemfile.
My completely bad.
b255bc3
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.
I am pretty sure people are locking gem versions :S.
b255bc3
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.
http://blog.rubygems.org/2015/04/13/permadelete-on-yank.html#a-final-note
you could post on http://help.rubygems.org/
b255bc3
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.
I got into that same article before pushing a new version 🐼
b255bc3
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.
Not only
2.0.10
, but all the gems down to version2.0.5
:(from Rubygems)
b255bc3
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.
@jonahoffline some we needed to yank, they were completely bogus, we don't want people trying to deploy them. But 2.0.10, I shouldn't have yanked. I'm sorry for that, we will be extremely more careful with it in the future.
b255bc3
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.
@phstc 👍 just thought you guys hadn't noticed. Awesome gem btw! 😄
b255bc3
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.
@jonahoffline thanks for checking it 🍻 ❤️