Repository navigation
chore(deps): update dependencies and test SQLAlchemy 2.1 - #1
Merged
Merged
Conversation
Welcome to Codecov 🎉Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests. Thanks for integrating Codecov - We've got you covered ☂️ |
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.
What changed
^0.15.22→^0.17.3.poetry.lockwith Poetry 2.0.0 so every dependency resolves to the newest release its range allows on the supported Python floor.sqlalchemy20everywhere,sqlalchemy21on 3.11+), installed afterpoetry installthe same way vintasend-django pins Django. SQLAlchemy 2.1 needs Python 3.11, so the lock can only ever pick 2.0.x and 2.1 — which^2.0.51already allows — was never exercised.py310-sqlalchemy20,py311-sqlalchemy21andpy313-sqlalchemy21: all 76 tests pass, including on SQLAlchemy 2.1.6.Breaking: no. Only dev dependencies and the lock file change; the published package's requirements are the same.
Verification
ruff check,ruff format --check,mypyandpytestpass locally against the new lock.🤖 Generated with Claude Code