status-im/PyGithub
1
0
Fork 0
mirror of https://github.com/status-im/PyGithub.git synced 2026-08-31 19:01:15 +00:00
Code Issues Packages Projects Releases Wiki Activity
Files
b94a83cbf328bbcdabeaaaef572d5ca360e1dbba
PyGithub/DEPLOY.md
T
Liuyang WanandSteve Kowalik d6e77ba1e2 Drop Travis in favor of Github workflow (#1488) 
* Drop Travis CI

* Update DEPLOY.md about new workflow of uploading new version to PyPI

* Upload coverage data to Codecov

Co-Authored-By: Steve Kowalik <steven@wedontsleep.org>
2020-04-27 21:54:20 +10:00

930 B
Raw Blame History

Upload a new version to PyPI

Github workflow (.github/workflows/python-publish.yml) will push tagged commits to PyPI. Here are the steps:

  1. Run manage.py
./manage.sh publish
Next version number? (previous: 'XXX')

  1. Give the new version number based on previous version (Use semantic versioning)

  2. Create a new Github release from the tag that has just been committed, with the same release note from doc/changes.rst. This step is the hook that will trigger the workflow. (also needed for some web spiders for changelog parsing)

  3. Now the push will be on hold until you press Enter. Manually inspect the changelog (doc/changes.rst) to make changes if necessary. Once you are sure, go back and press Enter.

  4. Once the python-publish workflow completes, a new version will appear on PyPI shortly.

Reference in New Issue View Git Blame Copy Permalink