Read the current sources with channel context
The Gradle release notes identify the current Gradle release. The AGP 9.4 reference lists Gradle 9.6.0 and JDK 17 as its minimum/default compatibility entries, with maximum API support of 37.
That AGP page also contains alpha-labelled change sections. Verify the actual artifact and release channel offered for your project rather than assuming every prominent release-note heading is a production-stable recommendation.
Separate the three version questions
| Question | Evidence |
|---|---|
| What is newly documented or released? | Official release notes and artifact channel |
| What does this AGP version require? | Its compatibility table |
| What does my project actually run? | Wrapper and JVM output plus plugin declaration |
Android Studio's version is another separate component. Its compatibility table describes supported AGP ranges, not a command to upgrade every existing project immediately.
Inspect the local project
./gradlew --version
Then inspect the AGP plugin declaration in the root build script or version catalog. The command reports Gradle and its JVM; it does not replace reading the Android plugin version.
If CI and the IDE disagree, compare the wrapper path, Java environment and included builds before changing versions.
Choose a tested combination
Start from the AGP version needed for your compile SDK and plugin ecosystem, then select its supported Gradle and JDK combination. Test release packaging, lint, shrinking, native builds and third-party plugins before promotion.
Do not treat “newer than the minimum” as proof that every combination has been validated for your project.
Keep the article date meaningful
Version information is a dated snapshot. APKLint's Build Analyzer can review your declarations, but it is not a live dependency resolver and cannot establish the newest available artifact in a private repository. Recheck the official sources when making a future upgrade.
Turn a latest-version search into a recorded choice
At this guide's 29 September 2026 review, the linked Android page is headed AGP 9.4.0 and contains alpha-labelled entries. Its compatibility table states Gradle 9.6.0 and JDK 17. Treat those as the documented requirements for that AGP page, not as proof that a particular release artifact is stable or appropriate for your repository. The version-specific release notes preserve the context better than an unqualified “latest” link.
Write the selected full plugin version, including any preview suffix, in an upgrade record. Separately record the wrapper distribution and the JVM that actually ran the build. A release-channel decision should be explicit: a preview can be useful for compatibility experiments, while promotion into an existing release pipeline needs its own validation. Do not silently remove a suffix when copying a version from documentation.
Build a small project-specific compatibility matrix
List the project's Android plugin, Gradle, runtime JDK, Kotlin setup, code processors and any native or framework plugins. For each proposed change, identify which component's documentation establishes compatibility. A minimum Gradle version says where one requirement starts; it does not establish that every future Gradle distribution works with every installed plugin. The Gradle compatibility reference adds the runtime side of the matrix.
Test the candidate in a branch using the actual release task, not just a new empty sample project. Include shrinking, signing configuration validation, generated sources and any dynamic feature or native packaging that the application uses. Compare the resulting package identity, minimum and target SDK, native libraries and expected resources with the baseline artifact.
If the project cannot adopt the newest documented combination, record the blocking plugin or migration requirement and the supported current tuple. That is more useful than repeatedly updating a headline without changing the build. Recheck the official release channel and requirements when the upgrade is performed later; this article's review date identifies when its snapshot was verified and does not promise that version listings remain unchanged.
Sources and further reading
- Android Developers: Current Android Gradle plugin release notes
- Gradle: Gradle Wrapper
- Android Developers: Java versions in Android builds
- Gradle current release notes
- Android Gradle Plugin 9.4 compatibility reference
- Android Studio stable releases and toolchain compatibility
Reference review: 29 September 2026. Examples illustrate the workflow; check your installed versions, release artifact and account-specific Console requirements before applying them. This guide is not a claim that APKLint executed your project or verified your private account.
Android inspection tools and practical release guides. About APKLint · Report a correction
