-
-
Notifications
You must be signed in to change notification settings - Fork 816
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
Remove packages pinning #5132
Comments
Would you create a PR for this change? |
is the renovatebot also reconfigured not to pin back things? or it does that automatically if ranges are used? |
It respects ranges. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
your renovatebot integration pins dependencies which is also affecting downstream packages.
it's ok to pin your devDependencies, but pinning on dependencies has effect on downstream packages too, resulting duplicate instances in node_modules.
Describe the solution you'd like
Remove the version pinning and update your lock file only in your repo.
so currently:
value-or-promise "1.0.12"
future:
value-or-promise "^1.0.0"
(affects downstream packages)value-or-promise "1.0.12"
(does not affect downstream packages)Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered: