Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider avoiding version bumps for "^x.x.x" versions #22

Closed
alexjeffburke opened this issue Oct 1, 2018 · 3 comments
Closed

Consider avoiding version bumps for "^x.x.x" versions #22

alexjeffburke opened this issue Oct 1, 2018 · 3 comments

Comments

@alexjeffburke
Copy link

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.

@theflow
Copy link
Member

theflow commented Oct 8, 2018

Thanks for the feedback @alexjeffburke!

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?

@AlexWayfer
Copy link

What's the reason you'd like to not have it, any downsides you have seen?

Too many pull requests: https://github.com/AlexWayfer/stream_timer/pulls?q=is%3Apr+label%3Adepfu

@theflow
Copy link
Member

theflow commented Jul 20, 2022

Closing older issues

@theflow theflow closed this as completed Jul 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants