What to check
Scan the summary to confirm the main outcomes match the release intent.
Spot check linked PRs to ensure high risk changes are included.
Look for missing contributors, security notes, or breaking changes.
- Ensure the version number matches the tag
- Confirm breaking changes are called out
- Check for missing contributors or PRs
Validate grouping and tone
Make sure changes are grouped in a way your audience can scan quickly.
Rewrite any vague entries so they reflect user impact, not internal jargon.
Publish with confidence
Once the draft looks correct, use it as the source for the GitHub Release.
Keep a copy of the final notes in case you need to re-run the release.
Archive and share
Post the final notes where your team tracks releases (changelog, docs, or internal updates).
Share the draft link internally before publishing for a quick sanity check.
Review and introspect
A thoughtful review makes releases feel intentional.
- Did the draft tell the story you intended for customers?
- Are there recurring missing items you should fix upstream?
- Do you need a lightweight approval step before publishing?