[Feature Request] Automate PyPI deployment

[gregnazario]

See aptos-labs/aptos-core#7410

[gregnazario]

@cursoragent can you look into this if it isn't already

[cursor]

I looked into issue #28 / aptos-core#7410. Automated PyPI deployment is already on main — it was added in March 2026 (a468fa4). The issue was still open because the workflow existed but wasn’t fully documented, and one maintainer setup step remains.

What’s already in place

.github/workflows/publish.yaml runs on published GitHub Releases (and supports a manual dry-run):

1. Unit tests + BDD tests
2. uv build
3. PyPI upload via OIDC trusted publishing (no PYPI_TOKEN secret)

The old v2-publish.yaml workflow was removed; v2 ships inside the main aptos-sdk package.

What was still missing

1. CONTRIBUTING.md said to git tag + push, but the workflow triggers on a GitHub Release, not a tag push alone.
2. No maintainer setup docs for the one-time PyPI trusted-publisher configuration.
3. No version guard — a mistagged release could publish the wrong version.

What I did

Opened PR #116 with:

• Expanded publishing docs (trusted-publisher table, release steps, dry-run instructions)
• A build-step check that fails if the release tag doesn’t match pyproject.toml (e.g. tag v0.12.0 requires version 0.12.0)

One maintainer action before first automated publish

On pypi.org, add a trusted publisher:

Field	Value
Project	aptos-sdk
Owner	aptos-labs
Repository	aptos-python-sdk
Workflow	publish.yaml
Environment	pypi

Then create the pypi GitHub environment (no secrets needed). After that, releasing is: bump version → merge → Publish GitHub Release → CI handles the rest.

Issue #28 can be closed once that PyPI setup is done and a release has been verified end-to-end.