CI: Create Action to publish to PyPI on release #1169
Conversation
Creates a GitHub Action workflow that builds and published packaged distribution files to PyPI when a release is published in GitHub.
The secret used in ${{ secrets.PYPI_API_TOKEN }} needs to be created on the settings page of your project on GitHub.
At some point we should probably switch to pyproject.toml as defined in PEP 518.
Codecov Report
@@ Coverage Diff @@
## main #1169 +/- ##
=======================================
Coverage 89.27% 89.27%
=======================================
Files 19 19
Lines 1268 1268
Branches 254 254
=======================================
Hits 1132 1132
Misses 100 100
Partials 36 36 Continue to review full report at Codecov.
|
Only those who can get the PyPI token can do. |
|
LGTM |
|
@tpike3 Thanks for merging! Did you add the |
|
@tpike3 Can you confirm that the |
|
Hmmm...I cannot, I do not have those authorities. @jackiekazil can you confirm if PYPI_API_TOKEN was added. (I did talk to Igor and Natalie thought... thanks) |
|
The GH Actions is not working for 2.1.0 release: https://github.com/projectmesa/mesa/actions/runs/5637000752/job/15269631728. |
|
Raised #1740. |
Creates a GitHub Action workflow that builds and published packaged distribution files to PyPI when a release is published in GitHub.
It builds and deploys the same two files as currently deployed to PyPI with 0.9.0:
Mesa-0.9.0.tar.gz(Source Distribution)Mesa-0.9.0-py3-none-any.whl(Built Distribution)A version to test: package.zip
It runs whenever a GitHub Release is published, either from an existing tag of when creating a new tag when creating the release through the GitHub CLI or web interface (mesa/releases). See Managing releases in a repository for more information.
TODO: The secret used in
${{ secrets.PYPI_API_TOKEN }}needs to be created on the settings page of your project on GitHub. See Creating & using secrets. All maintainers can do so, see Creating & using secrets.At some point (in another PR) we should probably switch to
pyproject.tomlas defined in PEP 518.Example of creating a GitHub release, on which this workflow runs:
