Skip to content

Changelog

Every release is recorded in CHANGELOG.md, at the root of the repository. It is generated from a single source file rather than written by hand, and a CI gate fails if the two disagree — so it cannot quietly fall behind what shipped:

CHANGELOG.md

Pre-1.0 a breaking change takes the minor (how versions move), and those are indexed at the top of that file — one line each with the version it landed in, so "does this upgrade break me" is a short list rather than a read:

Breaking changes

The same notes are published as GitHub Releases, one per version tag, where each release also links its artifacts — the PyPI wheel, the lat CLI binaries and the npm packages.