Skip to content

Commit b2e6265

Browse files
Change versioning-strategy to increase
I misunderstood how increase-if-necessary works. How it works: 1. Will only update the package.json if the range doesnt match 2. If the range matches, it will update the package-lock.yml file I chose increase-if-necessary because I thought it would reduce PR's. It doesn't. We get the same number of PR's, just some of them don't touc hthe package.json file. On top of that, increase-if-necessary seems problematic since it may change the package-lock.yml file, but not the actual package.json file. This means our local version of a package could drift from the released version of a package, even with the same version number. That seems like it would be hard to debug.
1 parent 471c901 commit b2e6265

File tree

1 file changed

+0
-3
lines changed

1 file changed

+0
-3
lines changed

.github/dependabot.yml

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -13,9 +13,6 @@ updates:
1313
interval: 'weekly'
1414
# Dependabot defaults to 5 open pull requests at a time
1515
open-pull-requests-limit: 100
16-
# ignore versions already covered by a range
17-
# e.g: ^1.2.3 -> 1.2.4, would be ignored
18-
versioning-strategy: increase-if-necessary
1916

2017
# Cooldown is the number of days after a release to wait until opening a PR
2118
# This gives us more confidence changes can be merged because changes have been community tested.

0 commit comments

Comments
 (0)