So KSP and Jetbrains Compose already support 1.9.20. Any timeline on Jetpack Compose?

# compose

[eygraber]

So KSP and Jetbrains Compose already support 1.9.20. Any timeline on Jetpack Compose?

[Kirill Grouchnikov]

Jetbrains Compose supports rc02, not the final release

[Kirill Grouchnikov]

And 1.9.20 isn’t official yet

[eygraber]

Jetbrains compiler 1.5.3 was released that supports 1.9.20

[jw]

It's hard to get more official than the artifacts landing in Maven Central which is immutable. It just hasn't been announced, but that doesn't make it any less usable.

[hfhbd]

The 1.5.3 compiler supports 1.9.20 and is used by the 1.5.10 gradle plugin, which is already released at maven central.

[eygraber]

The 1.5.3 compiler that supports 1.9.20 is from Jetbrains. I was asking about the Jetpack Compose compiler

[jw]

Google haven't even merged 1.9.20 yet because of the monorepo of sadness. If we're extremely lucky we'll see a release in a few days. If things are normal, it'll be a week, or two.

[eygraber]

Maybe someone at Google wants to reopen Move development of Compose out of AndroidX?

Marking with a Won't fix, not that we will not fix this in the future, but, rather, no other resolution seemed appropriate either.

[Jan Skrasek]

How does it work that JetBrains' compiler is merged/released and the Android's not? Do both teams make similar changes? Or is Android's version waiting on something and in the meantime, JetBrains reused that and published it?

[jw]

The changes needed are known weeks in advance as AndroidX engineers track the preview releases of future versions of Kotlin. There's even preview releases from the Android team, just not on Google Maven. As a result, JetBrains can land the required changes into their fork immediately upon Kotlin's release and release the Compose compiler. They can do this because they're not burdened by having to deal with hundreds of unrelated projects in their fork and they presumably have a more straightforward release process than the crazy one Google dreamed up for AndroidX.

[Jan Skrasek]

Yes, thanks. My main question is though - is JetBrains copying over CLs from Google? Or do they do the update on their own?

[jw]

I haven't checked. I would have a hard time believing they do anything but copy since ultimately they have to reconcile the two repos' contents.

[Oliver.O]

It happens in the compose-multiplatform-core repo: https://github.com/JetBrains/compose-multiplatform-core/commit/24cad2e680c5b7bf49ef22c10d49b2bf4979857b

[Piotr Prus]

I have tested briefly kotlin 1.9.20 and compose compiler 1.5.4-dev. It works:
https://androidx.dev/storage/compose-compiler/repository

[eygraber]

I'm sure it works, but that's not the same as a real release. I have multiple libraries that use Compose and this happens every time there's a new Kotlin release. Everyone in the ecosystem is ready except Google with Compose and it causes a backlog of PRs. I don't think it's acceptable to switch to the dev version until they get the monorepo together.