How the archive is built
Traceary keeps the release notes of 36 products in one place. Every version gets its own page, its own address and its own entry in the feed, so a release from three years ago is as easy to link to as today’s.
Where the notes come from
There are two sources and nothing else. 32 products are read through the GitHub Releases API, using the tags their maintainers publish. The rest come from the RSS or Atom feed the vendor publishes on its own changelog page.
No page is scraped and no browser is driven. If a product stops publishing a machine readable changelog, it stops updating here, and the archive keeps what it already collected.
What happens to the text
Markdown is turned into HTML and the HTML is stripped down to text, links, lists, tables and code. Scripts, styles and images are removed. Headings are pushed one level down so they sit under the page title. The contributor roll that GitHub appends to generated notes is dropped, because on a large repository it can be longer than the notes themselves.
Notes longer than 40 kB are cut, and those pages say so and link to the publisher. Nothing is summarised, reworded or translated. The wording on a release page is the wording its author shipped.
About the labels
Labels like added or security are matched from words that appear in the notes. They are a reading aid, not a claim about the release. A release that changed an API without using the word breaking will not carry that label.
What is missing
Several products worth tracking publish a changelog for people to read but no feed for machines. Stripe, Linear, the Anthropic API docs and the OpenAI platform docs are the ones asked for most often. They are on the list and they stay off the site until a public feed exists or the vendor offers one.
Suggesting a product
A product qualifies when it has a public GitHub releases page or a public RSS or Atom changelog, and when its releases carry notes rather than bare tags. Send the feed address and the reason it belongs here to hello@traceary.com.
Rights
Release notes stay the property of the projects and companies that wrote them. Traceary stores them for reference and links back to the original on every page. Any publisher who wants an entry removed can write to the same address and it will be taken down.
Checking any of this
The status page records what the daily job managed to read, source by source, so the claim on this page can be checked rather than taken. Traceary’s own releases are on its changelog.