Revert range strategy to "replace" #83
Merged
Conversation
This file contains 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
Per renovatebot/renovate#19800, the "auto" strategy now raises additional PRs to update dependencies in range. This is either unsuitable for our use case or bugged, as we have "lockfile update" PRs (as denoted by a `-lockfile` branch suffix) which are bumping the in-range version of a package's production dependencies. This means that e.g. `^2.0.0` gets bumped to `^2.1.0` and so on, and results in a lot of transitive noise for projects that consume the package. This _may_ break the previous behaviour of widening peer dependency ranges, but's a lesser concern now and I'm following up on the Renovate recommendation for handling this use case. https://docs.renovatebot.com/release-notes-for-major-versions/#version-35 renovatebot/renovate#20990
72636c
added a commit
to seek-oss/skuba
that referenced
this pull request
Mar 19, 2023
72636c
added a commit
to seek-oss/skuba
that referenced
this pull request
Mar 19, 2023
tbolg
approved these changes
Mar 19, 2023
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.
Per renovatebot/renovate#19800, the "auto" strategy now raises additional PRs to update dependencies in range. This is either unsuitable for our use case or bugged, as we have "lockfile update" PRs (as denoted by a
-lockfilebranch suffix) which are bumping the in-range version of a package's production dependencies. This means that e.g.^2.0.0gets bumped to^2.1.0and so on, and results in a lot of transitive noise for projects that consume the package.I've also patched in widening of peer dependency ranges which is what "auto" was previously described as doing.
https://docs.renovatebot.com/configuration-options/#rangestrategy
https://docs.renovatebot.com/release-notes-for-major-versions/#version-35
renovatebot/renovate#20990