Release notes
Write for people who were not in the repo.
Sources
git logon the range the user named (tag, branch, or SHA).- Existing
CHANGELOG.mdordocs/releases/if present.
Do not quote private tracker comments, local paths, or tool transcripts.
Shape
- What changed, in user terms.
- Why it matters, one line when it is not obvious.
- Breaking changes called out first.
Skip chore-only commits unless they are the whole release.
Public bar
No session or run ids, no absolute machine paths, no provider or account detail, no paste of a user message. An issue mention is enough for a bugfix.