Know your audience
Whatever source you choose for release announcements, try to keep them user-friendly.
End users aren't fond of commit logs. While "merged pull request XY" might be technically highly relevant (for e.g. libraries), it's gibberish to most everyone else.
So be careful with the GitHub module in particular. If you're not using githubs /release tool, a commit log may be used still. Only basic filtering is applied. 🔧 And it's sort of broken at the momement :/
Likewise write Changelogs as summaries. (They're better and more correctly called NEWS or RELEASE-NOTES files actually.)