Publishing a KMP library commits you to every target you listed
Dropping a target in a minor release breaks consumers at resolution time.
build
15 posts
Seven modules, seven copies of the same Gradle block
Copy-pasted build config drifts silently per module. A convention plugin makes the shared part shared.
A dependency that resolves in commonMain and only exists on Android
Gradle metadata decides which variant each target gets. A library with no native artifact fails at link, not at resolution.
KSP runs once per target, and your generated code can disagree with itself
A processor sees one compilation at a time. Generating into commonMain is a race you win by accident.
A version catalog is a contract, and a transitive bump breaks it quietly
Declared versions are requests, not guarantees. Resolution picks the highest.
A klib is not a jar, and that changes how dependencies resolve
Metadata, klibs and platform artifacts resolve through different Gradle variants.
Why the build cache helps the JVM target and almost never the native ones
Cache keys for native compilation include the toolchain, so they rarely hit.
CocoaPods or Swift Package Manager: the choice belongs to the iOS team
Each channel constrains your publishing pipeline differently.
The Compose compiler version is not independent of your Kotlin version
A Kotlin bump without the matching plugin fails at a position no trace explains.
Gradle's configuration cache, and the one task that kept invalidating it
A task capturing Project at execution time disables it for the whole build.
R8 stripped a reflective call that only the shared module made
Shrinking runs on one target, so a reflection path ships broken there.
A framework builds for one architecture. iOS consumers need an XCFramework
A simulator-only framework works on your machine and fails on the device, and the error names a missing architecture rather than the packaging decision that caused it.