chore: upgrade dependencies, pin sqlalchemy below 2.1 - #69
Merged
Merged
Conversation
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
1 participant
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.
Upgrades all locked dependencies (
uv lock --upgrade) and adapts to the breaking changes. Mirrors modern-python/litestar-sqlalchemy-template#43.modern-di-fastapiconstraint raised from>=2,<3to>=3,<4(modern-di 2 -> 3):cache_settings=is renamed tocache=.psycopg2->psycopg, and Alembic now names the driver explicitly (postgresql+psycopg), so migrations don't depend on SQLAlchemy's default Postgres driver, which changes in 2.1.CPY001(copyright header).Why sqlalchemy is pinned below 2.1
On SQLAlchemy 2.1 (checked on 2.1.0 and 2.1.1) the asyncpg adapter no longer includes the
DETAIL: Key (...)=(...) already exists.line inexc.orig.args. advanced-alchemy 1.11.0 (latest) detects duplicate keys with regexes that need that line, so a unique violation surfaces as a genericIntegrityErrorinstead ofDuplicateKeyErrorand the API returns 500 instead of 400.tests/test_cards.py::test_create_cardscatches this.Upstream: litestar-org/advanced-alchemy#803. Remove the pin once a fixed release is out.