You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For example, for Android projects, the plugin should align Gradle & Android Gradle Plugin versions. We shouldn't offer the upgrade to a new Gradle major version if AGP is not supporting it yet.
AGP docs:
We are updating the version numbering for Android Gradle plugin (AGP) to more closely match the underlying Gradle build tool.
Here are the notable changes:
AGP will now use semantic versioning, and breaking changes will be targeted for major releases.
There will be one major version of AGP released per year, aligned with the Gradle major release.
The release after AGP 4.2 will be version 7.0 and will require an upgrade to Gradle version 7.x. Every major release of AGP will require a major version upgrade in the underlying Gradle tool.
APIs will be deprecated approximately one year in advance, with replacement functionality made available concurrently. Deprecated APIs will be removed approximately one year later during the subsequent major update.
The text was updated successfully, but these errors were encountered:
See if BOM can help with this.
For example, for Android projects, the plugin should align Gradle & Android Gradle Plugin versions. We shouldn't offer the upgrade to a new Gradle major version if AGP is not supporting it yet.
AGP docs:
The text was updated successfully, but these errors were encountered: