feat: optimize Dependabot config #220
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
sinopeus
approved these changes
Apr 19, 2024
lsorber
force-pushed
the
ls-optimize-dependabot
branch
from
61a7893 to
a7d6d6e
Compare
After testing, I encountered some limitations on the way Dependabot can be configured. I updated this PR to conform with those limitations and also updated the changes in the PR's description above. |
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.
Before this PR: the Dependabot configuration is suboptimal because it doesn't differentiate well between applications and packages, and because it doesn't group updates to reduce the number of PRs.
After this PR:
pyproject.toml.Every month, Dependabot will create a single PR for all transitive dependency updates (of both production & development dependencies). This PR only updates the lockfile.pyproject.toml.EDIT: Dependabot unfortunately has a number of limitations currently that prevent us from grouping transitive dependency updates and using a different versioning strategy for them. I've updated the scope of this PR's changes above.