validating-compose-stability

Prevent silent Jetpack Compose recomposition regressions by committing a .stability baseline generated by the Compose Stability Analyzer plugin and failing CI when stabilityCheck detects a composable has become less skippable or restartable.

A Compose stability baseline is a committed .stability file snapshot of composable skippability and restartability. The stabilityDump task generates it, and stabilityCheck compares compiled output against it to gate CI on parameter stability regressions.

Configure the plugin by applying the composeStabilityAnalyzer { stabilityValidation { … } } DSL in Gradle. Set failOnStabilityChange to true and ensure your pipeline runs a build task before executing stabilityCheck to validate compiled output against the baseline.

Exclude Jetpack Compose previews and scaffolding by annotating them with @IgnoreStabilityReport. This prevents the Compose Stability Analyzer from tracking their stability changes and triggering unwanted CI failures.

Handle non-regressive Compose stability changes by enabling ignoreNonRegressiveChanges in the stabilityValidation DSL. This allows the stabilityCheck task to pass when composables become more stable, while still failing CI on actual regressions.

You do not strictly need an existing baseline if you enable allowMissingBaseline in the validation DSL. However, bootstrapping a .stability file via stabilityDump and committing it to version control is required for continuous regression tracking.