Repository navigation
fix(deps): drop the upper bound on sqlalchemy - #2356
Merged
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #2356 +/- ##
==========================================
- Coverage 94.13% 94.12% -0.01%
==========================================
Files 184 184
Lines 13647 13647
==========================================
- Hits 12846 12845 -1
- Misses 801 802 +1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
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.
Removes the
<3.0.0cap onsqlalchemyfrom thesql_postgres,sql_sqliteandsql_mysqlextras. There is no known incompatibility behind it, and downstream users can't override a cap in published metadata, so it can only cause resolver conflicts. If a future SQLAlchemy release breaks us, CI will show it and we can exclude that version.The
stagehand<4cap stays, since it guards a known breaking API change.Background: https://iscinumpy.dev/post/bound-version-constraints/
✍️ Drafted by Claude Code