Repository navigation
Update Compose to BOM 2026.06.01 - #144
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Walkthrough
Merge Risk: ⚪ Minimal · up to This change updates Android dependency versions, with no demonstrated incompatibility or material behavior risk. It appears ready for normal checks. Pre-merge checks |
|
Code reviewNo issues found. Checked for bugs and CLAUDE.md compliance. 🤖 Generated with Claude Code |
aaronbrethorst
left a comment
There was a problem hiding this comment.
Version-catalog-only, no Compose artifacts pinned against the BOM, and CI built both debug and minified release and ran the instrumented suite. Good to go. A follow-up for later: createComposeRule is now deprecated in favor of the v2 rule.
Updates the Android app's Compose libraries to the newest versions that still build with our AGP 8.11 and compileSdk 36. No app code changes.
Why now: the Android UI work for #36 needs APIs that are stable only in these versions (shared element transitions, Text autoSize, haptics with fallbacks on older phones). Doing the update on its own means any regression shows up here, not inside a UI change.
Why not newer: Compose 1.12, navigation 2.10 and material3 1.5 (the Material 3 Expressive components) all need AGP 9.1 and compileSdk 37. I'd like to do the AGP 9 upgrade as its own PR next. material3 1.5 is still beta, so the UI work will copy its motion values until it is stable.
Tested:
Summary by CodeRabbit