Autorelease
Release management for GitHub and continuous integration, based on branches. The basic philosophy is to maintain development branches (which always have development versions of the code) and release branches (which always have release versions of the code). The workflow for a release is therefore:
- Update the version for release and make a PR to a stable branch; the top post will be the release notes.
- Merge the PR.
That's it. Autorelease handles the rest.
When you make the PR to a stable branch, Autorelease will deploy the package to testpypi, and re-download it and test it again. This ensures that you don't publish broken packages. After you merge to the stable branch, Autorelease will cut a new release on GitHub, and then publish the release on PyPI.
Tools included:
- Travis config imports and scripts to automatically test-deploy on testpypi, then cut a GitHub release, then deploy to PyPI.
- Vendor-able GitHub Actions workflows for test-deploy, GitHub release, and PyPI deploy.
- Vendor-able
version.pythat gives one true location for version (setup.cfg) while also enabling developer installs to give full and correct version information. - Vendor-able
setup.pythat keeps all user-required information in thesetup.cfg. - Script to draft release notes based on labels on merged PRs.
If you're a Python developer who uses Travis and GitHub, Autorelease handles everything related to releasing to PyPI.
1 maintainer
Metadata
1 maintainer
Release files for autorelease 0.7.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| autorelease-0.7.1.tar.gz | 27.3 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| autorelease-0.7.1-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details |
Total release size: 62.2 kB
Release files / autorelease-0.7.1.tar.gz
| Download URL | autorelease-0.7.1.tar.gz |
|---|---|
| Size | 27.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
dbe37b9a631f7cfbdeb97cd4a34da14a92e5e1f2ea42c09169f22e0c1ba7405e
|
|
BLAKE2b-256 checksum How to use checksums |
b069f972cc88b684161a575cccc48ad9f5c3feffdd23069efd50227cd33058aa
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 22, 2026.
Transparency logRelease files / autorelease-0.7.1-py2.py3-none-any.whl
| Download URL | autorelease-0.7.1-py2.py3-none-any.whl |
|---|---|
| Size | 34.9 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
736f8fed505dff22ebf25f91646e07c2aebd92dfe09355cb04d54e529a2821a2
|
|
BLAKE2b-256 checksum How to use checksums |
0d50453a3598835c4220d153f218f4cebab3c496d9f2ebe04eed99bdf857d043
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 22, 2026.
Transparency log
