Interview frequency: …
Short answer
Use semantic versioning (Major.Minor.Patch): Major indicates breaking changes that may break product screens, Minor indicates backward-compatible features, and Patch indicates small visual fixes.
Explanation
Renaming a property, removing a core component option, or changing a container's structural behavior is a breaking change (Major Release). It requires advance notice and a Migration Guide for product teams. A deprecation period lets teams schedule interface updates without disruption and prevents working production screens from breaking.
Common mistakes
- Publishing breaking changes to a shared Figma library without coordinating with developers, creating a gap between design and code.
- Changing the size or margins of a component used in thousands of screens without studying the effect on existing page layouts.