Manage properly semver in your repository
The easiest way to manage semantic versioning in your project and generate an automatic Changelog file.
The semantic versioning spec involves several possible variations, but to simplify, in Semversioner we are using the three-part version number:
Constructed with the following guidelines:
- Breaking backward compatibility or major features bumps the major (and resets the minor and patch).
- New additions without breaking backward compatibility bumps the minor (and resets the patch).
- Bug fixes and misc changes bumps the patch.
An example would be 1.0.0
$ pip install semversioner
Bumping the version
In your local environment your will use the CLI to create the different changeset files that will be committed with your code. For example:
$ semversioner add-change --type patch --description "Fix security vulnerability with authentication."
Then, in your CI/CD tool you will need to release (generating automatically version number) and creating the the changelog file.
$ semversioner release
As a part of your CI/CD workflow, you will be able to generate the Changelog file with all changes.
$ semversioner changelog > CHANGELOG.md
Made with ♥ by
Raul Gomis <https://twitter.com/rgomis>.
Release history Release notifications | RSS feed
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
|Filename, size||File type||Python version||Upload date||Hashes|
|Filename, size semversioner-0.6.14.tar.gz (5.7 kB)||File type Source||Python version None||Upload date||Hashes View|