**Being built** on `claude/dependency-update-plan-1b853a`, one commit per step. Each phase
records what it turned out to be in the results table below.
| phase | result |
|---|---|
| 0 | the baseline, at `25f14aa4`. `check` green. `jvmTest` 1,407 run, 0 failed, 0 skipped, 182 classes; `testDebugUnitTest` 529 run, 0 failed, 65 classes. `m3-audit`: every budget 0, adaptive APIs **12 against a floor of 12**, navigation components 2 against 2. Resolved graphs: 277 coordinates on `jvmRuntimeClasspath`, 342 on `debugRuntimeClasspath`, 336 on `releaseRuntimeClasspath`. The newest versions were as the tables below say. The build's own warnings are AGP 9's seven deprecated opt-out flags in `gradle.properties` (each "removed in version 10.0"), the obsolete `applicationVariants` API, Kotlin's deprecation of KMP beside `com.android.application`, and three Gradle 10 deprecations (`by getting`, `by registering`), all of them in the composite's scripts rather than Giza's |
| 1 | built. Eight library entries, the `sqldelight` plugin alias and six version keys removed, with the six commented-out lines in `composeApp/build.gradle.kts` that named them or Room 2's aliases. All three resolved graphs are identical to Phase 0's, line for line. `check` green |
| 2a | built. serialization 1.13.0, kermit 2.2.0, okio 3.18.2. The graph diff is those three families and nothing else; serialization moved 1.12.0 → 1.13.0, since quartz had already lifted it past the declared 1.11.0. kermit 2.2.0 publishes one `kermit-android` where 2.1.0 had `kermit-android-debug`. `jvmTest` 1,407 run, 0 failed, once the `IdentitySwitchJvmTest` 5 s timeout seen under the first full run (the one [giza-wallet-removal.md](./giza-wallet-removal.md) Phase 3 records) passed three times alone and in a second full run |
Nothing in the last column is above 2.4.10, so Phase 2 does not wait on Phase 6.
### Left alone, and why
| what | today | why |
|---|---|---|
| quartz, marmot-kmp, mls-kmp, crypto-kmp | 2.20.1, 2.3.0, 1.3.1, 2.1.1 | [quartz-mls-marmot-update.md](./quartz-mls-marmot-update.md) owns them, and they are the newest released as of yesterday. mls-kmp 1.4.0 is its Phase 5b |
| `fr.acinq.secp256k1:secp256k1-kmp-jni-android:0.24.0` | — | substituted by the composite and never resolved; the version is a placeholder |
| `android-compileSdk`, `-targetSdk`, `-minSdk` | 37, 37, 26 | not revisited here; a target SDK move is a behaviour change with its own checks |
| `docs/tools/engine-interop/old`, `docs/tools/old-state-blob` | old engines | pinned to old versions on purpose; they exist to reproduce them |
### Dead catalogue entries
Nothing in any build script reads these:
| entry | note |
|---|---|
| `androidx-core-ktx`, `androidx-appcompat` | |
| `androidx-testExt-junit`, `androidx-espresso-core`, `junit` | there are no instrumented tests; `jvmTest` uses `kotlin-test-junit` |
| `secp256k1-kmp` | `settings.gradle.kts`, a `resolutionStrategy` that rewrites every `com.android` plugin request | 9.4.0 |
`lightning-kmp` and `bitcoin-kmp` apply no Android plugin. They take part only to carry the
submodule pointer.
**C3 — one Kotlin across the composite.** This is a choice, not something Gradle enforces (D2).
Every build pins 2.4.10 today:
| build | where |
|---|---|
| Giza | `kotlin` in the catalogue (multiplatform, compose compiler, serialization) |
| `lightning-kmp-app` | `kotlin` in its catalogue |
| `lightning-kmp` | `kotlin` in its catalogue |
| `bitcoin-kmp` | `kotlin` in its catalogue |
| `secp256k1-kmp` | `kotlin("multiplatform") version "2.4.10"` in `build.gradle.kts` |
| `docs/tools/engine-interop/new` | `kotlin("jvm") version "2.4.10"`, whose comment says to keep it at the app's versions |
**C4 — green at every commit.** Each commit passes:
-`./gradlew check`, which runs `m3Audit`, `brandAudit`, `walletAudit`, `marmotAudit` and
`magpieLockAudit`;
-`./gradlew :composeApp:compileDebugKotlinAndroid :composeApp:jvmTest`, with the test count
equal to Phase 0's;
-`./gradlew -Pmagpie.frozenLock=true :composeApp:jvmTest` once the lock is frozen. None of the
moves here may add a lock line. If one does, a library has started asking for a newer quartz
or crypto, and the `strictly` pins will already have failed resolution. That is the intended
tripwire.
**C5 — iOS is built on a mac or not at all.** The `isMacOsX` gate in `composeApp` stays. So does
the `-Xdisable-phases=RemoveRedundantCallsToStaticInitializersPhase` workaround for Kotlin
2.4.10's release linker, until a mac links a release binary without it (Phase 6). Every phase
that touches iOS-visible code leaves an iOS line for Phase 8.
## Decisions
The recommended option is first, and the plan below assumes it.
| # | question | recommended | alternative |
|---|---|---|---|
| D1 | Libraries or toolchain first? | **Libraries first** (Phases 2–3), then the toolchain (4–6). The libraries need no newer Kotlin and no submodule commit, so each is a single bisectable Giza commit. | Toolchain first, the usual order. Here it only puts the most expensive phase, the one that leaves this repository, in front of the cheap ones. |
| D2 | Kotlin in Giza alone, or down the chain as well? | **Down the chain, on the same trip as AGP.** The composite compiles all five builds in one daemon, and keeping them on one compiler is what has been done every time so far. The trip is already being made for AGP, so the extra cost is one line per submodule. | Giza alone. A newer compiler reads klibs from an older one, so it would probably work, but nothing here has been run that way. |
| D3 | Compose 1.13.0 or 1.12.2? | **1.13.0 with material3 1.13.0, if both are final when Phase 3 starts.** Otherwise 1.12.2 with material3 1.12.0-alpha03 now, and a follow-up that changes two lines once 1.13.0 ships. Either way the material3 alpha is retired onto the Compose it was built for. | Hold at 1.11.1 until 1.13.0. That keeps a material3 built for Compose 1.9.3 for however long that takes. |
| D4 | Pre-releases? | **Stable only**, except material3, which has had no stable release in JetBrains' line since 1.9.0 and is already an alpha here. Not taken: Kotlin 2.5.0-RC, AGP 9.6.0-alpha, room3 3.1.0-alpha, sqlite 2.8.0-alpha, activity 1.14.0-alpha, core 1.20.0-alpha, adaptive 1.4.0-alpha. | Take release candidates where they exist. |
| D5 | SQLDelight? | **Hold at 2.3.2.** Nothing under `mobi.giza` uses it. The runtime and drivers are there for `lightning-kmp-app`'s Phoenix databases, whose code its own 2.3.2 plugin generates. A 2.4.1 runtime under 2.3.2-generated code is a mismatch for no gain, and the whole dependency goes with wallet-removal Phase 7. | Bump the runtime to 2.4.1 and the library's plugin with it. That is a submodule commit for a dependency already on its way out. |
| D6 | One commit per library, or per phase? | **One per group that moves together**: a plugin with its runtime, Compose with material3, AGP with its composite. Each commit is green on its own (C4). | One commit per phase. That is fewer commits, but a regression found in Phase 8 then bisects to a commit that moved eight things. |
| D7 | What if wallet-removal Phase 7 lands first? | **Then Phases 5–6 shrink.** The composite becomes bitcoin-kmp → secp256k1-kmp: one AGP pin pair, and two Kotlin pins. Nothing else in this plan changes, so neither plan waits for the other. | — |
## Phase 0 — the baselines
**Half a day. No commit.**
1.**Check the newest versions again.** This plan's tables are from 2026-11-20, and Compose
1.13.0 and Kotlin 2.5.0 are both days from final. For each coordinate, read the
`maven-metadata.xml` from the repository it resolves from:
- Google Maven: `androidx.*`, `com.android.tools.build:gradle`;
- Maven Central: everything else, including the KSP plugin as
- **A comment that states the current version.** Update it. Examples are the `material3Adaptive`
comment in the catalogue, the Kotlin/Native comment in `composeApp`, and the "Kotlin 2.4.10"
line in quartz-mls-marmot-update.md's transitive table.
- **A record of what was true then.** Leave it. A phase's result in another plan is history, and
rewriting it would make that plan wrong about its own past.
- **A table that claims to be current.** Update it, or add a *Since* line the way the wallet
removal did, for example jvm-target.md's dependency table.
Add a row for this plan to [README.md](./README.md), and fill this plan's [status
table](#where-the-build-stands) with each phase's result.
No new audit. The one guard this plan could want, AGP agreeing across the composite, Gradle
already enforces by refusing to configure (C2).
## Phase 8 — what Linux cannot check
These are the checks every earlier phase deferred. They can share one session with
quartz-mls-marmot-update.md's Phase 6 mac half and Phase 8, since all three need a mac and
devices.
1. **Android, over the current build.** Install a Phase 7 debug build over a build from
`390d4bc3`, on a device that has a recovery-phrase profile, an nsec profile and an npub
profile, and is in at least one group. Every profile opens. Every group opens, and sends and
receives. This is C1: DataStore 1.3.0, Room 3.0.3 and SQLite 2.7.1 on real files.
2. **Desktop, on an existing data directory.** The same profiles and groups open. The relays
connect (ktor). Avatars load (coil). The window resizes across the three breakpoints.
3. **iOS on a mac.** A debug build and a release framework link (C5, Phase 6). The app runs on
a device. The keychain-held profiles open.
4. **QR codes** from both platforms scan on the other (2d).
5. **A release APK** installs, and runs the same as debug.
Until these pass, the status line says "built but for a mac and devices", the way the other
plans in this folder do.
## Risks, and what each one costs
| risk | where it shows | cost if missed |
|---|---|---|
| DataStore 1.3.0 reads a 1.2.1 preferences file differently | Phase 8.1 | profiles fail to open on update. High, which is why it is C1 and not a footnote |
| A material3 default changed between alphas: padding, shape, colour role | Phase 3.5 screenshots | visual regressions. Low cost, and caught by looking |
| A renamed adaptive API drops the `m3Audit` floor | Phase 3.3 | `check` fails. That is the guard working |
| Compose Resources changes its escape handling | `StringCatalogueJvmTest` | strings render with a stray backslash or a doubled `%`, a visible bug on every screen using that string |
| A submodule push is forgotten | a fresh clone fails to resolve the pointer | broken clones for everyone else. Push before the pointer moves, every level |
| The Kotlin/Native workaround is still needed at 2.4.21 | Phase 6, on a mac | none, if the rule is followed: keep it unless a link without it passes |
| ktor 3.6 changes websocket behaviour under the relay pool | `jvmTest`, then Phase 8.2 | relays that connect and then go quiet. Medium, and it looks like a network problem |
## Out of scope
- **AGP 10 and the KMP application module.** The AGP 9 opt-out flags in `gradle.properties`
(`android.builtInKotlin=false`, `android.newDsl=false`, and the others) exist because
`composeApp` applies `com.android.application` beside the Kotlin Multiplatform plugin. AGP's
next major is expected to drop those opt-outs. That would mean splitting the Android entry
point into its own module, with `composeApp` as a `com.android.kotlin.multiplatform.library`.
It is a restructure, not an update. It needs its own plan, and no AGP 10 exists yet: the
newest is 9.6.0-alpha04.
- **Kotlin 2.5.0.** It is RC as of 2026-11-11. Once it is stable it takes the same route as
Phase 6, as its own change.
- **The Magpie four.** These are quartz, marmot-kmp, mls-kmp and crypto-kmp, under the rules of
[quartz-mls-marmot-update.md](./quartz-mls-marmot-update.md): marmot's pins first, each step
past them its own commit, and lock lines for every target.
- **The composite's own libraries.** `lightning-kmp` asks for ktor 3.4.1, coroutines 1.10.2 and
serialization 1.9.0, and `lightning-kmp-app` asks for okio 3.17.0. Gradle resolves the highest
version in Giza's graph, so Giza's catalogue already decides them. Only the plugins have to
agree (C2, C3).
- **SQLDelight and `lightning-kmp-core`.** These go with wallet-removal Phase 7 (D5).
- **Material icons.** 1.7.3 is the last version published, and no newer artifact exists in
either JetBrains' line or Google's. Moving to vendored icons or Material Symbols is a design
change, not a version bump.
- **Re-enabling the configuration cache.** It is tied to secp256k1-kmp's two tasks, not to any
version here.
## Where the numbers come from
- **Newest versions:** each coordinate's `maven-metadata.xml`, on 2026-11-20, read from:
- Google Maven (`dl.google.com/android/maven2`);
- Maven Central (`repo1.maven.org/maven2`);
- the Gradle Plugin Portal (`plugins.gradle.org/m2`);
- and, for Gradle, `services.gradle.org/versions/current`.
"Newest stable" excludes alpha, beta, rc, RC and dev versions.
- **Pairings and stdlib floors:** each target's `.pom`. For kotlinx-serialization and okio,
which declare stdlib only in Gradle module metadata, the `.module` file's `requires`.
- **The composite's pins:** `lightning-kmp-app` at `3794eb8` and the submodules it pins, read
in the main checkout.
- **The AGP rule:** 546095b0, "build: unify the composite on AGP 9.4.0 so Android Studio can
sync". The error text is quoted in its message.
- **The last time these moved:** 086b2f4e (2026-08-15, Kotlin, Compose, Room, ktor and others),
546095b0 (2026-09-04, AGP), and 4e939c45 (2026-09-04, Gradle 9.7.1, carried up from the