search

nixme / pry-nav

Binding navigation commands for Pry to make a simple debugger
MIT License
390 stars 35 forks source link

update dependency for most recent pry release #13

Closed banister closed 12 years ago

banister commented 12 years ago

pry 0.9.9 has been released, time to update dependency ;)

jimmycuadra commented 12 years ago

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.

banister commented 12 years ago

@jimmycuadra The next version we expect to be 1.0 and i can't guarantee backwards compat from 1.0 to 0.9.9

dsisnero commented 12 years ago

Can we get this applied and have a new version put out?

ConradIrwin commented 12 years ago

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

fowlmouth commented 12 years ago

+1

banister commented 12 years ago

@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 :)

nixme commented 12 years ago

@banister. Added you as a collaborator. I'll do a release right now.

nixme commented 12 years ago

Released 0.2.1.

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?