chore(deps): upgrade Kotlin 2.3.21 -> 2.4.0 (compiler + stdlib + reflect)#161
Merged
Conversation
…ect) Closes Dependabot #146. A *real* toolchain upgrade, not the isolated kotlin-reflect bump Dependabot proposed (which would have mismatched the 2.3.21 compiler). What it took (documented for next time): bumping the kotlin("jvm") plugin to 2.4.0 alone leaves the actual compiler at 2.3.21 — Kotlin's Build Tools API decouples the plugin version from the compiler version, and this project's lockfiles pinned `kotlin-* {strictly 2.3.21}`. Neither --write-locks nor --update-locks could override the strict lock in one pass (the existing strict version wins the conflict, then re-persists). The fix: drop the kotlin 2.3.21 lock lines from every lockfile, then --write-locks, so they re-resolve to the 2.4.0 plugin default. Result (verified via dependencyInsight): kotlin-compiler-embeddable, kotlin-stdlib, and kotlin-reflect all 2.4.0 on the compile/runtime classpaths. The 2.4.0 compiler compiles the codebase with no new errors (only the pre-existing ForumBuilder unchecked-cast warnings). Full ./gradlew build green, all tests pass, detekt baseline steady at 415. - build.gradle.kts: plugin + both kotlin-reflect -> 2.4.0 - Regenerated all gradle.lockfiles (kotlin-only churn; no other dep moved) + added 2.4.0 sha256 checksums to verification-metadata. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes Dependabot #146 — but as a real toolchain upgrade, not the isolated
kotlin-reflectbump Dependabot proposed (which would mismatch the 2.3.21 compiler).Why it wasn't a one-liner: bumping
kotlin("jvm")to 2.4.0 alone leaves the actual compiler at 2.3.21 — Kotlin's Build Tools API decouples the plugin version from the compiler version, and the lockfiles pinkotlin-* {strictly 2.3.21}. Neither--write-locksnor--update-locksoverrides astrictlylock in one pass. The fix: drop the kotlin 2.3.21 lock lines from every lockfile, then--write-locks, so they re-resolve to the 2.4.0 plugin default.Result (verified via
dependencyInsight):kotlin-compiler-embeddable,kotlin-stdlib, andkotlin-reflectare all 2.4.0 on the compile/runtime classpaths. The 2.4.0 compiler builds the codebase with no new errors (only pre-existing ForumBuilder cast warnings). Full./gradlew buildgreen, all tests pass, detekt baseline steady at 415.build.gradle.kts: plugin + bothkotlin-reflect-> 2.4.0gradle.lockfiles (kotlin-only churn) + 2.4.0 sha256 checksums inverification-metadata.xml.With this, the entire Dependabot batch is resolved.
🤖 Generated with Claude Code