Explain what shipped, email stakeholders. Every one is ready to run, and you can adjust it in plain language.
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 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.
Save linked release notes as an unpublished page for review.
Get a draft release page that explains what changed and links every update to the work behind it, ready for your review.
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.
Publish categorized notes for each newly tagged release.
Your GitHub releases get readable notes as new tags arrive, with changes grouped by type and linked to commits.