Hot
Releases worth linking to.
A changelog with an address and a feed. Every release gets a permalink and appears in a dedicated feed, so people can follow the product without following the blog.
Changelogs usually live in a text file nobody reads or in blog posts that bury the release between announcements about conferences.
This gives every release its own address and its own feed. Support can link to the exact version that fixed a bug, and interested users can subscribe to releases alone.
Our users subscribe to releases and nothing else.
— A product manager
Releases with addresses.
Addressable releases
Every version gets a permalink, so a support reply can point at the exact release that changed something.
Release-only feed
A feed containing releases and nothing else, separate from the site feed.
Version comparison
A between-versions view listing everything that changed across a range of releases.
Breaking-change flags
Entries can be marked as breaking, which surfaces them separately and in the feed title.
The rest of the release record.
What a public changelog needs to be worth linking to from a support reply.
- Permalink per release
- Release-only feed
- Between-versions comparison view
- Breaking-change flags
- Semantic version sorting
- Release date and author fields
- Markdown accepted in entries
- Structured data for software releases
The details
- Version
- 1.1.0
- Released
- Oct 7, 2025
- Release URLs
- One per version
- Feed
- Releases only
- Sorting
- Semantic version
- Structured data
- SoftwareApplication
Recent releases
- 1.1.0Oct 2025 — Semantic version sorting replaced string ordering
- 1.0.0Aug 2025 — Breaking-change flag added to entries
MORE LIKE THIS
Related themes
New
Featured
