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