Record of notable changes published with each release. Options covered in the talk: a `CHANGELOG.md` file committed to the repository, Confluence pages, custom documentation sites, or GitHub Releases attached to git tags (Adrian's preferred choice). Keeping a changelog avoids the 'why did this break?' problem when users update the package.