Monthly Update
Use this recurring email to collect the product changes customers should know about in one place. Lead with the most useful release, group smaller updates underneath it, and link to details only when they add context. Replace the sample content each month and keep the order focused on customer value, not your internal shipping sequence.
Build a repeatable issue
Keep a consistent issue name and cadence so customers recognize the email. Use the subject line for the month and strongest release, then check how both survive mobile truncation. Link to the changelog for detail instead of reproducing internal release notes. See the release examples for other structures.