design system governance
The rules and processes for how a design system changes: who can contribute, how releases are versioned and how old APIs are retired.
In more detail
Product teams depend on the system, so unexpected breakage erodes trust and teams stop upgrading. Governance keeps changes predictable through semantic versioning, changelogs, deprecation periods and migration tools.
Related terms
- semantic versioning — A version numbering scheme of three numbers, major.minor.patch, raised for breaking changes, new features and fixes respectively.
- Changesets — A tool where each pull request adds a small Markdown file describing its change and its version bump, later combined into releases and changelogs.
- deprecation — Marking a feature as outdated and scheduled for removal, while it still works, so users have time to move to its replacement.
- codemod — A script that rewrites source code automatically, for example renaming a deprecated prop across a whole codebase.
Taught in
- System Governance: Changesets, Semantic Versioning & Deprecation — Design Systems & Component Engineering