Android Studio Gradle Wrapper Upgrade Prompt Persistence Limits

The goal is to keep the Gradle Wrapper version consistent for all developers and CI systems after the Android Gradle Plugin version is changed in a project.

Android Studio records the wrapper upgrade suggestion in the .idea/workspace.xml file, which is normally excluded from version control. Consequently, the decision to accept or defer the upgrade is not persisted when the project is reopened, cloned, or used in a fresh CI environment, causing the prompt to reappear and potentially leading to divergent Gradle versions.

It remains unclear whether the IDE offers a way to persist the wrapper upgrade choice outside the workspace file or to suppress the automatic prompt while still respecting a committed wrapper version.

Can the wrapper upgrade decision be stored in a version‑controlled location such as the Gradle Wrapper properties file itself? Is there a setting to disable the automatic wrapper upgrade prompt without losing compatibility checks? How can teams enforce a specific Gradle version reliably without relying on the IDE’s transient prompt?