Test range of dependency versions #1674
Merged
Conversation
This file contains hidden or 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
Coverage report
This PR does not seem to contain any modification to coverable code. |
austinweisgrau
approved these changes
Jan 6, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
In #1446, I exposed the
uv pip install --resolutionflag to configuration via a matrix in the pytest job. Initially, the accepted package resolution options werehighestandlowest. Unfortunately since we have so many dependencies with very permissive dependencies, this was basically guaranteed to fail unless we expanded our dependencies list to cover a ridiculous amount of packages that really should be handled in other projects.Recently the uv team added
lowest-directwhich totally addresses this issue! By incorporating this in our workflow, we can easily determine whether the oldest dependency version we list as compatible truly doesn't result in test failures (rather than just checking the newest version we list as compatible).