alver
Easy management of versions, releases and changelog.
The alver release flow
- Run
alver bump vx.y.z - Edit CHANGELOG.md as needed.
- Create a PR, discuss, merge.
- -> Github does the rest (publish release to Pypi and GH).
This flow is based on the idea that a release deserves the care of a human to at least approve the generated release notes, but from then on a release should be as automatic as it can get.
The release workflow on Github Actions triggers when a branch named release is merged into main,
but can also be triggered manually or by pushing a tag vx.y.z.
So if you e.g. forgot to setup the trusted publisher, you can just retry.
Adopting the alver flow in your project
Install alver:
pip install alveror use your favorite installer.
Meet the assumptions made by alver:
- Your version is defined in
pyproject.toml,__init__.py, or_version.py. - You have a CHANGELOG.md with headers marked as
## [v1.0.0] - 09-11-2026. If no changelog exists, alver will create it.
To setup Github actions:
- Copy release.yml into your project.
- Create a
build.ymlthat does the build and published the artifacts todist. - At Pypi: setup trusted publishing, using
release.ymland thepypienvironment. - At Github: in the settings create an environment called
pypi.
Using the alver CLI tool
usage: alver [-h] {version,gitversion,format,bump,notes,changelog-from-gh,changelog-to-gh} ...
positional arguments:
{version,bump,notes,changelog-from-gh,changelog-to-gh}
version Print the current project version (from _version.py, __init__.py, or pyproject.toml).
gitversion Print the detailed project version based on git tags and history (like 'version', but refined), e.g. 1.2.3.post4+gabcdef1.
format Format CHANGELOG.md in place, fixes section headers and blank lines.
bump Bump to the given version and add a changelog section with gh-generated release notes, e.g. `alver bump v1.2.3`.
notes Print the release notes for the given version from CHANGELOG.md, e.g. `alver notes v1.2.3`.
changelog-from-gh Create/update CHANGELOG.md sections from the GitHub releases of this repo for the given version, e.g. `alver
changelog-from-gh v1.2.3` ('*' = all releases).
changelog-to-gh Update the gh release notes from the CHANGELOG.md section of the given version, e.g. `alver changelog-to-gh v1.2.3`
('*' = all sections).
options:
-h, --help show this help message and exit
Using alver as a library
get_detailed_version_of_lib(module) -> str | None: get the git-enhanced version of a library.get_detailed_version(version: str, filename: str) -> str: get the git-enhanced version of a module's version and filename.
Metadata
Release files for alver 1.2.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| alver-1.2.4.tar.gz | 14.4 kB | With provenance | Details for alver-1.2.4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| alver-1.2.4-py3-none-any.whl | Python 3 | none | any | Details for alver-1.2.4-py3-none-any.whl |
Total release size: 30.6 kB
Release files / alver-1.2.4.tar.gz
| Download URL | alver-1.2.4.tar.gz |
|---|---|
| Size | 14.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c0b89d3b101cbe96554b09be2d930b83c6947e1ad306ab9594b36c3f5ae43b6a
|
|
BLAKE2b-256 checksum How to use checksums |
4680867df3e5ec3722dc5c5e140eb4f4e0ac64915b498377c70cdaba721b439a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 10, 2026.
Transparency logRelease files / alver-1.2.4-py3-none-any.whl
| Download URL | alver-1.2.4-py3-none-any.whl |
|---|---|
| Size | 16.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9f00090903a0f9a768378ef71fe6c04ce23f9220482ff832e71d29e7cc8d5531
|
|
BLAKE2b-256 checksum How to use checksums |
a3947489455ebbcd1cd259969e7890fe933eb04156a3a4e7286a146800bde643
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 10, 2026.
Transparency logSecurity for alver 1.2.4
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.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for alver-1.2.4.tar.gz
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 Nov 10, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.