-
-
Notifications
You must be signed in to change notification settings - Fork 21.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update Android dependencies for the project #87346
Update Android dependencies for the project #87346
Conversation
I think this is an important update for the future, thanks! |
- Update Android gradle plugin version from 7.2.1 to 8.2.0 - Update gradle version from 7.4.2 to 8.2 - Update target SDK from 33 to 34 - Update build tools version from 33.0.2 to 34.0.0 - Update kotlin version from 1.7.0 to 1.9.20 - Update Android fragment version from 1.3.6 to 1.6.2 - Update AndroidX window version from 1.0.0 to 1.2.0
9d6c5d6
to
e04a387
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Didn't test, but changes look good. Should be good to go for our next dev snapshot.
Thanks! |
Will there be separate PR for 4.2 or will this be merged to 4.2 branch? |
@YuriSizov @akien-mga We may consider cherry-picking this for 4.2.3 if it doesn't introduce any issues in the next 4.3 dev snapshot. |
Cherry-picked for 4.2.2. |
Can you update the documentary for the correct versions also? |
Time of the year for another broad Android dependencies update!
There have been quite a few deprecation and api updates in the gradle buildsystem so this PR updates the gradle build logic where needed to comply.
I've done my best to validate that no regressions were introduced, but I'd appreciate additional testing for thoroughness.
Fixes #87072 for the
master
branch; need to evaluate if this is safe to backport to 3.xNotes:
android.enableResourceOptimizations
was pushed to AGP version 9+. I have a few ideas for how to deal with this when it's fully deprecated but this will require follow-up discussions.