Release notes

Kerf release notes will live with the project’s GitHub releases so users can tie product changes to tags, commits, and deployment artifacts.

GitHub releases

For launch, use the repository’s GitHub Releases page as the canonical release-note feed. This docs page is a stable in-app pointer until a richer changelog feed is wired into the docs site.

What to expect

Release notes should call out modelling changes, import/export compatibility, AI-agent workflow changes, known migration notes, and any actions users should take after an update.

For end users, the most important notes are compatibility notes: whether a document created on a newer build can still be opened on an older build, whether a format exporter changed output, and whether AI-agent behaviour changed enough to affect review habits. For teams, release notes should also identify rollout risks such as auth, storage, or organization-model changes.

Until the release feed is embedded here, link users to the tagged GitHub release that matches the deployed build SHA shown in diagnostics or support bundles.