Changelog2 New2 Improved1 Fixed
Content guidelines give you project-wide control over tone and focus for every piece of generated content, with new per-run repo scoping so the right commits always drive the right output.
A new Content guidelines tab in Settings lets you set a default voice preset (Technical, Business, or Mixed) and free-text instructions — like "skip internal refactors" or "keep it casual" — that automatically apply to every changelog, release note, and social post Shipstar generates for your project. You can override these defaults per run in the Regenerate dialog or on any scheduled content, giving you fine-grained control without repetitive manual editing.
When generating content via the dashboard, a schedule, or the MCP tools, you can now limit the commit source to one or more specific tracked repositories instead of pulling from all of them. This means teams with multiple repos can produce focused, accurate changelogs and release notes for each project without noise from unrelated codebases.
"Technical depth" has been renamed to "Voice" throughout the schedule dialog, Regenerate dialog, and Settings, making the control easier to understand at a glance. The free-text field is now consistently labeled "Focus & exclusions" everywhere, so you always know exactly what to type to shape your content.
When a scheduled content run fails, the calendar now displays a persistent failure card with "Open Sources" and "Try again" actions so you never miss a failed run or lose the chance to recover it. No more chasing a disappearing notification to figure out what went wrong.
Previously, failed generation runs surfaced an unhelpful internal retry error message instead of the actual cause. Shipstar now stores and displays the underlying failure reason, making it much faster to diagnose and fix issues with your connected repositories or content settings.
Generated by Shipstar from 5 commits