Observation from writing a lot of release posts: the first line decides everything.

Compare:

  • “Refactored ExportService, closed PROJ-2231”
  • “You can now export a single month instead of your entire history”

Structure that tends to work:

  1. user-visible change, one sentence
  2. who it helps
  3. one concrete example
  4. link to full notes (internals go there)

And be careful with “faster” unless you have a measurement you are willing to explain.

One practical trick: if your changelog has RSS, have something turn new entries into drafts (GPTpost does this, there are other ways) so the social post is never forgotten.

What open-source projects write release posts you actually enjoy reading?

https://oraglegpt.org/use-cases/developer-relations/