Fill in the name you wish to publish your new PyPI project under (the name value in your setup.cfg or pyproject.toml), the GitHub repository owner’s name (org or user), and repository name, and the name of the release workflow file under the .github/ folder, see Creating a workflow definition. Finally, add the name of the GitHub Environment (pypi) we’re going set up under your repository. Register the trusted publisher.
This workflow builds native python wheels, which is fine for packages that don't contain compiled extensions. However, we need to use cibuildwheel to build portable binary wheels using manylinux. Have a look at the examples I gave.
Closes #57
Modified GitHub Action config following python packaging guide.
This will trigger on each
v*.*.*
tag. I've commented outgithub-release
andpublish-to-testpypi
sections, but they can be easily re-enabled.To enable, the following configuration is required:
Go to https://pypi.org/manage/account/publishing/.
Fill in the name you wish to publish your new PyPI project under (the name value in your setup.cfg or pyproject.toml), the GitHub repository owner’s name (org or user), and repository name, and the name of the release workflow file under the .github/ folder, see Creating a workflow definition. Finally, add the name of the GitHub Environment (pypi) we’re going set up under your repository. Register the trusted publisher.