Skip to content

Build and verify Python releases before publishing to PyPI - #5

Merged
vogti merged 1 commit into
masterfrom
codex/python-release-pipeline
Nov 15, 2026
Merged

vogti merged 1 commit into
masterfrom
codex/python-release-pipeline

Conversation

@vogti

@vogti vogti commented Nov 15, 2026

Copy link
Copy Markdown
Member

The PyPI workflow still uses Python 3.8 on ubuntu-latest, which has no setup-python build on Ubuntu 26.04. Build a wheel and source distribution on Python 3.12, check their metadata, and install the wheel before publishing. Pull requests and manual runs stop after validation and artifact upload to GitHub Actions. Only a published stable GitHub release can use the PyPI Trusted Publisher, whose repository and workflow identity are unchanged.

Package metadata now requires Python 3.9, the oldest supported runtime in the test matrix and the minimum needed by the connector’s type annotations.

Validated locally with v2.0.0: both formats passed twine check --strict; the wheel installed and imported on Python 3.12 and the source distribution on Python 3.9. Both contain polypheny==2.0.0 metadata and require Prism API 2.2. No package was uploaded to PyPI.

Build a wheel and source distribution on Python 3.12. Check metadata and install the wheel without upload in PRs and manual builds; grant PyPI OIDC only to the release upload job. Declare Python 3.9 as the minimum supported runtime.
@vogti
vogti merged commit a9a02c4 into master Nov 15, 2026
52 checks passed
@vogti
vogti deleted the codex/python-release-pipeline branch November 15, 2026 16:47
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