this post was submitted on 08 Nov 2025
17 points (90.5% liked)

Programming

23417 readers
235 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 2 years ago
MODERATORS
snowe@programming.dev
Ategon@programming.dev
MaungaHikoi@lemmy.nz
UlrikHD@programming.dev
17
Automated changelog generation (fhoekstra.eu)
submitted 1 day ago by fhoekstra@feddit.nl to c/programming@programming.dev
11 comments fedilink hide all child comments
 

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.

you are viewing a single comment's thread
view the rest of the comments
[–] silverpill@mitra.social 6 points 1 day 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.