[BW-DEP-01] Execute staged latest-stable toolchain and dependency migration #42
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Classification
Build/toolchain/dependency maintenance program. This issue owns execution of the staged migration described by
docs/latest-stable-upgrade-plan.md; GitHub PR #131 was the planning/tooling-preparation change and did not execute the migration.Goal
Move BookWave toward the latest mutually compatible stable build tools, Android platform, frameworks, application/runtime libraries, test tooling and CI tooling without turning the upgrade into one unreviewable dependency bomb or weakening verification to make it pass.
gradle/libs.versions.tomlremains the pinned dependency/toolchain source of truth.docs/latest-stable-upgrade-plan.mdremains the detailed migration playbook and should be referenced rather than copied here.Current compatibility gate
Re-resolve this at the start of every phase. As of 2026-09-10, accepted ADR-0011 is still material: it says BookWave stays off AGP 9 / API 37 until detekt has a stable 2.x release with the required type-resolution support, unless that ADR is explicitly superseded by a separately accepted decision. The currently published detekt 2.x line is still pre-release, so do not bypass the ADR by pinning an alpha.
Also do not assume the individually newest Gradle, AGP and Kotlin releases form a supported trio. Verify their official compatibility ranges immediately before each build-foundation phase.
Execution rules
main, not from a stale upgrade branch.--rerun-tasksas required byAGENTS.md/docs/testing.md.Required phase-specific evidence
compileSdk/targetSdkahead of the accepted architecture gate.Suggested staged sequence
Follow
docs/latest-stable-upgrade-plan.md, re-splitting when compatibility evidence requires it. The conceptual order is:Do not force this sequence if current official compatibility evidence requires a narrower split. Record why any phase is moved.
Acceptance criteria
gradle/libs.versions.toml, build docs, upgrade plan status and CI/Codex provisioning agree after each relevant phase.Governance
Do not merge any implementation PR automatically. Every phase is a separate reviewed change unless the repository's current plan explicitly justifies combining tightly coupled axes.
Reopened after verifying merged GitHub PR #137 against this issue. GitHub PR #137 was explicitly Phase 0 inventory/documentation only, changed only
docs/README.mdand addeddocs/dependency-compatibility-inventory.md, changed no dependency/toolchain/SDK/CI versions, and explicitly stated that it did not close #135. The staged migration therefore remains active; no duplicate issue is being created.Next staged slice opened as GitHub PR #161: AndroidX Activity 1.12.4 → 1.13.0. Stable 1.13.0 remains compatible with the current API-36 lane; the newer 1.14 line is prerelease and its Compose artifacts move to compileSdk 37.1, so ADR-0011 remains intact.
version-control.mdand the Phase-3 roadmap status are updated in the same PR. #135 remains open.GitHub PR #161 merged successfully after full CI and focused device smoke, but its merge auto-closed this umbrella migration issue. Reopening #135 because BW-DEP-01 remains intentionally active across the remaining staged dependency/toolchain slices. The next active maintenance slice is GitHub PR #162 (Gradle 8.14.3 → 8.14.5); the Gradle 9 / AGP 9 / API 37 foundation remains gated by ADR-0011.
Reopened after GitHub PR #163 merged. #163 completed only the Room 2.7.2 → 2.8.5 Phase-4 slice; it did not complete BW-DEP-01. The issue acceptance criteria still require the remaining compatible runtime/network, visual, test, CI/tooling and dependency-automation work. Individual staged migration PRs must not close the umbrella issue.
Reopened after GitHub PR #167 auto-closed this umbrella migration issue. #167 completed only the first-party Retrofit kotlinx.serialization converter ownership/coordinates slice; Phase 5 still has the Retrofit and OkHttp major network-stack migrations outstanding, followed by later phases from the staged plan. Keep #135 open until the full migration program is complete.
Post-#169 reconciliation is now in draft GitHub PR #170.
Phase 5 is reconciled as complete at the current mutually compatible stable frontier:
javax.inject:1has no version migration and needs no manufactured dependency PR;mockwebserver3package/API migration is not required for Phase-5 completion.GitHub PR #170 also corrects stale Phase-4 status after merged Room #163. No runtime or dependency pins change. After this reconciliation merges, Phase 6 (Coil major, then Haze separately) is the next executable dependency lane.
Keep #135 open: Phases 6-9 plus the gated build/platform foundation remain outstanding.