chore(renovate): use range strategy update-lockfile for runtime and pin for dev dependencies
#54
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've updated Renovate's range strategy to
update-lockfilefor runtime andpinfor dev dependencies. Previously, Renovate was bumping the pins of dev dependencies, but it didn't update the lock file for direct runtime dependencies (except when performing lock file maintenance). I think it's preferable to update direct dependencies in the lock file to (a) discover incompatibilities as early as possible and (b) receive isolated updates for better problem resolution.