bump sql-versioning: SQLAlchemy 1.4 → 2.x, Python 3.8 → 3.9#4306
Merged
kialj876 merged 1 commit intobcgov:mainfrom Apr 28, 2026
Merged
bump sql-versioning: SQLAlchemy 1.4 → 2.x, Python 3.8 → 3.9#4306kialj876 merged 1 commit intobcgov:mainfrom
kialj876 merged 1 commit intobcgov:mainfrom
Conversation
SQLAlchemy 1.4 is EOL. Bump to ^2.0.0 and update the lock file. Raise python floor from ^3.8 to ^3.9 as 3.8 is also EOL. Version bumped 0.1.0 → 0.2.0 to signal the breaking dependency change so consumer services can update their toml and lock files in a follow-up PR. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
kialj876
approved these changes
Apr 27, 2026
meawong
approved these changes
Apr 27, 2026
argush3
approved these changes
Apr 27, 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
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
1.4.44pin to^2.0.0(resolves to 2.0.49)^3.8to^3.9(3.8 is EOL)0.1.0 → 0.2.0to signal the breaking dependency changepoetry.lockwith Poetry 2.3.2Follow-up required
A second PR will be needed to update
legal-api(the only direct consumer ofpython/common/sql-versioning) to SQLAlchemy 2.x — updating itspyproject.tomland regenerating itspoetry.lock.Context
Separated from #4266 per reviewer guidance (kialj876): shared-library major-version bumps should land as their own PR with an updated lock file and version increment before consumers are updated.
🤖 Generated with Claude Code