Invalid dependencies in previously released version

Robert Pankowecki's Avatar

Robert Pankowecki

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 ?

  1. Support Staff 2 Posted by Nick Quaranto on 04 Aug, 2012 06:35 PM

    Nick Quaranto's Avatar

    Sorry, this comment was buried in our spam inbox.

    Yanking is probably the safest bet here.

  2. 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.

Keyboard shortcuts

Generic

? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac

Recent Discussions

29 Aug, 2014 06:23 PM
28 Aug, 2014 07:18 PM
27 Aug, 2014 12:03 PM
26 Aug, 2014 07:09 PM
26 Aug, 2014 07:07 PM