Turn GitHub releases into a changelog your customers actually read.
You already write release notes on GitHub. Release Changelog syncs them into structured WordPress entries you can review, enrich, and publish on your schedule—then renders an accessible public changelog with dynamic blocks and editable templates.
Release pages printed their notes twice: once in the Release Source Notes
block and again in a Release Changes block that sync filled with a copy of
the same notes, with **bold** markdown left raw. Sync no longer writes the
copy, and updating removes copies nobody edited from existing releases.
Edited copies are kept.
Changed
With a file-based extraction source, release notes come from the
release’s section of that file (for example CHANGELOG.md) instead of the
GitHub release body: in the Release Source Notes block, timeline and card
excerpts, the change list, the Rank Math description, and “Copy
synchronized notes into editor”. Previously those notes appeared only in
the copy. A sync that arrives without the file keeps the stored section.
One release library. Every product gets its own view.
Publish each release once, keep one combined company archive, and give customers a focused changelog for the product they use.
Combined archive
Everything shipped, in one chronology
The main archive combines every mapped product. Code Atlantic currently publishes Release Changelog here, and the same archive is ready to grow with the rest of the catalog.
Set the product filter and the archive becomes a shareable, product-specific feed. This link uses the real Release Changelog mapping—no copied posts and no second source of truth.
Timeline and filter blocks can be limited to allowed product slugs. Add a repository mapping and that product becomes available to the same controls and reusable layouts.
Launch a working sandbox to inspect the protected-draft workflow, or browse Popup Maker’s public archive of more than 100 dated releases to see the finished customer experience.
