Explain what shipped, email stakeholders. Every one is ready to run, and you can adjust it in plain language.
Prepare a draft release page with evidence behind each update.
Get a draft release page that explains what changed and links every update to the work behind it, ready for your review.
Prepare one sourced draft per version for release owner review.
Get a sourced release note draft in your tracker when version work closes. Review shipped changes against the previous release and resolve open questions.
Put approved release notes live when the release card moves to Live.
Your app changelog gets a dated customer update when a release goes live. Your product owner gets the public link on the release card.
Open a changelog review issue for each tagged release.
Your conventional changelog draft arrives in an assigned review issue. Your maintainer sees grouped changes and questions about unclear commits.
Keep published release notes in step with new version tags.
Your GitHub releases get readable notes as new tags arrive, with changes grouped by type and linked to commits.
Draft release notes and surface gaps before release review.
Get a release note draft that turns rough bullets into clear updates, with possible repeats and missing details called out for your review.
Check shipped changes before publishing the release changelog.
Your software changelog covers what shipped in the release, and your editor gets the public page link after publication.