Use pinned dependencies for testing #96
Merged
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.
I was using
pip install -e .[dev,server]
to set up the Python environment in CI. This means that, ifruff
ormypy
(or indeed anything else) updates, it might cause the CI to fail. This then means fixes end up in random PRs, because otherwise the CI fails for those PRs. I am now using pinned dependencies as per usual best practice.I've duplicated the tests rather than just pinning them: tests will run once with pinned deps, and once without. Testing without pinned dependencies helps spot issues people might run into if they just
pip install
the package, as most users would do. In the future, this should probably use the exact commands in thequickstart
section.This PR also updates the upload-artifact CI step to use v4, as v3 is now no longer supported.
I've also deleted requirements.txt as it wasn't being used.