chore(deps): bump org.jetbrains.kotlin.jvm from 2.4.0 to 2.4.10

[dependabot]

Bumps org.jetbrains.kotlin.jvm from 2.4.0 to 2.4.10.

Release notes

Sourced from org.jetbrains.kotlin.jvm's releases.

Kotlin 2.4.10

Changelog

Backend. Wasm

• KT-87066 K/Wasm: Not all files are presented in compiler output directory with multimodule-closed-world and incremental compilation

Compiler

• KT-86939 JVM: IllegalStateException "No value for annotation parameter" when using const val in nested Java annotation array argument
• KT-83766 K2: Wrong sourcePsi is set for SymbolPsiLiteral in SLC for annotation arguments referencing a const val
• KT-86728 Reified type inference: expected type not propagated into inline call inside lambda with elvis operator

Compose Compiler

• b/522127447 Compose Compiler 2.4: classes previously inferred stable now reported runtime/Uncertain

Klibs

• KT-86501 Native: IrTypeAliasSymbolImpl is already bound. Signature: kotlinx.datetime/Instant|null[0] on iosSimulatorArm64

Tools. CLI

• KT-86930 Introduce kotlinr in the Kotlin distribution

Tools. Gradle. BCV

• KT-87223 Gradle, BCV: open version range in kotlinAbiValidationCompatClasspath causes kotlin-build-tools-impl to resolve to 2.4.20-Beta1 instead of 2.4.0

Tools. Gradle. JS

• KT-87304 jsBrowserTest fails with "exited with errors (exit code: 1)"
• KT-86057 kotlinUpgradeYarnLock skips lock file regeneration when kotlinNpmInstall is up-to-date, causing kotlinStoreYarnLock to fail

Tools. Gradle. Multiplatform

• KT-87084 False positive warning for JS and Wasm compilations when CRI is enabled

Tools. Scripts

• KT-87076 @file:CompilerOptions("-jvm-target", ...) ignored in .main.kts scripts in Kotlin 2.4.0, falling back to JVM target 1.8
• KT-86352 K2 scripting: FirResolvedTypeRef exception when resolving extension functions from imported scripts

Kotlin 2.4.10-RC2

Changelog

Backend. Wasm

• KT-87066 K/Wasm: Not all files are presented in compiler output directory with multimodule-closed-world and incremental compilation

... (truncated)

Changelog

Sourced from org.jetbrains.kotlin.jvm's changelog.

2.4.10

Backend. Wasm

• KT-87066 K/Wasm: Not all files are presented in compiler output directory with multimodule-closed-world and incremental compilation

Compiler

• KT-86939 JVM: IllegalStateException "No value for annotation parameter" when using const val in nested Java annotation array argument
• KT-83766 K2: Wrong sourcePsi is set for SymbolPsiLiteral in SLC for annotation arguments referencing a const val
• KT-86728 Reified type inference: expected type not propagated into inline call inside lambda with elvis operator

Compose Compiler

• b/522127447 Compose Compiler 2.4: classes previously inferred stable now reported runtime/Uncertain

Klibs

• KT-86501 Native: IrTypeAliasSymbolImpl is already bound. Signature: kotlinx.datetime/Instant|null[0] on iosSimulatorArm64

Tools. CLI

• KT-86930 Introduce kotlinr in the Kotlin distribution

Tools. Gradle. BCV

• KT-87223 Gradle, BCV: open version range in kotlinAbiValidationCompatClasspath causes kotlin-build-tools-impl to resolve to 2.4.20-Beta1 instead of 2.4.0

Tools. Gradle. JS

• KT-87304 jsBrowserTest fails with "exited with errors (exit code: 1)"
• KT-86057 kotlinUpgradeYarnLock skips lock file regeneration when kotlinNpmInstall is up-to-date, causing kotlinStoreYarnLock to fail

Tools. Gradle. Multiplatform

• KT-87084 False positive warning for JS and Wasm compilations when CRI is enabled

Tools. Scripts

• KT-87076 @file:CompilerOptions("-jvm-target", ...) ignored in .main.kts scripts in Kotlin 2.4.0, falling back to JVM target 1.8
• KT-86352 K2 scripting: FirResolvedTypeRef exception when resolving extension functions from imported scripts

Commits

• 5687445 Add Changelog for 2.4.10-RC2
• ba30392 [Wasm] Support regenerate unchanged modules flag on KGP
• 6307e73 [Wasm] Implement Xwasm-IC-generate-unchanged-modules flag
• 39d7aee Add ChangeLog for 2.4.10-RC2
• a2956be [Gradle] Update karma.conf.js to use 'require(...)' instead plain strings
• 9b1361c [Gradle] KT-87223: Updated regression test
• a4c153a [Gradle] KT-87223: Fix toochain to 2.4.0 for abiValidation compat config
• bc04b90 Add ChangeLog for 2.4.10-RC
• bbcb94b [CRI] explicitly disable CRI generation for non-JVM targets to avoid false-po...
• 6c2c458 Scripting: fix jvmTarget processing from script annotations
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[github-actions]

Qodana Community for JVM

It seems all right 👌

No new problems were found according to the checks applied

💡 Qodana analysis was run in the pull request mode: only the changed files were checked

View the detailed Qodana report

To be able to view the detailed Qodana report, you can either:

• Register at Qodana Cloud and configure the action
• Use GitHub Code Scanning with Qodana
• Host Qodana report at GitHub Pages
• Inspect and use qodana.sarif.json (see the Qodana SARIF format for details)

To get *.log files or any other Qodana artifacts, run the action with upload-result option set to true,
so that the action will upload the files as the job artifacts:

      - name: 'Qodana Scan'
        uses: JetBrains/qodana-action@v2026.1.3
        with:
          upload-result: true

Contact Qodana team

Contact us at qodana-support@jetbrains.com

• Or via our issue tracker: https://jb.gg/qodana-issue
• Or share your feedback: https://jb.gg/qodana-discussions