You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've noticed in quite a few projects I work with that use depth that it will create version bump branches even in package.json specifies a caret range and thus the upgrade is covered. It would be great to have a way to turn off this behaviour - perhaps even make it conditional on the presence of lock files.
Thanks.
The text was updated successfully, but these errors were encountered:
We know it's not strictly necessary, but it solved a few edge cases with npm where it didn't behave the way we expected it to. What's the reason you'd like to not have it, any downsides you have seen?
Hey,
I've noticed in quite a few projects I work with that use depth that it will create version bump branches even in package.json specifies a caret range and thus the upgrade is covered. It would be great to have a way to turn off this behaviour - perhaps even make it conditional on the presence of lock files.
Thanks.
The text was updated successfully, but these errors were encountered: