andygrove opened a new pull request, #1610: URL: https://github.com/apache/datafusion-ballista/pull/1610
# Which issue does this PR close? Closes #. # Rationale for this change The Python client `ballista` is published to [PyPI](https://pypi.org/project/ballista/) as part of each release, but the procedure was undocumented. The bottom of `.github/workflows/build.yml` has a commented-out publish job with the note "PyPI publish needs to be done manually for now after release passed the vote", and `dev/release/README.md` documents the crates.io publish step but says nothing about PyPI. This PR fills that gap so any committee member added as a maintainer of the PyPI project can run the publish confidently after a successful release vote. # What changes are included in this PR? A new `### Publish Python Wheels to PyPI` section in `dev/release/README.md`, inserted between the existing "Publish on Crates.io" and "Publish Docker Images" sections. The new section covers: - Prerequisites (PyPI / TestPyPI accounts, maintainer access, `~/.pypirc`, `twine`). - Downloading the voted-on wheels from the RC's CI run via `dev/release/download-python-wheels.py`. - Validating the artifacts with `twine check`. - A TestPyPI dry-run with a fresh-venv smoke test, since PyPI uploads are immutable. - The actual `twine upload` to PyPI. - Verification. - Recovery for the realistic failure modes (`twine check` fails, smoke test fails, partial upload). One row is also added to the Post-Release task table near the top of the file. The new section calls out a known CI bug — the macOS arm64 wheel is built twice and no macOS x86_64 wheel is produced — and links to #1608 which tracks the fix. # Are there any user-facing changes? No code changes. Documentation only. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
