Compatibility
Kinvoicing is tested weekly against the 3 most recent Compose Multiplatform releases on macOS and Linux.
Compose Multiplatform versions
| Compose Multiplatform | Kotlin | Status | |:———————-|:——-|:——-| | 1.12.0-beta01 | 2.4.0 | CI tested (pre-release, non-blocking) | | 1.11.1 | 2.4.0 | CI tested (current) | | 1.10.3 | 2.4.0 | CI tested |
This table is generated from .github/compose-versions.json and updated weekly by the update-compose-versions workflow, which discovers the 3 most recent CMP releases and runs the compatibility suite against each. The current row is the version the library itself pins. Edit compose-versions.json, not this table.
Stable rows are blocking — a failure fails CI. On the newest pre-release row (e.g. an -alpha/-beta/-rc build), the shipped-renderer compatibility smoke (render-html/render-pdf, which exercise the reflective @InternalComposeUiApi scene path) is non-blocking (continue-on-error), so upstream Compose pre-release churn in that internal API can’t red-flag the build — treat it as an early-warning signal. The render-compose per-cell recompile stays blocking even on pre-release rows, since it uses only stable public Compose APIs.
What is tested per cell
Kinvoicing publishes several artifacts, so “Compose compatibility” means different things per module:
| Module | How it’s exercised against each cell |
|---|---|
:render-html | Tested directly — its own reflective Compose scene driver renders through the cell’s Compose/Skiko runtime. |
:render-pdf | Tested via compose2pdf — compose2pdf’s reflective scene driver drives the render, so it inherits compose2pdf’s own compatibility surface. |
:render-compose | Source-recompiled per cell — the library’s pinned Compose/Kotlin is overridden to the cell, then :render-compose’s own jvmTest, wasmJsNodeTest (and iosSimulatorArm64Test on macOS) are recompiled and run against it. A multi-target KMP klib can’t be reflectively bridged, so this is the normal KMP consumer contract (Compose is an api dependency, resolved by the consumer). |
:core, :render-html-email | Compose-independent — neither declares any org.jetbrains.compose or skiko dependency, so no Compose version can affect them. They are not part of the Compose matrix. |
How compatibility is tested
The compatibility workflow runs on pull requests touching the Compose renderers, weekly on Monday at 9am UTC, and on demand.
It loads the Compose Multiplatform versions from .github/compose-versions.json, publishes the shipped renderer binaries at the pinned base version, then overrides the library’s pinned Compose/Kotlin to each cell and runs :render-compose:assemble (or :render-compose:jvmJar for pre-release cells, to skip the Android target whose preview androidx metadata needs a newer compileSdk), :render-compose:jvmTest, :render-compose:wasmJsNodeTest (plus iosSimulatorArm64Test on macOS) and consumes the shipped renderers on the cell’s runtime.
The update-compose-versions workflow automatically discovers new CMP releases weekly, bumps the shipped build base to the latest stable, regenerates this table, and opens a PR.
See also
- Home – Overview and installation