fix: prepare prerelease packages for PyPI#9
Merged
Volv-G merged 1 commit intoJul 3, 2026
Merged
Conversation
Assisted-By: devx/863bf6dc-7461-4f68-9fcb-a52df3c22dcf
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
tangle-cliconsole-script alias while keepingtanglecanonicaltangle-cliandtangle-apiat0.0.1a2tangle-cli[native]totangle-api==0.0.1a2andtangle-apiback totangle-cli==0.0.1a2for the short-term circular releasepackages/tangle-api/README.mdsouv build --package tangle-apisucceeds for sdist+wheel buildsChecks
git diff --check origin/masteruv run pytest(621 passed)uv run pytest tests/test_packaging.py tests/test_tangle_cli_cli.py(6 passed)uv builduv build --package tangle-apitangle version,tangle-cli version)tangle-cli[native]resolution against builtdist/artifactsRelease notes
This PR prepares publishing only. It does not publish to PyPI. A later release tag such as
v0.0.1a2will trigger the workflow.Prerelease caveat: top-level installs from an index may still need an exact prerelease spec and/or prerelease allowance until a stable version exists. Exact transitive prerelease pins should resolve once the selected
tangle-cli==0.0.1a2prerelease is allowed/selected.