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

Programming

23417 readers
145 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 2 days 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
[โ€“] fhoekstra@feddit.nl 1 points 1 day ago (1 children)

That is indeed a difficult problem. Integration testing and contract testing can help to avoid this, but one can never be 100% sure.

https://xkcd.com/1172/

[โ€“] HaraldvonBlauzahn@feddit.org 1 points 1 day ago

It is the whole topic of Rich Hickeys talk linked above that breaking an API is a choice. And it is not a solution to not define an API and not agree any contract at all.