Changelog
Where release notes live, and how a change gets into them.
Every release of @crisp-ui-kit/crisp is written up in CHANGELOG.md, newest first, under a heading per version. It is the source of truth for what changed, why, and what you have to do when you upgrade. Until 1.0 the minor version carries breaking changes and the patch version does not.
The latest published version is on npm. Each component page says which version it first appeared in ("Available since").
Unreleased changes
Nobody edits CHANGELOG.md between releases. A change a consumer can see (a new component or prop, a changed default, changed behaviour or emitted CSS, a fixed bug) adds a small fragment under changes/ in the same pull request. At release time those fragments are folded into a new version heading and deleted. To see what is coming in the next release, read the fragments in that folder.
Reporting a docs gap
Docs live in the docs/ app of the same repository, and their props tables are generated from the component types, so a prop that exists in code appears in its table without a docs change. What can be missing is the guidance and the live example. File an issue on carrot-systems/crisp naming the page.