This message was deleted.

You don't say that updating Gradle changes the Kotlin version of you production project, do you? That is changes teh Kotlin version of build logic code could quite well be, as Gradle defines the Kotlin version that is used at runtime.

Exactly this happens, the kotlin-stdlib dependency is bumped to 1.8.10 as well. I wouldn’t have noticed that if not for the Compose compiler plugin that said that I’m using Kotlin 1.8.10, while I only whitelisted the usage of Kotlin 1.7.21 via the Kotlin compiler flag

plugin:androidx.compose.compiler.plugins.kotlin:suppressKotlinVersionCompatibilityCheck=1.7.21

I would also say it shouldn't happen, but hard to say for me without hands-on.

Anything I could do to debug into this a little more?

Can you maybe look at a build scan, that could clear things more up than just

dependencies

and

dependencyInsight

. Actually debugging the dependency resolution is not the nicest experience as far as I remember.

I published a scan here: https://scans.gradle.com/s/t4uy5q2tcd4hi/dependencies?focusedDependency=WzEwLDE1LDYsW[…]EwLDE2LFs2NjFdXSxbMTAsMTYsWzY2MSw2ODZdXSxbMTAsMTUsWzk2MF1dXQ

Hm, so why do you have 1.8.10 in the release runtime classpath? Do you maybe there use

embeddedKotlinVersion

and thus get a different version by updating Gradle?

No, I don’t reference

embeddedKotlinVersion

anywhere myself.

But you do depend on

org.jetbrains.kotlin:kotlin-parcelize-runtime:1.8.10

and

org.jetbrains.kotlin:kotlin-stdlib:1.8.10

in

releasRuntimeClasspath

, right?