The Pro API is no longer read-only. You can now create entries, edit them, and publish them with your API token, including scheduling by passing a future publish date. Entries created this way are tagged as coming from the API so you can tell them apart from hand-written ones. Publishing an entry that is already live keeps its original date, so nothing reshuffles for readers.
Patchlog now offers an MCP server, so your coding agent can list projects, read entries, and draft, update, and publish changelog entries for you. Run it locally with the patchlog-mcp package or connect to the hosted endpoint at https://patchlog.io/mcp using your API token as a bearer token. New entries default to drafts, so nothing goes public until you say so. Available on the Pro plan.
The GitHub setup page now offers a workflow built on our published action as the default, so there is nothing to maintain on your side when the payload changes. The snippet is prefilled with your project settings and only spells out the options that differ from the defaults, and it links out to the action's public repository. The original inline script is still available below if you would rather not depend on a third party step.
A new Drafts page gathers every unpublished update across all your projects in one place, split into what needs review and what is scheduled to go out. Drafts show how long they have been waiting and are flagged when they came from a GitHub push, and the sidebar carries a badge with the count still waiting on you.
A new option (off by default) adds a link in the widget footer so visitors can hide it. The widget reappears on its own as soon as you publish a new update, and turning the setting off brings it back for everyone. Your own trigger via window.patchlog.open() keeps working even while it is hidden.
The widget script was being cached at the CDN for up to four hours, so a published widget change could stay invisible on your site long after it shipped. The cache is now cleared automatically on every release. Returning visitors whose browsers already hold an older copy may still lag briefly.
The widget settings page now shows a real, interactive preview beside the controls. It renders with your actual published updates (or sample ones if you have not published yet) and redraws instantly as you change colors, position, size, text and other options, before you save.
A new read API lets you pull your projects and changelog entries into your own tools, for example a docs site or status page. List entries by status (published, draft or all), filter by type, and page through results. API access is a Pro feature.
Connect a repository and Patchlog turns your commits into draft changelog entries, one per user-facing change, ready for you to review, edit, and publish. Setup is a single workflow file you paste into your repo plus a token you store as an Actions secret. Available on Pro.
You can now control a bunch of new stuff like new positions, colors, icons, sizes and much more in the Patchlog widget!
And that's why we added URL Exclusions to the widget settings page where you can add URLs that the widget shouldn't show on.
A QA analyst with 7 years of experience has performed a full audit of Patchlog and we're currently working on adding & fixing his amazing findings.
We have released a new blog and we'll be writing tutorial posts about patchlogs as well as other topics in the upcoming future.
is what's cooking next on our to-do list. Stay Tuned!
You can expose a /rss endpoint which will make your changelogs appear in a RSS feed. No extra work needed! NEAAT!
We'll be using patchlog to let you know about what's new in patchlog using patchlog... got it?