Changelog From Conventional Commits: Git-Cliff
fhoekstra.eu
The changelog in platform engineering At my current job, we maintain a package that is used by developers in their own codebases to use a database service on the platform. Like any package or artifact that is released to then be used by application developers, this requires a clear release with a semantic version that communicates what users can expect from it: Does it contain only fixes (patch), or are there new features in the release (minor)? Most importantly, do users (potentially) need to change how they use the package when upgrading (major)?

When publishing a package for use by programmers, automated changelog generation is very beneficial. In this blog post, I explore how to do it in a simple way that works everywhere.

  • silverpill@mitra.social
    4·
    17 hours ago

    @fhoekstra Such tools are worse than useless. Every time I see an automated changelog it’s mix of dependabot commits, “fix CI” and other meaningless messages.

    Not having a changelog is better, because then you just go straight to a commit history and don’t waste your time trying to parse machine-generated slop.