Impartial Versioning of Jetpack Compose Libraries

Message from Jolanda VerhoefAndroid Developer Relations Engineer

From at this time numerous Jetpack Compose Libraries Will Transfer to Impartial Model Management Schemes. This creates a chance for subgroups resembling androidx.compose.compiler or androidx.compose.animation observe their very own launch cycles.

In case you permit impartial versioning of those libraries, separate dependencies which had been beforehand implicitly linked, making it simpler to incrementally replace the app and due to this fact keep updated with the newest Compose options.

The primary library to separate from the one model of Compose is the Compose Compiler. Immediately we’re releasing 1.2.0 steady model what brings Kotlin 1.7.0 assist! Launch is each forwards and backwards compatibility with Compose UI libraries and Compose Runtime library. This implies you can improve your Compose compiler to steady model 1.2.0 and use Kotlin 1.7.0 whereas maintaining the present model of different Compose libraries, resembling steady 1.1.0.

To replace the model of the Compose compiler in your software, specify in kotlinCompilerExtensionVersion in your construct.gradle file.

android {
    composeOptions {
        kotlinCompilerExtensionVersion = "1.2.0"

Compose and Kotlin are intently associated, and we have heard your suggestions that updates to the Compose compiler are wanted so as to replace your model of Kotlin. We wish to be certain you should use the newest and biggest options (and bug fixes) from each Compose and Kotlin, which is why we plan to launch steady variations of the Compose compiler far more continuously. Which means that Compose compiler model numbers will change sooner than most different Compose libraries. For the reason that Compose compiler is each ahead and backward suitable, it is possible for you to to replace it as quickly as a brand new model is launched.

The Compose compiler is constructed as a plugin for the Kotlin compiler, so you have to use a model of the Compose compiler that’s suitable with the Kotlin model of your alternative. That can assist you choose the suitable model in your challenge, please see Compose-Kotlin Compatibility Map.

Transferring a compiler library to a distinct versioning scheme is step one in separating versioning for various teams of Compose libraries. You will see new steady releases for different Compose libraries within the subsequent few weeks, after which they will begin following their very own launch cycles impartial of the Compose compiler.

Put together your construct for particular person versioning and begin utilizing the newest model. Compile Compiler in addition to Kotlin variations now!

We sit up for seeing what you create with Compose!

The Information Weblog The place You Get The Information First
Android Builders Weblog
#Impartial #Versioning #Jetpack #Compose #Libraries