Traceary

Traceary changelog

A site that keeps other people’s release notes should keep its own. This page is built from the same components as every product page in the archive, so it is also the shortest description of what those pages do.

0.x1 release

0.1.0

First working version

  • Collects release notes for 36 developer, infrastructure and AI products through the GitHub Releases API and public RSS or Atom changelogs. Nothing is scraped and no browser is driven.
  • Every release with notes gets its own page and its own address, 1,991 of them at this version, plus a per product RSS feed and a feed covering everything.
  • Conditional requests mean a source that has published nothing costs one 304 response, and a day on which nothing changed produces no commit, no build and no deployment.
  • Tags are split into the package they belong to and the version, so Astro shows 7.2.7 rather than astro@7.2.7 and PostHog shows desktop 0.61.35 rather than an unlabelled 0.61.35.
  • Version history bands by major release line rather than by publication order, which keeps products such as Node.js readable while they maintain several lines at once.
  • A copy guard runs before every build and rejects the writing patterns that mark machine written English. A layout guard checks the page gutter, rejects colours written outside the palette, and measures every text tone against its own background.
  • The build measures its own output against the 20,000 file ceiling Cloudflare Pages enforces, and fails before a deployment can be refused.
  • A status page reports the collection job, day by day, and names a source only when that source is failing. How current any one product is sits on that product’s own page, under its facts, next to the releases it affects.

Traceary follows semantic versioning, and the number that matters most is the one on the collected data. A change to the shape of a release address is a breaking change, because every link anyone has made to a version page depends on it.