<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
    <channel>
        <title>Shipstar Changelog</title>
        <link>https://shipstar.ai/changelog</link>
        <description>Product updates for Shipstar — new features, improvements, and fixes, written by Shipstar from its own commits.</description>
        <lastBuildDate>Mon, 31 Aug 2026 03:16:56 GMT</lastBuildDate>
        <docs>https://validator.w3.org/feed/docs/rss2.html</docs>
        <generator>https://github.com/jpmonette/feed</generator>
        <language>en</language>
        <image>
            <title>Shipstar Changelog</title>
            <url>https://shipstar.ai/social/shipstar-banner.png</url>
            <link>https://shipstar.ai/changelog</link>
        </image>
        <copyright>© 2026 Shipstar. All rights reserved.</copyright>
        <item>
            <title><![CDATA[What's New — Aug 21–28, 2026]]></title>
            <link>https://shipstar.ai/changelog/julians-team-changelog-2026-08-28</link>
            <guid isPermaLink="false">https://shipstar.ai/changelog/julians-team-changelog-2026-08-28</guid>
            <pubDate>Fri, 28 Aug 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[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.]]></description>
            <content:encoded><![CDATA[<ul><li><strong>[New] GitHub App integration for more reliable repo access</strong> — 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.</li><li><strong>[New] Server-rendered changelog pages with permalinks, RSS feed, and social cards</strong> — 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.</li><li><strong>[New] Build-changelog-page agent skill for server-rendered changelogs in your own codebase</strong> — 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.</li><li><strong>[New] "Add to your website" guide surfaced directly from published content</strong> — 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.</li><li><strong>[Improved] Republishing a period now replaces the previous version instead of duplicating it</strong> — 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.</li><li><strong>[Improved] Changelog navigation grouped by month with category-color wayfinding</strong> — 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.</li><li><strong>[Improved] Website destination now lets you configure a page URL per content type</strong> — 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.</li><li><strong>[Fixed] Auto-published changelogs were stuck on "Loading entries" on the public page</strong> — 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.</li></ul>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What's New — Aug 14–21, 2026]]></title>
            <link>https://shipstar.ai/changelog/Bb1GeHJzPQiO</link>
            <guid isPermaLink="false">https://shipstar.ai/changelog/Bb1GeHJzPQiO</guid>
            <pubDate>Fri, 21 Aug 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[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.]]></description>
            <content:encoded><![CDATA[<ul><li><strong>[New] Content guidelines: steer every generated piece without editing prompts</strong> — 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.</li><li><strong>[New] Scope generated content to specific repos</strong> — 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.</li><li><strong>[Improved] Clearer, consistent voice and focus controls across the entire app</strong> — "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.</li><li><strong>[Improved] Scheduled content failures now show a persistent action card instead of a vanishing toast</strong> — 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.</li><li><strong>[Fixed] Failed runs now report the real error, not a cryptic retry wrapper message</strong> — 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.</li></ul>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What's New — Aug 7–14, 2026]]></title>
            <link>https://shipstar.ai/changelog/m-aGnjxQZYla</link>
            <guid isPermaLink="false">https://shipstar.ai/changelog/m-aGnjxQZYla</guid>
            <pubDate>Fri, 14 Aug 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[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.]]></description>
            <content:encoded><![CDATA[<ul><li><strong>[New] MCP Server Live on Official Registry with 23 Tools</strong> — 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.</li><li><strong>[New] Claude Code Plugin Now Available</strong> — 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.</li><li><strong>[Improved] Free Plan Now Fully Accessible In-App</strong> — 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.</li><li><strong>[Fixed] Multi-Tenant Content Isolation: Your Published Content Stays Private</strong> — 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.</li><li><strong>[Improved] Project Name Now Shown in Email Subjects</strong> — 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.</li><li><strong>[Fixed] MCP Blog Post Ideas Tool No Longer Crashes</strong> — 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.</li><li><strong>[Improved] OAuth Token Prefixes Rebranded to shipstar_*</strong> — 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.</li></ul>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What's New — Jul 24–31, 2026]]></title>
            <link>https://shipstar.ai/changelog/Mmm23twxa1M9</link>
            <guid isPermaLink="false">https://shipstar.ai/changelog/Mmm23twxa1M9</guid>
            <pubDate>Fri, 31 Jul 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[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.]]></description>
            <content:encoded><![CDATA[<ul><li><strong>[New] Per-user project switcher in the sidebar</strong> — A new Notion-style project menu in the dashboard sidebar lets each team member switch between projects independently, so your active project no longer affects your teammates'. You can also rename projects and create new ones directly from the sidebar.</li><li><strong>[Improved] Slack review channel is now configured per project</strong> — The Slack channel for content-review notifications can now be set individually for each project from the Destinations page, so teams with multiple projects can route reviews to the right channel. Existing setups continue to work without any changes.</li><li><strong>[Improved] Content ideas emails now go to whoever scheduled the generation</strong> — Scheduled content ideas are now emailed to the team member who set up the schedule, rather than always going to the team owner. This ensures the right person receives their own content suggestions in their inbox.</li></ul>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What's New — Jul 10–17, 2026]]></title>
            <link>https://shipstar.ai/changelog/3MJ3jq2OwfEL</link>
            <guid isPermaLink="false">https://shipstar.ai/changelog/3MJ3jq2OwfEL</guid>
            <pubDate>Fri, 17 Jul 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[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.]]></description>
            <content:encoded><![CDATA[<ul><li><strong>[New] Team Plan with Per-Seat Billing and Collaborative Workflows</strong> — Teams can now collaborate under a shared subscription with per-seat Stripe billing, pooled generation credits (50k/seat), and email invitations — any team member can invite colleagues, and content review notifications fan out to the whole team. Project limits have been updated across all plans: Free (1 project), Solo (3 projects), and Team (unlimited).</li><li><strong>[New] Mailing Lists and Release Notes Email Delivery</strong> — You can now build project mailing lists and send release notes directly to your subscribers, either manually from the content tab or automatically when a scheduled release notes email publishes. Recipients can unsubscribe via a one-click link included in every email, and re-adding an opted-out address will never resubscribe them.</li><li><strong>[New] Expanded MCP Agent Tools for Full Content Lifecycle Automation</strong> — MCP-connected agents can now manage the complete content lifecycle — polling generation status, retrieving and editing drafts, approving content, sending release emails, and publishing — in addition to the existing generation and read capabilities. Ready-to-install agent skills (announce-release, write-blog-post, email-your-users, and more) are available from the new Agents page in your dashboard.</li><li><strong>[New] Credit Metering System with Live Usage Dashboard</strong> — Generation credits are now actively metered and enforced: each content type consumes credits (long-form 100, social 25, weekly/ideas 50), and scheduled generations are skipped when your monthly allowance is exhausted. A credit meter in the sidebar and a detailed usage bar on the billing tab let you track usage and reset date at a glance, with contextual upgrade nudges as you approach your limit.</li><li><strong>[New] Public Mailing List API for Developer Integrations</strong> — Developers can now sync mailing list recipients programmatically via the new v1 API endpoints (GET /email/lists and POST /email/lists/{id}/recipients), authenticated with an API token scoped to your project. The API preserves all existing validation, deduplication, and unsubscribe semantics.</li><li><strong>[New] Sign In with GitHub</strong> — You can now sign in to your account using GitHub OAuth in addition to email and Google, with automatic account linking based on your verified GitHub email. The option appears on all auth pages and works seamlessly alongside existing login methods.</li><li><strong>[Improved] Actionable Empty States When No GitHub Source Is Connected</strong> — Instead of a generic error when no repos are tracked, the content generation UI now clearly distinguishes between a missing GitHub connection, no tracked repositories, and a genuine absence of commits — and offers a direct link to the Sources page to fix it. The schedule dialog's repo picker also shows an inline setup prompt when nothing is connected.</li><li><strong>[Improved] Mailing List Recipients Panel with Search and Status Filtering</strong> — The recipient list on the email destinations page now includes search and filtering by active or unsubscribed status, making it easier to manage large subscriber lists.</li><li><strong>[Fixed] Solo-to-Team Upgrade Flow Now Works End to End</strong> — The Team plan was effectively unpurchasable due to a database constraint rejecting the plan type, a missing subscription replacement step, and a payment error page that sent everyone back to a Solo checkout. All of these issues are resolved, and the account Plan tab now shows clear upgrade buttons for users without a discoverable upgrade path.</li><li><strong>[Fixed] Legacy Subscribers No Longer Lose Access on Renewal or Cancellation</strong> — Subscribers on pricing plans predating the current price IDs had their plan resolved as unknown, causing renewals to be skipped and cancellations to incorrectly strip access. Plan resolution now falls back to the Stripe product, so any pricing vintage on the same plan resolves correctly.</li><li><strong>[Fixed] Content Ideas Emails Now Render Correctly in Gmail</strong> — Idea descriptions in content ideas emails would render as broken text in Gmail due to unsupported HTML elements, and type icons appeared as empty tiles because Gmail strips inline SVGs. Descriptions are now truncated with a link to the full idea, and icons use text monograms that display reliably across all email clients.</li><li><strong>[Fixed] Changelog and Structured Content Previews No Longer Show Raw JSON</strong> — Generated changelogs and other structured content types occasionally rendered as raw JSON when the output was wrapped in a markdown code fence. The fence is now stripped at save time and on the frontend, so previews always display correctly regardless of how the content was originally saved.</li><li><strong>[Fixed] Unverified Login and Resend Verification Errors Now Show the Correct Message</strong> — Unverified users attempting to log in were shown a generic 'Invalid email or password' message instead of being prompted to verify their email. Users who had already verified their account saw a generic error on the resend page instead of being directed to log in. Both error messages now display correctly.</li></ul>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What's New — Jul 3–10, 2026]]></title>
            <link>https://shipstar.ai/changelog/fW41KbTf8BYG</link>
            <guid isPermaLink="false">https://shipstar.ai/changelog/fW41KbTf8BYG</guid>
            <pubDate>Fri, 10 Jul 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[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.]]></description>
            <content:encoded><![CDATA[<ul><li><strong>[Fixed] Users no longer get logged out during backend deploys</strong> — A deploy-time 502 error was incorrectly treated as an invalid session, signing out every active user whenever the backend restarted. Network errors and server-side failures now fail gracefully, keeping your session intact until a definitive authentication rejection occurs.</li><li><strong>[Fixed] Scheduled content generation now runs reliably without getting stuck</strong> — A workflow engine constraint caused every scheduled generation tick to crash silently, leaving drafts permanently stuck in a generating or pending state. Drafts stranded by past failures are also automatically recovered and re-queued.</li><li><strong>[Fixed] Concurrent content generation no longer hits rate limits and fails</strong> — When multiple drafts were due at the same time, all generation requests fired simultaneously and exceeded concurrency limits, causing permanent failures. Generation is now queued with a concurrency cap and automatic retries with backoff, so drafts complete successfully even during bursts.</li><li><strong>[Fixed] Workflow checkpoints now persist across deploys</strong> — The background job system was silently falling back to a temporary database that gets wiped on every deploy, losing all workflow state and progress. Checkpoints are now stored in the persistent database, so in-flight jobs survive deployments.</li><li><strong>[Improved] Email notifications are easier to read across all clients and devices</strong> — Email templates have been redesigned with a light theme and improved typography — including better monospace font rendering on Apple, Windows, and Android mail clients — so code snippets and structured content are sharp and legible at any size. Contrast levels have been raised across all text tiers to meet accessibility standards, including on Gmail iOS where dark-mode handling previously washed out text.</li><li><strong>[Improved] Dashboard secondary text and muted labels are more legible</strong> — Muted and secondary text throughout the dashboard was failing WCAG AA contrast requirements on card and page backgrounds, making labels and supporting copy hard to read. Text tiers have been brightened to meet accessibility standards across dark mode.</li></ul>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What's New — May 25 – Jun 1, 2026]]></title>
            <link>https://shipstar.ai/changelog/3u7mQRFSYDri</link>
            <guid isPermaLink="false">https://shipstar.ai/changelog/3u7mQRFSYDri</guid>
            <pubDate>Mon, 01 Jun 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[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.]]></description>
            <content:encoded><![CDATA[<ul><li><strong>[New] Publish Now directly from the calendar editor</strong> — A new Publish Now option in the calendar editor's toolbar lets you immediately publish any scheduled content without leaving the editor. The action menu has also moved into the toolbar for a more consistent experience across all content editors.</li><li><strong>[New] Status badges and sort controls in the timeline</strong> — Each item in the timeline list now displays a colored Published, Scheduled, or Draft status badge so you can see content state at a glance. A new sort dropdown lets you order items by newest, oldest, or last updated.</li><li><strong>[Improved] Intercom sync scheduling is now fully configurable</strong> — The Intercom article sync no longer runs on a fixed daily schedule — it now uses the same calendar event scheduling system as all other content types, so you can configure the frequency and timing per project.</li><li><strong>[Improved] Calendar event status stays in sync with published content</strong> — When you publish or unpublish content, the associated calendar event status now automatically updates to reflect the current state, keeping your content calendar accurate without any manual adjustments.</li><li><strong>[Fixed] Incomplete Intercom sync entries no longer appear in the timeline</strong> — Sync runs with no relevant activity were previously saving raw data as timeline entries, creating noise in your content history. These empty entries are now skipped, and existing ones have been cleaned up.</li></ul>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What's New — May 22–29, 2026]]></title>
            <link>https://shipstar.ai/changelog/4Ermp-IrQS54</link>
            <guid isPermaLink="false">https://shipstar.ai/changelog/4Ermp-IrQS54</guid>
            <pubDate>Fri, 29 May 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[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.]]></description>
            <content:encoded><![CDATA[<ul><li><strong>[New] Drag and drop calendar events to reschedule</strong> — You can now drag events to new time slots in day and week views, or to different day cells in month view, to reschedule them instantly. Only future events are draggable, and recurring events can be shifted to a different hour within the same day while date changes are safely blocked.</li><li><strong>[New] Content preview in Slack review notifications</strong> — Slack review notifications now include the first paragraph of generated content as an inline preview, so reviewers can read the copy at a glance before deciding to approve or reject without leaving Slack.</li><li><strong>[New] Unified blog post type with flexible options</strong> — Blog posts now support configurable length (short or long), SEO mode, and focus (multi-feature or single-feature) in one place, replacing the separate Feature of the Week content type. Existing content has been migrated automatically with no action required.</li><li><strong>[New] Status filter on Timeline and Calendar views</strong> — You can now filter scheduled content by status — Published, Scheduled, or Draft — directly in the Timeline and Calendar views, making it easier to focus on what needs attention.</li><li><strong>[Improved] Blog posts now use your ICP and audience context</strong> — When your project has an Ideal Customer Profile configured, blog post generation now uses that context — including company description, products, and customer pain points — to tailor content to your audience rather than making generic assumptions.</li><li><strong>[Improved] Improved navigation with Solutions and Resources dropdowns</strong> — The top navigation now features hover-activated Solutions and Resources dropdowns, giving quick access to use cases, industries, blog, changelog, knowledge base, and documentation from anywhere on the site.</li><li><strong>[Fixed] Recurring events no longer land on the wrong day</strong> — Recurring calendar events were sometimes appearing a day early or late for users outside UTC because recurrence rules were being expanded in UTC instead of the user's local timezone. This is now resolved — events land on the correct day regardless of your timezone.</li><li><strong>[Fixed] Calendar context menus no longer clip at screen edges</strong> — Right-click menus on calendar events and day cells were getting cut off when triggered near the edges of the browser window. Menus now reposition automatically to stay fully visible.</li></ul>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What's New — Apr 19–26, 2026]]></title>
            <link>https://shipstar.ai/changelog/-WxCiCFAoiRT</link>
            <guid isPermaLink="false">https://shipstar.ai/changelog/-WxCiCFAoiRT</guid>
            <pubDate>Sun, 26 Apr 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[Major publishing workflow overhaul, a redesigned changelog list view, and a new weekly calendar — plus 40 new pages added to the marketing site.]]></description>
            <content:encoded><![CDATA[<ul><li><strong>[New] Weekly Calendar View with Time Grid</strong> — The calendar now defaults to a weekly view with a Google Calendar-style hour grid, positioned events, and auto-scroll to 7 AM. Switch between Week and Month views anytime using the new toggle.</li><li><strong>[New] All Changelogs Now Displayed in a Scrollable List</strong> — Changelogs are now stacked vertically with the newest at the top, replacing the previous one-at-a-time view with a separate drafts dialog. Shared controls for scheduling, the published URL, RSS feed, and embed options live in a top bar, while per-card menus let you publish, unpublish, edit, copy, regenerate, or delete each entry.</li><li><strong>[New] Separate Pages for External and Internal Content</strong> — Content is now organized into two dedicated pages — External and Internal — each accessible from the sidebar. This makes it easier to manage and navigate content intended for different audiences without them being mixed together.</li><li><strong>[New] 40 New Marketing Pages Added</strong> — The marketing site now includes dedicated pages for features, use cases, integrations, and industries — covering topics like changelogs, release notes, GitHub, Slack, SaaS, fintech, and more. All pages are cross-linked and included in the sitemap.</li><li><strong>[Improved] Simplified, Unified Publishing Dialog</strong> — The publishing flow has been redesigned into a single streamlined layout — Publish Now is always visible at the top, followed by a One-time or Recurring schedule toggle with shared date and time fields. This eliminates duplicate pickers and reduces the clicks needed to configure or change your publishing schedule.</li><li><strong>[Improved] Schedule Changes Now Save Only When You Click Save</strong> — Adjusting scheduling fields no longer auto-saves immediately — all changes are batched and applied only when you explicitly click Save. This prevents accidental saves when browsing schedule options and gives you full control over when changes take effect.</li><li><strong>[Improved] Unpublished Badge on Changelog Cards</strong> — Changelog cards that haven't been published yet now display a clear Unpublished badge. Clicking the badge opens the publish dialog directly, making it faster to act on drafts.</li><li><strong>[Fixed] Marketing Site Assets Now Properly Indexed by Search Engines</strong> — A misconfiguration in robots.txt was blocking search engines from accessing the site's page assets, preventing pages from rendering and being indexed correctly. This has been resolved so the full site is now crawlable.</li></ul>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What's New — Mar 13–20, 2026]]></title>
            <link>https://shipstar.ai/changelog/KcrrRmVPTlBB</link>
            <guid isPermaLink="false">https://shipstar.ai/changelog/KcrrRmVPTlBB</guid>
            <pubDate>Fri, 20 Mar 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[Introducing the Content Calendar, a unified Drafts hub, and public Changelog publishing — your entire content workflow now lives in one place.]]></description>
            <content:encoded><![CDATA[<ul><li><strong>[Improved] Content Calendar with Scheduling and Recurring Events</strong> — A new monthly calendar view lets you schedule content by type, source, and frequency — including recurring events built on standard recurrence rules. Click any event to open a side panel where you can view and generate content inline, and right-click to edit or delete individual occurrences, future events, or entire series.</li><li><strong>[New] Public Changelog Publishing with RSS Support</strong> — You can now publish changelogs to a unique public URL with a single click, making them instantly accessible to anyone without logging in. Published changelogs are also available as RSS feeds, and the marketing site changelog page now pulls live data automatically.</li><li><strong>[New] GitHub Sources Integration</strong> — Connect your GitHub account, select repositories to track, and view a rolling 7-day commit feed directly in the app. Tracked repos become the source for automated content generation across all content types.</li><li><strong>[New] Unified Drafts Page for All Content Types</strong> — A new Drafts page consolidates all your generated content — blog posts, LinkedIn posts, X/Twitter threads, changelogs, release notes emails, and more — into a single view with Internal and External tabs. Each tab includes a chronological All view plus individual content type sub-tabs.</li><li><strong>[New] Public Changelog and Release Notes Email as New Content Types</strong> — Public changelogs and release notes emails are now fully supported content types with their own generation, preview, draft history, and copy controls. Both appear alongside your other content in the Drafts page and calendar.</li><li><strong>[Improved] Cleaner Content Previews with Publishable-Only Copy</strong> — All content tabs now wrap publishable output in a distinct Preview container so you can clearly see exactly what will be published versus supporting metadata. Copy buttons only capture the publishable portion, and auto-generated type headings are stripped from the output.</li><li><strong>[Improved] Consistent Regenerate, Copy, and Delete Controls Across All Content Cards</strong> — Every content card — in both the content pages and the Drafts list — now has inline Regenerate and Copy outline buttons, plus a delete button, for a consistent and predictable experience. Loading states use inline button spinners instead of full-card overlays to reduce visual disruption.</li><li><strong>[Fixed] Schedule Edits Now Preserve Series Start Dates and Respect Frequency Changes</strong> — Editing a recurring schedule no longer shifts the original series start date — only the time is updated. Stale recurrence end values are also cleared automatically so frequency changes take full effect.</li></ul>]]></content:encoded>
        </item>
    </channel>
</rss>