Explain what shipped, email stakeholders. Every one is ready to run, and you can adjust it in plain language.
Explain reader-visible product updates with links to the work behind them.
Your stakeholders get clear release notes backed by code changes and completed tickets, with links to the work behind each update.
Share approved product changes and stated actions by email.
Your stakeholders get key changes and action items by email, with a link to the full release note page.
Draft reader-facing release updates backed by completed tickets.
Your upcoming release page gets notes tied to completed work, and your maintainer gets a draft to review.
Bring confirmed product changes into a changelog draft for approval.
Get a changelog draft in your chosen format, with uncertain changes flagged before the release owner signs off.
Explain completed product changes in a stakeholder release email.
Your release contacts get a short note with links to completed issues, while you get a copy and any gaps that need attention.