ci: publish to PyPI on GitHub Release via Trusted Publishing - #202
Open
aqeelat wants to merge 7 commits into
Open
ci: publish to PyPI on GitHub Release via Trusted Publishing#202aqeelat wants to merge 7 commits into
aqeelat wants to merge 7 commits into
Conversation
Co-authored-by: Thomas Grainger <tagrain@gmail.com>
pytest-dev is not going to fork this and means it's more re-usable Co-authored-by: Hugo van Kemenade <hugovk@users.noreply.github.com>
Otherwise we have to keep changing this. Co-authored-by: Hugo van Kemenade <hugovk@users.noreply.github.com>
- Split build and publish jobs: build with least privilege via build-and-inspect-python-package (includes twine check and GitHub build provenance attestation), publish with only id-token for PyPI Trusted Publishing - Publish via the release environment with PyPI attestations - Add RELEASING.rst documenting the release process
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
2 participants
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.
Replaces #154, which cannot be reopened or retargeted because its base branch
masterwas deleted.Publishes to PyPI when a GitHub Release is published, following the pytest-mock deploy pattern:
packagejob: builds sdist+wheel withhynek/build-and-inspect-python-package(twine check + wheel-contents check included), attests GitHub build provenance. Onlyid-token: write+attestations: write.publishjob: downloads the artifact and publishes viapypa/gh-action-pypi-publishwith PyPI attestations, through thereleaseenvironment with Trusted Publishing (no token). Onlyid-token: write.github.repository_owner == 'pytest-dev'.RELEASING.rstdocumenting the process.Addresses all review feedback from #154 (split build/publish jobs,
releaseenvironment, RELEASING.rst, owner check,release: publishedtrigger, drop EOL Python pin).Setup needed once by a maintainer: register the PyPI Trusted Publisher for
pytest-timeout(ownerpytest-dev, repopytest-timeout, workflowrelease.yaml, environmentrelease).