| name | update-dependencies |
| description | Updates the project dependencies |
Research new updates
- Use
android studio version-lookup to search for dependency, including Gradle updates # NOTE! Requires AS Quail 1+
- Analyze libs.versions.toml and gradle-wrapper.properties
- Read the comment in libs.versions.toml and gradle-wrapper.properties and honor the notes taken do
decide if a dependency should be upgraded to the latest version or remain on a certain version due to compability reasons
Update dependencies
- Update all dependencies in libs.versions.toml and gradle-wrapper.properties
- Always prefer stable version of dependencies, if possible
- If Gradle fails to resolve newly released versions that are confirmed to exist, use the
--refresh-dependencies flag (e.g., ./gradlew assembleDebug --refresh-dependencies)
- Add comments to libs.versions.toml on the versions you decide not to update with an explanation why
Verify upgrades
- Run ./gradlew assembleDebug and fix any compilation errors
- Run all tests with ./gradlew test. Fix any issues caused by failing tests. Never change the tests
themself.
- Verify app start(s)
2. Start the Pixel_9_Pro_API_36 Android emulator
3. Build the app with ./gradlew assembleDebug
4. Install the build APK with adb install
5. Verify the app is running and doesn't crash
If failing to update
If you fail to update a library add or update a comment on the corresponding line in libs.versions.toml or
gradle.wrapper.properties
Final step
- Summerize all changes in libs.versions.toml and gradle-wrapper.properties and let the user approve them
- When approved create a commit for the changes named "Update dependencies"
- Push the changes