Release Notes
Release notes are organized by product, not by repository (REL-DOC-01) — so they stay stable when repositories split. Release ownership follows product ownership (REL-DOC-03): an SCM release is a Commerce Chain release, a Loop Engine runtime release is a Boss Loops release, a Registry release is a Commerce Gateway release, and a Signal Tags release is a Tagd release.
Release notes summarize customer-visible change (REL-DOC-02). Commits, PRs, and internal refactoring are implementation artifacts and live in engineering systems, not here.
Each release entry uses a consistent structure so customers can scan changes quickly:
| Field | What it covers | | ----- | -------------- | | Release summary | One-line description of the release and its date | | What's new | Customer-visible features and improvements | | Breaking changes | Changes that require customer action | | Migration notes | Steps to adopt the release safely | | Developer notes | API/SDK-relevant changes (links to API Reference) | | Related documentation | Links to the product capability docs affected |
Historical entries may not fill every field; new entries should.