pry 0.9.9 has been released, time to update dependency ;)
update dependency for most recent pry release
Wouldn't it be better to use >= instead of ~> so there doesn't need to be a new version of pry-nav every time a new pry is released that increases the penultimate version number? As it stands, I'm now waiting on a release of this gem to update Pry in my app.
@jimmycuadra The next version we expect to be 1.0 and i can't guarantee backwards compat from 1.0 to 0.9.9
Can we get this applied and have a new version put out?
I'd vote for just changing it to >=, it seems unlikely that too much would break; and having to update the version number of a dependency every time gets pretty old.
(but whatever, we should do it ASAP, not having pry-nav is like not having a thumb on your right hand).
@nixme, As i stated in the email i sent today, im happy to take over the mundane process of releasing future pry-nav gems; feel free to add me as a gem owner/repository collaborator :)
@banister. Added you as a collaborator. I'll do a release right now.
I'd rather stay away from using >= especially with the level of money-patching going on in pry-nav. I did make a mistake with the last release tying the approx operator to the patch level instead of one up. If we stick to three digits then minor releases of pry should match up fine. Or perhaps pry can adopt strict semver past 1.0? What do you think?