:mega::compose-multiplatform: <https://github.com/JetBrains/compose-multiplatform/releases/tag/v1.6....

# compose

[Daria Voronina [JB]]

📣K Compose Multiplatform 1.6.1 is out!

This release brings compatibility with Kotlin 1.9.23 and addresses several bugs that affected the resource management library and the TextField component.

Check out the changelog for more details. kodee walking https://kotl.in/compose-1.6.1-slack

[Yan Pujante]

I am a bit confused. I created a multiplatform compose app a few days ago with the online wizard, and I see this in in the libs.versions.toml file:

[versions]
compose = "1.6.2"
compose-plugin = "1.6.0"
junit = "4.13.2"
kotlin = "1.9.22"

It looks like I am using 1.6.2 yet 1.6.1 just got released?

[Igor Demin]

How did you create it?

This is probably a Jetpack Compose version, not a Compose Multiplatform version. They have different versioning, but keep the first 2 numbers aligned.

[Igor Demin]

I see, https://kmp.jetbrains.com/ creates this. We will discuss this, how to avoid confusion.

[Igor Demin]

You should change versions this way:

[versions]
compose = "1.6.2"
compose-plugin = "1.6.1"
junit = "4.13.2"
kotlin = "1.9.22"

[Yan Pujante]

Yes I did use the wizard you mention. I suppose I can change kotlin to 1.9.23 as well. And yes it is very confusing that there is something called compose with a version and compose-plugin with another which somehow refers to the version of compose multiplaform

[Igor Demin]

Yes, you can. Thanks for bringing this. We'll look at it here

[Yan Pujante]

Thank you. The suggested rename in the ticket would indeed remove the confusion.

[Mofe Ejegi]

I noticed this with the dev releases but if anyone else having issues with using standard apis like forEach and only seeing fastForEach, you should try updating to Kotlin 1.9.23. That worked for me

[Michael Paus]

Wouldn’t it be a good idea to publish an updated libs.versions.toml together with the release notes of each release in order to avoid any confusion?