This PR adds a workflow which automatically publishes releases to PyPI.
This is almost identical to the corresponding workflow on Envisage (which ran successfully this morning). The only difference is an extra line to upgrade pip if necessary. (This line doesn't make a difference right now, but it's not inconceivable that some future release of build or twine can only be installed properly with an updated pip.)
I've tested the commands in the workflow manually by:
This PR adds a workflow which automatically publishes releases to PyPI.
This is almost identical to the corresponding workflow on Envisage (which ran successfully this morning). The only difference is an extra line to upgrade
pip
if necessary. (This line doesn't make a difference right now, but it's not inconceivable that some future release ofbuild
ortwine
can only be installed properly with an updatedpip
.)I've tested the commands in the workflow manually by:
python -m pip install --upgrade pip
andpython -m pip install build twine
python -m build
followed bypython -m twine check --strict dist/*
.The strict checks passed for me.