Explain what shipped, email stakeholders. Every one is ready to run, and you can adjust it in plain language.
Send a formatted changelog draft for release signoff.
Get a changelog draft in your chosen format, with uncertain changes flagged before the release owner signs off.
Send stakeholders a linked release summary and flag missing details.
Your release contacts get a short note with links to completed issues, while you get a copy and any gaps that need attention.
Draft linked release notes and flag changes needing review.
Your draft release gets concise notes backed by code and tickets, plus questions to settle before you publish.
Date the approved release's changelog and post its link.
Your GitHub changelog stays current as pull requests merge, and your maintainer gets a dated section and link after release approval.
Prepare a note draft for each version ready for review.
Get a release note draft on your team's website that follows your format and highlights questions for the release owner.
Prepare a linked changelog draft for review before release.
Get a GitLab changelog draft in an issue, with changes grouped by type and linked to the work behind them.
Prepare sourced release notes for review before publication.
Get a sourced release note draft in your tracker when version work closes. Review shipped changes against the previous release and resolve open questions.
Review grouped changes and unclear commits before each release.
Your conventional changelog draft arrives in an assigned review issue. Your maintainer sees grouped changes and questions about unclear commits.