Autorelease

Latest version: v0.5.0

Safety actively analyzes 626071 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 3 of 5

0.2.0

New features
* Support for PACKAGE_IMPORT_NAME (60)

0.1.2

Bugs fixed
* Fixes for problems found by OpenPathSampling (54)

0.1.1

Bugs fixed
* Fix issues with less-than-perfect version tags (52)

0.1.0

This is the public-ready version of Autorelease. Thanks to the ability to [import Travis configs](https://blog.travis-ci.com/2019-11-11-build-config-imports), this can now finally be the project I've wanted it to be -- easily used by different projects, my own or those of others.

More docs still need to be written, but the main idea is that you keep a particular branch `stable` from which you do your releases. When you want to do a release, you make a PR against `stable`. It runs tests and a test deployment; when merged it cuts a GitHub release and pushes the real deployment. All without you needing to worry about it!

Basic setup process is:

* vendor the `setup.py` and `version.py` scripts from here
* write your `setup.cfg`
* add a few environment variables to your Travis script: `AUTORELEASE_TOKEN` (a GitHub personal access token) and pypi credentials $TWINE_USERNAME and $TWINE_PASSWORD (should be the same for both pypi and testpypi)
* import `dwhswenson/autorelease:autorelease-travis.ymlv0.1.0` in your Travis script
* optionally, write a small script to check that your branch/version behavior is correct

(Note: Version 0.1.0 is essentially a repackaging of 0.0.18, so there is no changelog here.)

0.0.18

New features
* Improve testpypi deployment (48)

0.0.17

New features
* Scripts to improve testpypi integration (45)

Page 3 of 5

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.