Repository navigation
chore(deps): qualify SQLAlchemy >=2.1.4,<2.2 - #165
Merged
DeusExTaco merged 4 commits intoOct 16, 2026
Merged
Conversation
Updates the requirements on [sqlalchemy](https://github.com/sqlalchemy/sqlalchemy) to permit the latest version. - [Release notes](https://github.com/sqlalchemy/sqlalchemy/releases) - [Changelog](https://github.com/sqlalchemy/sqlalchemy/blob/main/CHANGES.rst) - [Commits](https://github.com/sqlalchemy/sqlalchemy/commits) --- updated-dependencies: - dependency-name: sqlalchemy dependency-version: 2.1.1 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
Contributor
Author
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
added 2 commits
October 16, 2026 02:47
…ot/pip/develop/sqlalchemy-gte-2.0-and-lt-2.2
Require SQLAlchemy >=2.1.4,<2.2 and adapt typing without changing runtime query or transaction contracts. Classify SQLite URLs structurally so memory sessions and legacy sidecar paths survive escaped database rendering. Add real autoflush/admission, lock-order, session-isolation and URL regression tests while preserving existing commit, rollback and no-autoflush boundaries.
Use real SQLAlchemy URLs with explicit URL-bearing carriers for the three PostgreSQL backend-negative rows, without constructing engines that import optional asyncpg. Preserve every assertion, parameterized case, real SQLite engine, session-isolation check and production transaction/autoflush contract. Full local CI also passed in a separately isolated environment without asyncpg.
DeusExTaco
deleted the
dependabot/pip/develop/sqlalchemy-gte-2.0-and-lt-2.2
branch
October 16, 2026 20:23
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.
Summary
I qualified SQLAlchemy 2.1 and narrowed this update to
sqlalchemy[asyncio]>=2.1.4,<2.2, rather than claiming one application typing/runtime contract across both 2.0 and 2.1.:memory:detection and encoded filesystem paths.Existing commits, rollbacks, savepoints, flush/no-autoflush scopes, migrations, test cases, worker counts, coverage gates and security policy are preserved. The live instance and recovery worktree were not changed.
Validation
The final test-only follow-up keeps three PostgreSQL URL negative cases independent of optional
asyncpg; real SQLAlchemy URLs, all original assertions/cases, and every real SQLite engine/isolation check remain. I reproduced the driver-import dependency, confirmed the backend-negative assertions still fail for deliberately broken classification, and ran all 58 owning cases plus the full local pipeline in a separate environment withoutasyncpg. The driver remained absent after validation. Production transaction/autoflush behavior is unchanged.make ci-full: exit 0, including Docker.The local Docker build used native ARM64 with cached native/OS layers and a rebuilt application environment containing SQLAlchemy 2.1.4; it is not fresh AMD64 or multi-architecture qualification. Existing lower-severity Grype findings and npm/Bandit advisories remain. Coverage remains above the gate, but individual line coverage is not claimed identical.
Remote exact-head required checks remain the final merge gate. The Dependabot branch's public Docker sanity workflow is distinct from the locally validated production image/runtime security checks.