What problem does it solve?
It ensures every user-visible change to Plate registry UI components, kits, examples, and registry metadata is documented with a consistent, machine-generated changelog entry instead of ad-hoc or missing release notes.
Core Features & Use Cases
- MDX Entry Authoring: Defines a strict frontmatter contract (id, date, status, kind, summary, change, release, diagnostics) for changelog source files under apps/www/src/registry/changelog/entries.
- Generator Workflow: Provides commands to create new entries, regenerate public JSON artifacts, and verify source and generated output agree.
- Scope Classification: Distinguishes registry changelog entries from package changesets and defines when an entry is required versus N/A.
- Use Case: After modifying a registry UI component like the editor renderer, create a dated MDX entry, run the generator with --write, and confirm --check passes before handoff.
Quick Start
Create a registry changelog entry for my changes to the editor component, regenerate the public JSON, and verify the output passes the check.