Add lower bound for all direct dependencies #920
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
Updated anyio v4.7.0 -> v4.8.0 Updated pygments v2.18.0 -> v2.19.1 Updated ruamel-yaml v0.18.8 -> v0.18.10 Updated setuptools v75.6.0 -> v75.7.0 Updated trove-classifiers v2024.10.21.16 -> v2025.1.6.15
tp832944
approved these changes
Jan 10, 2025
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.
PR Type
Description
Add lower bounds for all direct dependencies. These are largely just "whatever the most recent major version was", or most recent minor version for 0ver dependencies. Closes #807.
How Has This Been Tested?
Existing tests pass as expected. This doesn't change which dependencies are installed when solving for the latest dependencies, but should prevent solvers from erroneously backtracking to early versions of our dependencies.
We don't actually test with our stated lower bounds - that's left for #918.
Does this PR introduce a breaking change?
No.
Checklist before requesting a review