// every release that moved a packet through the gate faster. Newest first.
Every entry is a change that reached production and that a caller could notice — a new endpoint, an altered default, a fix to something that was returning the wrong answer. Internal refactors and infrastructure work do not appear unless they changed behaviour you can observe.
Releases are numbered by the day they shipped, because this is continuously delivered and a semantic version would imply a release cadence that does not exist. A version here tells you when, not how big.
new is capability that did not exist, improved is something that already worked doing so better, fixed is something that was wrong, and security is anything touching keys, authentication or isolation.
The API is versioned in its path. Anything that would break an existing integration gets a new version rather than an entry here, so a release on this page is safe to ignore if what you have is working.
The RSS feed carries the same entries. For whether the service is up right now rather than what changed, the status page is the one to watch.