Explain what shipped, email stakeholders. Every one is ready to run, and you can adjust it in plain language.
Send client software release notes from approved briefs.
Your stakeholders get release notes in your team's format, and the release owner gets a copy of the sent note.
Email release contacts about completed client software changes.
Your release contacts get a short note with links to completed issues, while you get a copy and any gaps that need attention.
Draft notes on changes between versions of client software.
Get a release note draft in your docs after your repository publishes a version, with a clear summary and links to the changes behind it.
Summarize verified client software changes for the next release.
Get a GitLab changelog draft in an issue, with changes grouped by type and linked to the work behind them.