Explain what shipped, email stakeholders. Every one is ready to run, and you can adjust it in plain language.
Turn approved milestones into release notes drafts for handoff.
Get a release notes draft with changes linked to completed tickets and code work. Review it in your documentation before publishing.
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.
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.
Publish the approved changes when the release goes 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.
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.
Draft release notes from change bullets and flag earlier announcements.
Get a release note draft that turns rough bullets into clear updates, with possible repeats and missing details called out for your review.
Publish a changelog that matches the tagged release.
Your software changelog covers what shipped in the release, and your editor gets the public page link after publication.