Aller au contenu principal

Sort Component Changes by Versioning Risk

Classify component changes as patch, minor, or major based on consumer impact.

design-systems4 min read

Place each design-system change in the versioning risk bucket that best matches consumer impact. Patch Minor Major Fix Dialog so focus returns to the opener after close Add a neutral Badge variant without changing existing variants Remove the deprecated Button emphasis prop from the public API Correct a typo in Tooltip usage documentation Add optional onDismiss callback to Toast while preserving existing behavior Change Card default padding from 16 to 24 across all consumers Maintainer effort How hard it was Consumer risk What can break

Read the full lesson

Sign up free: one personalized lesson every day, matched to your role and goals.

← Back to library

Nous contacter