-
Notifications
You must be signed in to change notification settings - Fork 151
Creating a new release (GitHub and PyPi)
Kent Inverarity edited this page May 12, 2022
·
11 revisions
- Ensure you are on master:
$ git checkout master
- Ensure you are using the latest copy of master:
$ git pull origin master
- Check for any local changes to master:
$ git status
- test locally and push if necessary. - Check that GitHub Actions Python CI for
master
is passing. - Find changes since last version release: see list of commits.
- Summarise these changes in docs/source/changelog.rst
- Run the Jupyter Noteook at docs/Add links to GitHub for all issue and PR refs in changelog.ipynb to add hyperlinks for all issue and PR references.
- Commit with a message e.g.
Release v1.3
- Tag with the same message e.g.
git tag v1.3
- Push to github - first the commit:
git push origin master
- ..and then push the new tag:
git push origin tag v1.3
- Create a universal wheel:
python setup.py bdist_wheel --universal
- This will put a new wheel file in
dist/
- Also create a source distribution:
python setup.py sdist
- This will put a source distribution archive in
dist/
- Upload all the new distribution release files (wheel and archive) to PyPI:
twine upload -u USERNAME -p PASSWORD dist/file
- Create a new GitHub release - https://github.com/kinverarity1/lasio/releases/new - select the tag
- Copy the CHANGELOG text in - convert to RST to Markdown quickly by replacing
`#
with#
and`_
with - Copy the wheel and source distribution archive files into the release page.
- Publish the release.
That's it.