Skip to content

chore(release): smart-data-engine-sdk 0.1.1, the index recovery fix - #101

Merged
krzysztof-smartdataengines merged 1 commit into
mainfrom
chore/release-python-0.1.1
Sep 28, 2026
Merged

krzysztof-smartdataengines merged 1 commit into
mainfrom
chore/release-python-0.1.1

Conversation

@krzysztof-smartdataengines

@krzysztof-smartdataengines krzysztof-smartdataengines commented Sep 28, 2026 •

Copy link
Copy Markdown
Contributor

Summary

This sets smart-data-engine-sdk 0.1.1, a patch release of the Python library alone, for
#100. Merging releases nothing. The owner approved the release; it happens by tagging this PR's
squash commit python-v0.1.1 and approving the PyPI deployment.

What 0.1.1 contains

  • The fix from fix(operator): index recovery waits for the interrupted PostgreSQL statement #100. Resume and abandonment of a PostgreSQL in-place index build wait for the
    interrupted statement before reading the catalogue. Before, they raced its commit ("tuple
    concurrently updated") or dropped the index it was finishing.
  • Nothing else in what the wheel ships. Since python-v0.1.0, git diff over python/src,
    python/pyproject.toml and python/README.md shows the fix in _index_build.py and the
    version, and nothing more.

Why npm gets no 0.1.1

Since typescript-v0.1.0, the only change in what the npm package ships (dist, bin, the
README, LICENSE and NOTICE) is its version field. One tag per language keeps an otherwise
identical package from going out under a new number (docs/publishing.md §5.1). npm keeps
0.1.0, and typescript/package.json stays on 0.1.1-dev.0.

What changed here

  • python/src/sde/__init__.py: 0.1.1.
  • CHANGELOG.md: the Unreleased section becomes the 0.1.1 section.

The documents that describe registry state change after the publish, as §5.5 step 6 says. main
then moves to 0.1.2.dev0.

What the tag will do

tools/release_tag.py accepts refs/tags/python-v0.1.1 on this tree. The release workflow builds
the wheel and sdist, the gate checks them, and after the deployment is approved it publishes them to
PyPI through trusted publishing.

Tests

  • make check with both live engines on 4731381 (this head):
    • ruff and mypy are clean;
    • Python: 2103 passed and 10 skipped (the orderbook slice);
    • TypeScript: 999 of 999.
  • CI: fourteen of fourteen.
  • tools/release_tag.py on this tree resolves refs/tags/python-v0.1.1 to ('python', '0.1.1').
    As a control, it refuses typescript-v0.1.1, because the manifest says 0.1.1-dev.0.

🤖 Generated with Claude Code

A patch release of the Python library alone, for #100: resume and
abandonment of a PostgreSQL in-place index build wait for the interrupted
statement before reading the catalogue, instead of racing its commit or
dropping the index it was finishing.

@smart-data-engines/sde has no 0.1.1: of what it ships, only the version
field changed since typescript-v0.1.0, so npm keeps 0.1.0 (one tag per
language, docs/publishing.md 5.1).

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@krzysztof-smartdataengines
krzysztof-smartdataengines merged commit 99c1ed7 into main Sep 28, 2026
14 checks passed
@krzysztof-smartdataengines
krzysztof-smartdataengines deleted the chore/release-python-0.1.1 branch September 28, 2026 05:13
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