Skip to content

Upgrade Dagger to 2.59.1 and migrate to AGP 9#1425

Closed
lihenggui wants to merge 1 commit intonav3-migrationfrom
agp9-dagger-upgrade
Closed

Upgrade Dagger to 2.59.1 and migrate to AGP 9#1425
lihenggui wants to merge 1 commit intonav3-migrationfrom
agp9-dagger-upgrade

Conversation

@lihenggui
Copy link
Owner

Summary

  • Bump AGP 8.13.2 → 9.0.0, androidTools 31.13.2 → 32.0.0, Hilt 2.57.2 → 2.59.1
  • Bump protobuf plugin 0.9.5 → 0.9.6, roborazzi 1.52.0 → 1.56.0, macrobenchmark 1.4.1 → 1.5.0-alpha01
  • Migrate all convention plugins to AGP 9 new DSL (non-parameterized CommonExtension, localDevices, new LibraryExtension/TestExtension imports, remove explicit kotlin-android plugin)
  • Add kotlin-metadata-jvm KSP dependency for Hilt + Kotlin 2.3.0 compatibility
  • Convert core:datastore-proto from Android library to JVM library
  • Use api(platform(bom)) for Compose BOM to fix transitive version propagation
  • Align Java toolchain to 21 across all convention plugins
  • Enable JaCoCo coverage only on debug builds
  • Fix SearchViewModel @AssistedFactory parameter mismatch

Test plan

  • ./gradlew assembleFossDebug builds successfully (all modules except pre-existing nav3-migration issues in app-compose)
  • ./gradlew testFossDebugUnitTest passes
  • ./gradlew spotlessCheck passes
  • ./gradlew dependencyGuard to regenerate baselines

- Bump AGP 9.0.0, Hilt 2.59.1, protobuf plugin 0.9.6, roborazzi 1.56.0
- Migrate convention plugins to AGP 9 new DSL
- Convert datastore-proto to JVM library
- Fix Compose BOM transitive propagation and JVM target alignment
- Fix SearchViewModel @AssistedFactory parameter mismatch
@lihenggui lihenggui closed this Feb 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant