chore(release): smart-data-engine-sdk 0.1.1, the index recovery fix - #101
Merged
Merged
Conversation
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>
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
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.
Summary
This sets
smart-data-engine-sdk0.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.1and approving the PyPI deployment.What 0.1.1 contains
interrupted statement before reading the catalogue. Before, they raced its commit ("tuple
concurrently updated") or dropped the index it was finishing.
python-v0.1.0,git diffoverpython/src,python/pyproject.tomlandpython/README.mdshows the fix in_index_build.pyand theversion, 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, theREADME, 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 keeps0.1.0, andtypescript/package.jsonstays on0.1.1-dev.0.What changed here
python/src/sde/__init__.py:0.1.1.CHANGELOG.md: the Unreleased section becomes the0.1.1section.The documents that describe registry state change after the publish, as §5.5 step 6 says.
mainthen moves to
0.1.2.dev0.What the tag will do
tools/release_tag.pyacceptsrefs/tags/python-v0.1.1on this tree. The release workflow buildsthe wheel and sdist, the gate checks them, and after the deployment is approved it publishes them to
PyPI through trusted publishing.
Tests
make checkwith both live engines on4731381(this head):tools/release_tag.pyon this tree resolvesrefs/tags/python-v0.1.1to('python', '0.1.1').As a control, it refuses
typescript-v0.1.1, because the manifest says0.1.1-dev.0.🤖 Generated with Claude Code