Use pip-compile's backtracking dependency resolver to fix failing CI pipelines #2509
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.
The CI pipeline began failing three days ago, due some dependency changes in an upstream dependency.
It seems the pip-compile step of our tox environments became unable to resolve a full dependency graph from this point on (related to versions of pylint, it seems).
Using the backtracking resolver of pip-compile allows it to select older dependencies as long our pinned requirements are satisfied.