Sample work · Texts & Documentation
Changelog: Release notes from a real Git history, versioned according to SemVer
A changelog following 'Keep a Changelog' and a short version for customers are generated from the commits of a demo repository. Each commit appears exactly once, breaking changes are at the top, unclear items are visible, and the version number follows the rules.
Sample work (demo), not a client job. Built as a trial task with invented example data; the check figures below come from the automatic test run and are not polished.
What was built
- Grouped by Conventional Commits, breaking changes first
- Next version determined from history according to SemVer
- Non-conventional items are visibly listed under 'Other'
- Repository invented
How it was checked
Automatic test run on 2026-10-31, taken from the log (test data invented, figures measured):
- Real Git history with 10 demo commits: each grouped exactly once, breaking change at the top, unclear items under 'Other', version 1.4.2 to 2.0.0 according to SemVer
- Verification of patch, minor, and major updates correct
- 11 checks
Limits
What this sample does not cover, so nobody expects more:
- As good as the commit messages; unclear items require a human
- Whether a change is breaking is decided by the owner
- Publishing and tagging in the customer repository only with access and approval
Something like this for your business?
Describe briefly what you need. You get a fixed price before I start; nothing happens without your yes.