Replies: 1 comment 1 reply
-
👋 the last two steps can be automated with GH actions - I started doing this for lifelines, and it's been much smoother. You give your twine user/pass securely to GH, too (forget how though). The workflow is triggered on creating a new GH release, which was already part of the lifelines-new-release workflow. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
This thread is how the releases work for zEpid. This is both for recording how it operates, and as a reminder for myself (when I inevitably take a long time for the next release)
Once the version is completed, I take the following steps:
pytest tests/
sphinx-build -b html docs builddir
python setup.py sdist bdist_wheel
python -m twine upload -r pypi dist/*
Beta Was this translation helpful? Give feedback.
All reactions