chore: rename distro to archastro-sdk, reset version to 0.1.0 - #3
Merged
Conversation
Fresh-start rename — ship as archastro-sdk 0.1.0 rather than inheriting archastro-platform-sdk 0.77.0 from the firstlanding import. These changes were on feat/initial-setup but got left behind when PR #1 merged; rebasing onto main now that PR #2's flake fix is in. - pyproject.toml: name → archastro-sdk, version → 0.1.0 - scripts/sdk-generator-config.json: matches - README: pip install archastro-sdk - src/archastro/platform/__init__.py: patched to look up \"archastro-sdk\" via importlib.metadata. This file is auto-generated; the generator fix that will make this automatic is ArchAstro/archastro-openapi#4 — once that ships in @archastro/sdk-generator@0.1.1+, future regens produce the right output without patching. - uv.lock: regenerated The Python import path (`archastro`) is unchanged — only the pip-install name and the __version__ lookup key change. Local verification uv run python -c \"import archastro.platform; print(archastro.platform.__version__)\" → 0.1.0 Test suite: 51 non-contract tests + 641 contract tests (incl. channel suites over a real @archastro/channel-harness subprocess) all pass; ruff check + format clean. Co-Authored-By: Claude Opus 4.7 (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
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.
Summary
Fresh-start rename — ship as `archastro-sdk 0.1.0` rather than inheriting `archastro-platform-sdk 0.77.0` from the firstlanding import.
These changes were on `feat/initial-setup` during PR #1 but didn't make it into the merge — rebasing onto main now that PR #2's flake fix is in.
What changed
The Python import path (`archastro`) is unchanged — only the pip-install name and the `importlib.metadata` lookup key change.
Generator coupling
`init.py` is auto-generated by `@archastro/sdk-generator`, which hardcodes `_pkg_version("archastro-platform-sdk")`. The manual patch here will be clobbered on the next `./scripts/regenerate_sdk.sh` until the fix in archastro-openapi#4 ships in `@archastro/sdk-generator@0.1.1+`. That PR makes the emitter interpolate `spec.name` — after it lands and is published, regens produce the correct output unaided.
Risk
Low. Pure rename. No Python API change for consumers. Tests all still pass locally.
Testing
🤖 Generated with Claude Code