enforcing-stability-in-ci

To block Jetpack Compose stability regressions in CI, apply the compose-stability-analyzer Gradle plugin to your UI modules and wire the stabilityCheck task into your CI pipeline to fail builds on regression.

You generate a stability baseline by running the stabilityDump task for your module, which produces .stability files that you commit to version control to track baseline drift.

For multiplatform projects, the compose-stability-analyzer offers ComposeGuard as an alternative flow to enforce CI-grade stability and detect regressions across multiple modules.

Committing .stability files to version control is required because it establishes the baseline for stability validation, allowing the stabilityCheck CI gate to detect and fail on regressions accurately.

You configure stabilityValidation by applying the stability analyzer plugin in every UI module, ensuring the CI pipeline can enforce stability checks across the entire Android Jetpack Compose project.

The best way to integrate stabilityCheck into GitHub Actions is to wire the Gradle task into your CI pipeline after committing the .stability baselines, failing the build when regressions are detected.