Pin SQLAlchemy third-party tests to pytest==9.0.3#765
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. @@ Coverage Diff @@
## main #765 +/- ##
=======================================
Coverage 97.19% 97.19%
=======================================
Files 3 3
Lines 7815 7815
=======================================
Hits 7596 7596
Misses 219 219
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
Contributor
Author
|
Thanks for the heads up. It will likely be fixed by SQLAlchemy soon |
srittau
approved these changes
Jun 14, 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
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.
Fixes #764
For whatever reason, the SQLAlchemy tests fail when using the newly released pytest v9.1.0. Pinning pytest to v9.0.3 seems to fix things.
It looks like SQLAlchemy's CI is still using v9.0.3 (example from recent run), so this hasn't affected them yet. I'm guessing they'll start seeing the same failures when their CI updates to v9.1.0.