Skip to content

docs: the documents describe smart-data-engine-sdk 0.1.1; main moves to 0.1.2.dev0 - #102

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

krzysztof-smartdataengines merged 1 commit into
mainfrom
docs/after-python-0.1.1

Conversation

@krzysztof-smartdataengines

Copy link
Copy Markdown
Contributor

Summary

smart-data-engine-sdk 0.1.1 is on PyPI, and npm keeps 0.1.0. The documents that describe
registry state now say so. Python's development version moves to 0.1.2.dev0. TypeScript was not
released and stays on 0.1.1-dev.0.

What changed

  • Install commands in docs/weather-starter.md pin 0.1.1 from PyPI and 0.1.0 from npm.
    The artifact names are the ones a later commit builds. README.md and
    examples/weather/README.md name the current releases.
  • docs/implementations.md: pip install installs 0.1.1, and npm install installs 0.1.0.
  • CHANGELOG.md: the publication date. python-v0.1.1 published on its first run, with
    attestations.
  • docs/publishing.md:
    • §5.1 says a release of one language moves only that language on.
    • §5.5 gets step 8, the first patch release, with a correction to the rule written for 0.1.0.

The correction

The rule for 0.1.0 said to pin the version when verifying right after a publish. For 0.1.1, a pinned
pip install 'smart-data-engine-sdk==0.1.1' --no-cache-dir started 41 s after the upload
answered "No matching distribution found". It saw only 0.1.0rc1 and 0.1.0. The simple index
listed 0.1.1 70 s after the upload, and it is served with cache-control: max-age=600.

pip resolves a pinned version from that same index, so pinning is not the fix. Right after a
publish, the files are verified against the gate's artefacts through the JSON API. Installs,
pinned or not, wait until the simple index lists the version.

Verified from PyPI before this PR

  • The wheel and the sdist are the artefacts the gate checked, each with a PEP 740 attestation from
    release.yml and the pypi environment.
  • The pinned install from the index carries the fix.
  • The suite of 99c1ed7 against the installed package, with both engines, on CPython 3.14.7:
    2098 passed, 10 skipped, 5 failed. The five are the ones 0.1.0 failed, each computing a repository
    path from sde.__file__. fix(operator): index recovery waits for the interrupted PostgreSQL statement #100's two recovery tests passed against the installed package.
  • The Weather model version is 794ff972d69c52e5 from PyPI 0.1.1 (pinned and unpinned) and from
    npm 0.1.0 on Node 18 and 26.

Tests

make check with both live engines on f86353e (this head):

  • ruff and mypy are clean;
  • Python: 2103 passed and 10 skipped (the orderbook slice);
  • TypeScript: 999 of 999.

🤖 Generated with Claude Code

…to 0.1.2.dev0

0.1.1 is on PyPI, published on the first run of python-v0.1.1 with
attestations; npm keeps 0.1.0. The install commands pin 0.1.1 and 0.1.0, the
pages name the current releases, and Python's development version moves to
0.1.2.dev0 while TypeScript, not released, stays on 0.1.1-dev.0.

publishing.md corrects a rule written the day before. A pinned install
waits for PyPI's simple index as well: 40 s after the upload,
`pip install smart-data-engine-sdk==0.1.1 --no-cache-dir` answered "No
matching distribution found", and the index listed 0.1.1 70 s after the upload.
Right after a publish the files are verified through the JSON API; installs,
pinned or not, wait for the simple index.

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