Pip dependency versioning: Use "compatible-version" specification #1917
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
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.
This is defined as "at least this patch version, but feel free to use any higher patch (=compatible) version". This should reduce dependabot spam, since we're basically always up-to-date on patch-versions, while it still allows to specify a minimum patch version if there is a bug we need to have fixed.
I've left the "smaller" dependencies in
requirements.txtpinned because I think it's more likely that they have a faulty release, so full version pinning might be beneficial there. These core dependencies usually don't have that many patch updates, so this should be fine.