build: hold Kotlin at 2.3.21 so consumers on 2.3.x can read our klibs#55
Merged
Conversation
v0.3.7 was built with Kotlin 2.4.0 (#52), which stamps every published klib with ABI version 2.4.0. Kotlin 2.3.x consumers hard-reject those: The current Kotlin compiler can consume libraries having ABI version <= '2.3.0'. Meshtastic-Android is pinned to Kotlin 2.3.21 until the Koin compiler plugin supports 2.4 (InsertKoinIO/koin#2431), so its mqtt-client bump fails CI (meshtastic/Meshtastic-Android#5763) and the TLS pump crash fix (#54) can't reach production. Revert the toolchain to 2.3.21 and add a Renovate hold so it can't creep back. The next release (v0.3.8) re-ships everything since v0.3.6 — the protobufs SDK migration (#50) and the TLS transport fix (#54) — on a 2.3-compatible toolchain. Kotlin 2.3.21 + CMP 1.11.1 was the CI-green state on main immediately before #52, and the full gate passes here: spotlessCheck detekt jvmTest apiCheck + iOS/wasm compile. Drop the hold and re-bump once Meshtastic-Android lands Kotlin 2.4 (meshtastic/Meshtastic-Android#5760). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This was referenced Jun 10, 2026
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.
Why
v0.3.7 was built with Kotlin 2.4.0 (#52), which stamps every published klib with ABI version 2.4.0. Kotlin 2.3.x consumers hard-reject those:
Meshtastic-Android is pinned to Kotlin 2.3.21 until the Koin compiler plugin supports 2.4 (InsertKoinIO/koin#2431). Its mqtt-client 0.3.7 bump therefore fails CI (meshtastic/Meshtastic-Android#5763), which blocks the TLS pump crash fix (#54) — currently the top production crash in the Android app — from shipping.
What
packageRuleshold so the bump can't creep back in. ci: hold Kotlin at 2.3.x until Meshtastic-Android can consume 2.4-built klibs protobufs#944 adds the same guard there.Kotlin 2.3.21 + CMP 1.11.1 was the CI-green state on main immediately before #52. Verified locally:
spotlessCheck detekt jvmTest apiCheck(the release gate) plus:library:compileKotlinIosSimulatorArm64and:library:compileKotlinWasmJsall pass; no kotlin-js-store churn.Release plan
After merge, tag v0.3.8 — Renovate then updates meshtastic/Meshtastic-Android#5763 to 0.3.8 and it goes green.
Drop the hold and re-bump Kotlin once Meshtastic-Android lands meshtastic/Meshtastic-Android#5760.
🤖 Generated with Claude Code