Release Notes Newsletter
A release notes newsletter is the most direct line to your users — and the first thing teams stop sending, because every issue means gathering changes, writing copy, and wrestling an email tool. Shipstar runs the whole thing: it writes each issue from your GitHub activity, manages your subscriber lists with proper opt-in, and delivers on your cadence with compliant unsubscribe handling built in.
Product Update Emails Written for You
Every issue of your newsletter starts as an AI draft built from what actually shipped — features, improvements, and fixes pulled from your commits and merged pull requests, written in your configured voice. You edit and approve rather than compose. The newsletter that used to consume an afternoon per issue becomes a ten-minute review, which is the difference between a newsletter that exists and one that used to.
Subscriber Lists Without a Separate Email Tool
Shipstar manages recipients natively: mailing lists per project, a double-opt-in subscribe flow so every address confirmed they want your updates, and clean list hygiene throughout. Developers can manage lists and recipients through the API. No syncing subscribers to a general-purpose newsletter platform, no CSV exports, no second subscription to pay for.
Deliverability and Compliance by Default
Update emails live or die on trust. Every message Shipstar sends carries a per-recipient one-click unsubscribe link (RFC 8058 compliant), and unsubscribes are permanent — re-adding an address can never resurrect an opt-out. Sends are claimed once per release, so a retry or a double-click never emails your list twice. The compliance details you'd otherwise learn the hard way are simply handled.
One Pipeline with the Rest of Your Release Comms
The newsletter isn't a separate workflow — it's another destination for the release notes you already approved. The same content that updates your changelog page and posts to Slack also lands in subscriber inboxes, so email never lags the changelog and nothing gets announced in one place but not the other. Changelog followers can subscribe to email notifications, growing the list from the page itself.
Why teams choose Shipstar
- Each newsletter issue drafted automatically from shipped changes
- Native mailing lists with double opt-in — no external email tool
- One-click unsubscribe and duplicate-send protection built in
- Email stays in sync with your changelog and other channels automatically
Frequently asked questions
How does the release notes newsletter get written?
Shipstar generates each issue from the commits and pull requests that shipped since your last send, in the voice you configure. The draft waits in review — edit it, approve it, and it goes to your mailing lists.
Do I need Mailchimp or another email tool alongside Shipstar?
No. Shipstar includes mailing list management, a double-opt-in subscribe flow, sending, and unsubscribe handling. It's product update email software and the content pipeline in one.
How are unsubscribes handled?
Every email includes a per-recipient one-click unsubscribe link that works instantly, per RFC 8058. Unsubscribed recipients are deactivated permanently — re-importing or re-adding their address cannot opt them back in.
Can users subscribe to updates themselves?
Yes. Your hosted changelog offers a double-opt-in email subscription, so readers can follow releases directly from the page. You can also add recipients to mailing lists via the dashboard or API for existing customer bases — with opt-out always honored.
Explore more
Explore related pages
Ship it. Share it. Celebrate it.
Release notes on autopilot.
Free to start. Connect your repo in 30 seconds.
No credit card required · Setup in 30 seconds