The what's-new email used to go out weekly, built from whatever release notes carried that week's dates. That had two problems.
A week of product work is often one fix and a copy change, which makes for a thin email — and a thin email teaches people to ignore the next one. It is monthly now, so there is usually something worth reading.
It also carried everything we shipped, including work that isn't product news at all. A blog and a set of comparison pages are real things we made, and neither belongs in the inbox of somebody paying us to track their time. Release notes can now say who a change is for, and only product changes go in the email.
The last change is the one that matters most: a person reads the month's draft before anybody else receives it. The notes are written by whoever shipped each change, which is the right place to record work and the wrong place to decide what belongs in a customer's inbox. If the draft is wrong, it gets fixed before it goes out — and if nobody reads it, nothing sends.
Nothing shipped in a month? Then no email. A digest that says "nothing this month" is one people filter, and then the month that mattered is filtered too.