Changelog Based Versioning
Documentation menu
Versioning from a changelog keeps the release number and the release notes in one place. The pipeline reads the changelog, derives the version and tags the commit.
One source of truth
The changelog entry describes what changed and the version that contains it. A human reviews the entry before the release, which is the right moment to decide whether the change is major, minor or patch.
Automation
The pipeline can extract the current version, apply it to the package and create a git tag. The tag connects the package to the exact commit, and the changelog connects the commit to the reason for the release.
Follow semver
The rules only work when the numbers mean something. Read Semantic Versioning in Practice before you automate the decision.