Target Android 16 (API 36) - #351
Merged
Merged
Conversation
Code Coverage
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
compileSdkandtargetSdkto 36 and preparing version 5.6.0 (46)Validation
./gradlew --no-daemon ktlintCheck koverXmlReportDebug lintRelease bundleReleaselintReleasecompleted with 0 errorsbundleReleasecompleted with R8Scope
This intentionally does not add
play/fossflavors or replace the current UMP implementation. Those remain follow-up steps after establishing the common target SDK 36 baseline.Defining filtered JVM coverage targets and separate instrumentation coverage remains a follow-up task.
The local release build used non-secret test ad placeholders and produced an unsigned AAB. Before a Play upload, verify the real ad configuration, release signing, version code availability, and Play pre-launch results.