Pin test tool versions - #447
Merged
Merged
Conversation
gkreitz
force-pushed
the
331_pin_test_tools
branch
from
July 31, 2026 11:25
d321cab to
0a3a5ca
Compare
pehrsoderman
approved these changes
Jul 31, 2026
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
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.
Apparently, ruff 0.16 adds a lot of new checks by default. This caused CI to fail for our latest PR.
This PR pins versions of our dev tools (and pins ruff to 0.15.22 so we can slowly start going through the fixes required for 0.16). I also did some additional QoL fixes:
./run_tests.shto easily run all tests locally. Ormake testif you prefer make.pyproject.toml- read requirements as a dynamic propertyI intentionally decided not to pin the libraries we depend on. I think it's good if CI pulls in the latest pip versions and blows up if upstream changes.
Fixes #331