Shipstar
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.

RSS feed
4 Fixed

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.

  • FixedCode blocks in help center articles now render correctly

    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.

  • FixedKnowledge base slugs are now scoped per project

    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.

  • FixedKnowledge base and blog pages load reliably on first visit

    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.

  • FixedCredits are refunded when a generation fails

    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

4 New3 Improved1 Fixed

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.

  • NewX threads and Slack updates are now posted automatically on approval

    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.

  • NewSchedule delivery destination when you set up a recurring content run

    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.

  • NewManage your content schedules directly from the calendar

    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.

  • NewWeekly content ideas email now ranks and briefs your top writing opportunities

    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.

  • ImprovedScheduled content windows now match your chosen cadence

    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.

  • ImprovedRefreshed dashboard sidebar with smarter navigation and live status

    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.

  • ImprovedSlack product updates are now formatted as concise, readable digests

    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.

  • FixedDelivery failures for scheduled X and Slack posts now trigger an email notification

    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

4 New3 Improved1 Fixed

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.

  • NewGitHub App integration for more reliable repo access

    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.

  • NewServer-rendered changelog pages with permalinks, RSS feed, and social cards

    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.

  • NewBuild-changelog-page agent skill for server-rendered changelogs in your own codebase

    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.

  • New"Add to your website" guide surfaced directly from published content

    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.

  • ImprovedRepublishing a period now replaces the previous version instead of duplicating it

    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.

  • ImprovedChangelog navigation grouped by month with category-color wayfinding

    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.

  • ImprovedWebsite destination now lets you configure a page URL per content type

    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.

  • FixedAuto-published changelogs were stuck on "Loading entries" on the public page

    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

2 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.

  • NewContent guidelines: steer every generated piece without editing prompts

    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.

  • NewScope generated content to specific repos

    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.

  • ImprovedClearer, consistent voice and focus controls across the entire app

    "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.

  • ImprovedScheduled content failures now show a persistent action card instead of a vanishing toast

    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.

  • FixedFailed runs now report the real error, not a cryptic retry wrapper message

    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

2 New3 Improved2 Fixed

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.

  • NewMCP Server Live on Official Registry with 23 Tools

    Shipstar's MCP server is now listed on the Official MCP Registry, Smithery, Glama, and the Claude connectors directory — giving you 23 tools to interact with your changelogs, blog posts, and knowledge base directly from your AI agent or coding environment. Connect via OAuth at mcp.shipstar.ai/mcp with no additional auth setup required.

  • NewClaude Code Plugin Now Available

    You can now install the Shipstar plugin for Claude Code, bundling the hosted MCP endpoint and four agent skills so you can generate and manage changelogs without leaving your editor. OAuth handles authentication automatically — no extra credentials needed.

  • ImprovedFree Plan Now Fully Accessible In-App

    The Free plan is now a first-class option in the in-app upgrade flow — you'll see clear Free, Solo, and Team plan cards with your current plan highlighted, and can switch plans or manage billing without being sent directly to a checkout page. Team owners also get a proper billing portal link instead of a generic Stripe login.

  • FixedMulti-Tenant Content Isolation: Your Published Content Stays Private

    A bug caused published changelogs, blog posts, and knowledge base entries to be visible across all projects — meaning any tenant's content could appear in another tenant's MCP list results or public content pages. Content lists are now strictly scoped to your project, so only your content is ever returned.

  • ImprovedProject Name Now Shown in Email Subjects

    If you're working across multiple projects, email notifications now include the project name in the subject line — covering content reviews, content ideas, changelog confirmations, and release notes — so you can immediately tell which project an email is about. The default project name is omitted to keep subjects clean when you only have one project.

  • FixedMCP Blog Post Ideas Tool No Longer Crashes

    The blog post ideas MCP tool was crashing in production due to a mismatch in the response format returned by the generator. This is now fixed, and all 23 MCP tools have been verified to work correctly end-to-end.

  • ImprovedOAuth Token Prefixes Rebranded to shipstar_*

    API tokens now display with a shipstar_ prefix for clearer identification in your integrations and logs. All previously issued tokens continue to work without any changes on your end.

Generated by Shipstar from 35 commits

Earlier updates

Get updates by email

One email per release week, written by Shipstar. Unsubscribe anytime.

Powered by Shipstar

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.

Get Started FreeView Pricing