Conversation
compose-devrel-github-bot
requested review from
dturner,
riggaroo and
simona-anomis
as code owners
Summary of ChangesHello @compose-devrel-github-bot, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request systematically updates various project dependencies across multiple applications within the repository. The primary goal is to ensure that all projects are using the latest stable versions of their libraries and build tools, which helps in maintaining compatibility, leveraging new features, and incorporating the latest bug fixes and security patches. Highlights
🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. Changelog
Activity
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request updates various dependencies across multiple sample projects. The changes are consistent and appear to be automated. My main feedback concerns the project structure, which leads to duplicated libs.versions.toml files and increased maintenance effort, as demonstrated by this PR. I've added a specific comment suggesting centralization of dependency management to improve maintainability and simplify future updates.
| androidGradlePlugin = "9.0.1" | ||
| androidx-activity-compose = "1.12.4" | ||
| androidx-appcompat = "1.7.1" | ||
| androidx-compose-bom = "2026.01.01" | ||
| androidx-compose-bom = "2026.02.00" |
There was a problem hiding this comment.
These version updates are being applied to multiple, nearly identical libs.versions.toml files across different sample projects. This duplication increases maintenance overhead, as seen in this PR where several files require the same set of changes. Some of the other version catalog files (e.g., in JetNews) even contain comments indicating they should be duplicated from a global file, but the update process seems to modify them individually.
To improve maintainability and align with the apparent original intent, consider centralizing dependency management. This could be achieved by either creating a script to synchronize a master catalog file to all projects or by restructuring the projects to share a single version catalog via Gradle's composite builds feature. This would streamline future updates and prevent inconsistencies.
1 participant
Updated depedencies