Ask HN: How do you handle release notes for multiple audiences?

Summary

For those of you who ship often, when you release updates, do you typically write one set of release notes, or do you end up rewriting them for different audiences?For example: • technical version for developers • simplified version for end users • something more high-level for stakeholders etc…In my current position I’ve seen a plethora of different ways teams, and even the company I currently work for, go about this.What I’ve seen: 1. paste raw GitHub changelogs into customer emails (highly wouldn’t recommend if you’re currently doing this ) 2. manually rewrite the same update multiple times for each audience 3. skip release notes entirely because it’s too much workSo I guess my question is: How do you or your company currently go about handling more than one set of release notes, and do you feel like more than one set is needed?Would love to hear what’s working (or not working) for you, and if you found any tools that help mitigate this issue.