Explain what shipped, email stakeholders. Every one is ready to run, and you can adjust it in plain language.
Keep stakeholders informed of shipped changes after each release.
Your stakeholders get clear release notes backed by code changes and completed tickets, with links to the work behind each update.
Summarize release changes in a draft for the maintainer.
Get a changelog draft for your next release, with customer-facing updates linked to the work behind them and emailed for review.
Summarize merged changes and completed tickets for release review.
Your upcoming release page gets notes tied to completed work, and your maintainer gets a draft to review.
Turn release comparisons into draft notes for owner review.
Get a changelog draft in your chosen format, with uncertain changes flagged before the release owner signs off.