Skip to content

Bump version to 2.22.0 (osi-orionbelt 0.1.1)#218

Merged
ralfbecher merged 2 commits into
mainfrom
release/v2.22.0
Jul 15, 2026
Merged

Bump version to 2.22.0 (osi-orionbelt 0.1.1)#218
ralfbecher merged 2 commits into
mainfrom
release/v2.22.0

Conversation

@ralfbecher

Copy link
Copy Markdown
Collaborator

Release 2.22.0. Ships 20 commits sitting unreleased since v2.21.1 (mostly Dependabot), of which three are substantive.

Why minor, not patch

sqlglot's floor moved >=26,<27 -> >=30,<31, so anyone pinning sqlglot 26 cannot install this release. A patch should not break dependency resolution. Python 3.14 is also newly supported, which reads as Added.

osi-orionbelt 0.1.0 -> 0.1.1

Bumped in the same tag, deliberately. pypi-publish.yml sets skip-existing: true on the osi-orionbelt job so an unchanged version passes without failing the run. Leaving it at 0.1.0 would have skipped that job silently, gone green, and shipped the converter fixes (#201, #202) to nobody. The constants dropped in #200 were private and unused, so there is no public API break: 0.1.1, not 0.2.0.

Contents

PR Change
#216 Python 3.14 across all three Docker images + CI matrix. Needed snowflake-connector-python 4.3.0 -> 4.6.0 and pyarrow 19.0.1 -> 25.0.0, since the locked versions had no cp314 wheels and the slim image failed building them from source.
#217 sqlglot 30 adaptation (Select arg renames, exp.Expr base class) in the OBSQL translator and pgwire subquery flattening. pyarrow cap -> <26, structlog -> <27.
#200, #201, #202 osi-orionbelt converter roundtrip fidelity and validation robustness.

The Docker images are the sharpest reason to cut this tag: docker-publish.yml is tag-triggered, so the Python 3.14 images do not exist on Docker Hub until this merges and is tagged.

Version refs

pyproject.toml, src/orionbelt/__init__.py, README.md (4 refs), mkdocs.yml, integrations/chatgpt-custom-gpt/openapi-gpt-action.yaml, uv.lock (both version lines, no other churn), CHANGELOG.md, CHANGELOG-versions.md, packages/osi-orionbelt/pyproject.toml. Verified by grep; no 2.21.1 remains.

Verification

2621 passed, 167 skipped. ruff format, ruff check, and mypy clean.

After merge

./scripts/release.sh --post-merge cuts the tag, which triggers the PyPI, Docker Hub, and docs workflows. Then confirm Docker Hub has ralforion/orionbelt-{api,ui,flight}:2.22.0 on 3.14, and that PyPI actually has osi-orionbelt==0.1.1 rather than a skipped job.

Minor rather than patch: sqlglot's floor moved 26 -> 30, so installs pinning
sqlglot 26 cannot take this release, and Python 3.14 is newly supported.

Bumps osi-orionbelt 0.1.0 -> 0.1.1 in the same tag. The PyPI publish workflow
sets skip-existing on that job, so leaving it at 0.1.0 would have skipped the
job silently and shipped the converter fixes (#201, #202) nowhere while the
release still went green.

Release contents (20 commits since v2.21.1, mostly Dependabot):
- Python 3.14 across all three Docker images + CI matrix (#216)
- sqlglot 30 adaptation; pyarrow <26, structlog <27 (#217)
- osi-orionbelt converter roundtrip fidelity + validation robustness (#200,
  #201, #202)

2621 passed, 167 skipped. ruff and mypy clean.
osi-orionbelt was bumped to 0.1.1 in pyproject.toml and uv.lock, but the module
still exported __version__ = "0.1.0", so the published wheel would have
self-reported 0.1.0 while its metadata said 0.1.1.

Root cause: the version-ref sweep grepped for the main package's version
(2.21.1) only, and osi-orionbelt is versioned independently, so its constant was
never in the search.

Adds tests/unit/test_version_consistency.py, which asserts every package's
exported __version__ matches its pyproject version. Verified it fails on the
reintroduced bug, not just passes on the fix. There was no existing release
consistency check to extend.

2623 passed, 167 skipped. ruff and mypy clean.
@ralfbecher
ralfbecher merged commit 3591137 into main Jul 15, 2026
7 checks passed
@ralfbecher
ralfbecher deleted the release/v2.22.0 branch July 15, 2026 22:09
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.

1 participant