or Create a profile
25 Feb, 2012 07:14 PM
Let's say that you have already released few version of a gem
that have >= requirement on another gem (or you have forgotten
to mention the requirement in gemspec at all). It turns out that
your gem will never work with version X.Y or greater of that
another gem. The problem is that if I release a new version of my
gem and specify that it requires "another" to by < X.Y then
bundler will find my previously released version of gem to be
compatible with "another" X.Y. Is there anything I can do in such
situation ? Yank all previous versions and release them again with
new requirements ? I know I should have used "~>" in the first
place and that is my lesson. But what can I do now ?
2 Posted by Nick Quaranto on 04 Aug, 2012 06:35 PM
Sorry, this comment was buried in our spam inbox.
Yanking is probably the safest bet here.
Nick Quaranto closed this discussion
on 04 Aug, 2012 06:35 PM.
Comments are currently closed for this discussion.
You can start a new one.
2 people watching.
No more actions from RubyGems.org or the discussion starter are required.
This discussion is private.
Only you and RubyGems.org support staff can see and reply to it.
This discussion is public. Everyone can see and reply to it.
Powered by Tender™.