-
Notifications
You must be signed in to change notification settings - Fork 173
How to cut a new release
Notes for myself.
Shamelessly copied over from https://truveris.github.io/articles/configuring-pypirc/
Make a .pypirc file:
touch ~/.pypircNow edit the file:
nano ~/.pypircPaste in the following block
[distutils]
index-servers=
pypi
testpypi
[pypi]
username: brodan
password: xxxxxxxxxxxxxxxx
[testpypi]
repository: https://test.pypi.org/legacy/
username: brodan
password: yyyyyyyyyyyyyyyy
If there's anything not passing, it must be fixed before a release can be cut.
Move everything "on deck" under a new header for the release.
bumpversion --dry-run <PUT ONE OF: major, minor, patch> --allow-dirty --verboseInspect the output to make sure the changes that will happen are all correct.
git add .
git commit -m "PUT YOUR COMMIT MESSAGE HERE"bumpversion <PUT ONE OF: major, minor, patch> --verbosebumpversion is configured to automatically commit changes.
If the pre-commit hooks error out, fix whatever needs fixing
and re-commit the changes.
Depending on whether tagging happened or not, you might need to tag the current commit after committing.
git tag -a v<NEW VERSION HERE>git push --tagsThis should, in most cases, suffice:
make releaseIf it doesn't, open up the Makefile and execute each command in order.
master branch is where we keep an "archival" of all releases.
Intent is sort of like a backup to the tags.
git checkout master
git merge dev
git push --tags