Strip PyPI publishing from reusable release workflow

ci-tooling 2026-03-30

2 files · 5+ · 269-

2 files changed

python-release.yml Remove repository-url, skip-existing, test-repository, publish-testpypi, publish-pypi inputs and PYPI_TOKEN/TEST_PYPI_TOKEN secrets. Delete the test-release and production release jobs entirely. Simplify the publishing-gate job to a single status message. Bump download-artifact to v8.
action.yml Remove workenv-path input and all virtualenv activation steps. Remove twine-based metadata verification step. Simplify dry-run validation and version extraction to run without a virtualenv.

The reusable release workflow now only builds, validates, and creates a GitHub Release with artifacts. Actual PyPI publishing is delegated to each calling repository’s own workflow, giving repos control over their publishing credentials and gates. decouple architectural
2 files
- python-release.yml
- action.yml
Removing the twine dependency simplifies the release action and eliminates a class of publishing failures caused by mismatched virtualenv paths. remediate internal
1 file
- action.yml