A quiet week behind the scenes — no customer-facing product changes shipped during this period.
Generated by Shipstar from 1 commits
Changelog
What's New in Shipstar
New features, improvements, and fixes — every entry below was written by Shipstar from our own commits, and published by the same pipeline we sell.
Shipstar now lets you sync, import, and manage mailing list recipients directly from the dashboard or API — and MCP tools for mailing lists are live.
You can now import recipients via CSV, export your lists, edit contact details, and soft-remove or restore recipients — all from the Shipstar dashboard. Each recipient can carry a name, external ID, and custom attributes, making it easy to manage your audience without leaving the platform.
A new set of API endpoints lets you keep your Shipstar mailing lists in sync with your own user database — upsert recipients in bulk, remove them by email or external ID, and export the full list as CSV. This means your announcement audience always reflects your actual users, no manual updates required.
Three new MCP tools — create mailing list, upsert recipients, and remove recipients — are now available, letting you build and maintain your announcement audiences programmatically as part of your existing workflows.
Scheduled X threads and LinkedIn posts now only go out when your commits contain genuine product changes your users can benefit from. When a release contains only internal work, Shipstar declines to post rather than publishing content that isn't meaningful to your audience — and refunds the credit.
When a recipient has a name on file, Shipstar now uses it in the email greeting, making your release announcements feel more personal to the people who receive them.
Generated by Shipstar from 37 commits
Shipstar now publishes help center articles with perfectly formatted code blocks, and knowledge base slugs are isolated per project — so your docs stay accurate and your projects stay independent.
Help center articles published through Shipstar now preserve code formatting exactly — multi-line functions, shell commands, and code samples appear as intended for your readers. Any previously published articles with affected code blocks have been automatically repaired.
Each project in Shipstar maintains its own knowledge base slug, so publishing or syncing a help center for one project no longer affects any other. Teams managing multiple projects can publish independently without their knowledge bases interfering with each other.
Knowledge base and blog API endpoints now respond correctly the first time a piece of content is embedded on a new page. As a bonus, embedding content on a new page no longer causes its published date to update unexpectedly.
If a content generation run fails for any reason, Shipstar now automatically refunds the credits charged for that run. Retry attempts are also capped, so a single failed job no longer accumulates repeated charges.
Generated by Shipstar from 30 commits
No user-facing product changes shipped this period.
Generated by Shipstar from 3 commits
Shipstar now automatically posts to X and Slack when you approve content, adds full schedule management from the calendar, and overhauls the dashboard with a smarter sidebar and cleaner navigation.
Approving a scheduled X thread or Slack product update now publishes it directly to the destination — no extra manual step required. The calendar and review pane link straight to the live post, and a clear notice appears if a delivery needs attention so nothing slips through quietly.
The schedule editor now lets you choose exactly where each content type will land — a specific Slack channel, your connected X account, Intercom, your mailing list, or your public changelog — at the time you create the schedule. Each occurrence carries that destination automatically, so content generated on a cadence is delivered without any manual routing.
Every event on the Shipstar calendar now surfaces a schedule summary and a full schedule menu — letting you edit, pause, resume, skip an occurrence, or delete a series without leaving the calendar view. Paused schedules are shown with a dashed chip so their status is always visible at a glance.
The ideas email now leads with your highest-priority content pick — including a working title, a one-line brief, and the specific commits behind it — and lists the rest as compact rows you can draft with a single click. Draft links open a confirmation dialog showing the brief, credit cost, and balance before anything is generated.
Daily, weekday, and weekly schedules now look back only as far as their cadence — a daily run covers one day, a weekly run covers one week — so each generated update reflects what actually shipped in that window rather than repeating the same accumulated history every time.
The Shipstar sidebar now follows the product workflow — Review, Calendar, and Generate come first, followed by Connections and Developers — and surfaces live status at a glance: draft counts on Review, your tracked repo count on Sources, and a credit warning on Generate. On mobile, the sidebar becomes a proper overlay drawer with full keyboard and focus support.
Generated Slack updates now follow a tight digest format — a title line, a summary sentence, and up to six punchy bullets — keeping your team posts skimmable and on-brand. Daily and weekly updates each have appropriate length caps and no longer include section headers or nested bullets that look out of place in Slack.
When a scheduled post cannot be delivered to X or Slack, Shipstar now emails the schedule owner with the details, the next automatic retry time, and direct links to fix the issue — such as reconnecting a destination or retrying immediately from the calendar sheet.
Generated by Shipstar from 32 commits
the project now publishes fully crawlable, SEO-ready changelogs with per-period permalinks and social cards, adds a GitHub App integration, and makes it easy to embed published content directly on your own site.
You can now connect your repositories through the official the project GitHub App — offering more stable, org-level access — instead of relying solely on OAuth. Existing OAuth connections can upgrade in place, and projects with multiple installations get a picker to choose the right one.
Your changelog is now a fully crawlable, SEO-friendly page with a permanent URL for every release period, an RSS feed, and auto-generated Open Graph social cards — so crawlers, AI answer engines, and social platforms all see your release content instead of a blank widget. Each period also gets a human-readable slug like `my-app-changelog-2026-08-28` that stays stable across regenerations.
A new coding-agent skill guides your AI assistant through adding a fully server-rendered, crawlable changelog page directly to your own website — complete with semantic HTML, JSON-LD, fail-closed feeds, and sitemap integration. This closes the gap where the embed widget was invisible to search engines and AI answer engines.
After publishing, the project now shows an "Add to your website" button with three ready-to-paste integration paths: the embed widget snippet, the agent skill for a server-rendered page, and the API and RSS endpoints. You no longer have to hunt for the right snippet or figure out how to get your changelog live on your own site.
Regenerating and republishing a changelog for the same period used to create a second entry in your feed and on your site. Now the project automatically supersedes the old version, preserving your public permalink and embed snippet so links never break when you update content.
Period pills are now organized under month headings with compact date-range labels so dozens of release periods fit comfortably on mobile without horizontal overflow. Each period also shows a color-coded category summary — like "2 New · 1 Breaking Change" — so you can scan at a glance which weeks had significant or breaking changes.
You can now set a specific page URL for each content type (changelog, blog, knowledge base) in your Website destination settings. The project uses this to show a "Published" link and a correct "not on your site yet" prompt even for server-rendered pages that don't send a Referer header.
Content published automatically never received a public slug, so the public changelog page couldn't resolve it and displayed a permanent loading spinner. Auto-published changelogs now get a slug assigned at publish time, and the page falls back gracefully to inline entries if a slug is unavailable.
Generated by Shipstar from 77 commits
Earlier updates
- 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.
- Shipstar's MCP server is now live on the official registry with 23 tools, the Free plan is fully accessible in-app, and a multi-tenant content isolation fix ensures your published content stays scoped to your project.
- Team members can now work across projects independently with a new sidebar project switcher, and Slack review channels are now configured per project rather than shared across all projects.
- Team plan with per-seat billing and collaborative workflows ships alongside mailing list email delivery, a credit metering system, and major MCP agent capabilities — making it easier than ever for teams to automate and distribute their release communications.
- Users stay logged in through backend deploys, scheduled content generation is now reliable, and emails render with sharper typography and better contrast across all clients.
- The calendar editor gets a Publish Now action and smarter scheduling, while the timeline list gains status badges and sort controls for better content visibility.
- Drag-and-drop calendar rescheduling, smarter Slack review previews, and a unified blog post experience ship this week alongside a wave of calendar reliability fixes.
- Major publishing workflow overhaul, a redesigned changelog list view, and a new weekly calendar — plus 40 new pages added to the marketing site.
- Introducing the Content Calendar, a unified Drafts hub, and public Changelog publishing — your entire content workflow now lives in one place.
Get updates by email
One email per release week, written by Shipstar. Unsubscribe anytime.
Want a Changelog That Writes Itself?
This page is Shipstar's own output. Connect your repo and get the same for your product — changelogs, release notes, and social posts, free to get started.