Closed andystanton closed 8 years ago
It looks like if your specs pass with the new version of a dependency and it is covered by your current range it doesn't send in a PR... but it leaves the branch around.
Yes, I was confused by this behaviour - I was expecting a PR.
I'm not familiar with npm or apm best practices but given the dependencies are installed per package, I think it might be a better idea to use concrete versions rather than caret ranges.
caret ranges aren't working properly in Atom on Windows anyway: https://github.com/atom/atom/issues/9775
You can certainly move to concrete versions, just a warning though Greenkeeper will send a PR for every update then, since every update would be outside your allowed range.
http://greenkeeper.io/