Repository navigation
CI: pin SQLAlchemy to an exact version - #19
Merged
Merged
Conversation
Every workflow installed SQLAlchemy through the dependency floor (`SQLAlchemy>=2.0`), so each run took the newest release. SQLAlchemy 2.1.0 came out on 2026-09-24 and changed what the compliance suite checks, with no change here. Each workflow now sets the version once, SQLALCHEMY: "2.0.54", and passes it as an exact requirement to every install: the checkout and the PyPI modes of compliance.yml, and the unit tests. A newer SQLAlchemy becomes a deliberate change of that line. The driver repository pins the same version for its own runs of this suite (seerdb/seerdb#1199). Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Signed-off-by: Peter Lemenkov <lemenkov@gmail.com>
This was referenced Sep 24, 2026
Merged
lemenkov
added a commit
that referenced
this pull request
Sep 24, 2026
Changes since 0.2.1: - A Boolean column's 1/0 is converted to a bool by the dialect itself (#20). SQLAlchemy 2.1 stopped doing it in the generic Oracle dialect, so before 23ai a Boolean came back as 1 or 0. - CI pins SQLAlchemy to one exact version, 2.0.54 (#19). The driver floor stays seerdb>=2.5.0: nothing here depends on an unreleased driver fix. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Signed-off-by: Peter Lemenkov <lemenkov@gmail.com>
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.
Every workflow installed SQLAlchemy through the dependency floor (
SQLAlchemy>=2.0), so each run took the newest release. SQLAlchemy 2.1.0 came out on 2026-09-24 and changed what the compliance suite checks, with no change here.Change
Each workflow sets the version once,
SQLALCHEMY: "2.0.54", and passes it as an exact requirement to every install:compliance.yml, in both the checkout and the PyPI mode;tests.yml.released.ymlandreleases.ymlonly callcompliance.yml, so they are covered. It is never a range or the newest release; a newer SQLAlchemy becomes a deliberate change of that line.The driver repository pins the same version for its own runs of this suite (seerdb/seerdb#1199). Moving to 2.1 is tracked on both sides under sqlalchemy-2.1 and seerdb/seerdb#1203. This repository's part of it, a Boolean fix, follows as its own PR.
The user-facing dependency (
SQLAlchemy>=2.0) is left as it is: which SQLAlchemy a user may install is a release decision, separate from what CI checks.Tests
CI configuration only; the workflows run on this PR because it touches them.
reuse lintpasses.🤖 Generated with Claude Code