-
-
Notifications
You must be signed in to change notification settings - Fork 80
deps(deps): bump the kotlin group with 2 updates #1002
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -2,10 +2,10 @@ | |
| plugins { | ||
| id("com.android.application") version "9.1.0" apply false | ||
| id("com.android.library") version "9.1.0" apply false | ||
| id("org.jetbrains.kotlin.plugin.compose") version "2.3.21" apply false | ||
| id("org.jetbrains.kotlin.plugin.compose") version "2.4.0" apply false | ||
| id("com.google.dagger.hilt.android") version "2.59.2" apply false | ||
| id("com.google.devtools.ksp") version "2.3.6" apply false | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Prompt To Fix With AIThis is a comment left during a code review.
Path: build.gradle.kts
Line: 7
Comment:
**KSP version incompatible with Kotlin 2.4.0**
`com.google.devtools.ksp` is pinned at `2.3.6`, which targets an earlier Kotlin release. The official Kotlin documentation pairs Kotlin 2.4.0 with KSP `2.3.9`. Running KSP 2.3.6 against the 2.4.0 compiler plugins will cause a version-mismatch error at build time (KSP validates the Kotlin compiler version it was built against). This PR should also bump KSP to `2.3.9`.
How can I resolve this? If you propose a fix, please make it concise. |
||
| id("org.jetbrains.kotlin.plugin.serialization") version "2.3.21" apply false | ||
| id("org.jetbrains.kotlin.plugin.serialization") version "2.4.0" apply false | ||
| id("io.sentry.android.gradle") version "6.1.0" apply false | ||
| // Chaquopy — applied ONLY by :rns-backend-py (module-level, never at :app level) | ||
| // so the kotlinBackend flavor's classpath is never polluted with the Python | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The Kotlin 2.4.0 changelog (commit
ef14611) changes the default stability of non-final classes fromStabletoUnknown. Any non-final class used as a@Composableparameter that was previously treated as stable will now be treated as unstable, potentially triggering additional recompositions at runtime. Review Composable call sites that accept non-final types (e.g., interfaces, open classes) and add explicit@Stable/@Immutableannotations or ensure classes aredata class/finalwhere stability is required.Prompt To Fix With AI
Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!