Skip to content

bump sql-versioning: SQLAlchemy 1.4 → 2.x, Python 3.8 → 3.9#4306

Merged
kialj876 merged 1 commit intobcgov:mainfrom
panish16:bump-sql-versioning-sqlalchemy2
Apr 28, 2026
Merged

bump sql-versioning: SQLAlchemy 1.4 → 2.x, Python 3.8 → 3.9#4306
kialj876 merged 1 commit intobcgov:mainfrom
panish16:bump-sql-versioning-sqlalchemy2

Conversation

@panish16
Copy link
Copy Markdown
Contributor

Summary

  • Bumps SQLAlchemy from the EOL 1.4.44 pin to ^2.0.0 (resolves to 2.0.49)
  • Raises Python floor from ^3.8 to ^3.9 (3.8 is EOL)
  • Bumps package version 0.1.0 → 0.2.0 to signal the breaking dependency change
  • Regenerates poetry.lock with Poetry 2.3.2

Follow-up required

A second PR will be needed to update legal-api (the only direct consumer of python/common/sql-versioning) to SQLAlchemy 2.x — updating its pyproject.toml and regenerating its poetry.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

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>
@sonarqubecloud
Copy link
Copy Markdown

@kialj876 kialj876 merged commit cbe2ad9 into bcgov:main Apr 28, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants