Repository navigation
Set __version__ to 0.3.0 - #27
Merged
Merged
Conversation
seerdb#26 bumped pyproject.toml to 0.3.0 but left sqlalchemy_seerdb.__version__ at 0.2.2, so the release workflow's test_version failed on the 0.3.0 tag and nothing was published. The two places now agree again. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Signed-off-by: Peter Lemenkov <lemenkov@gmail.com>
This was referenced Oct 13, 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
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.
#26 bumped
pyproject.tomlto 0.3.0 but leftsqlalchemy_seerdb.__version__at0.2.2. The dialect's AGENTS.md says to bump both. The release workflow's offline tests caught the mismatch on the0.3.0tag:The job stopped before building, so nothing was published: no GitHub release and no PyPI upload.
This PR sets
__version__ = '0.3.0'. Locally:test.test_versionand the whole unit suite pass, and ruff, ruff format and reuse are clean.After merging, the existing
0.3.0tag points at the commit without this fix. A re-run of that release keeps failing, so the tag needs to move to the new merge commit:Why PR CI missed it: the Tests workflow's Package job only runs the entry-point smoke check. The unit tests,
test_versionincluded, run only in the release workflow, although AGENTS.md says "the packaging job runs it". That gap is worth its own change.🤖 Generated with Claude Code