Skip to content

🤖 Update Dependencies#1661

Open
compose-devrel-github-bot wants to merge 1 commit intomainfrom
bot-update-deps
Open

🤖 Update Dependencies#1661
compose-devrel-github-bot wants to merge 1 commit intomainfrom
bot-update-deps

Conversation

@compose-devrel-github-bot
Copy link
Contributor

Updated depedencies

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello, 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 performs routine dependency updates across multiple projects by bumping the versions of the Android Gradle Plugin, AndroidX Compose Bill of Materials, and the Spotless code formatter. These updates are crucial for maintaining compatibility, leveraging the latest features, and ensuring consistent code quality and build stability across the codebase.

Highlights

  • Android Gradle Plugin Update: The Android Gradle Plugin has been updated from version 9.0.1 to 9.1.0 across all affected projects.
  • AndroidX Compose BOM Update: The AndroidX Compose Bill of Materials (BOM) has been upgraded from version 2026.02.00 to 2026.02.01.
  • Spotless Plugin Update: The Spotless code formatting plugin has been updated from version 8.2.1 to 8.3.0.

🧠 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
  • JetLagged/gradle/libs.versions.toml
    • Updated androidGradlePlugin from 9.0.1 to 9.1.0
    • Updated androidx-compose-bom from 2026.02.00 to 2026.02.01
    • Updated spotless from 8.2.1 to 8.3.0
  • JetNews/gradle/libs.versions.toml
    • Updated androidGradlePlugin from 9.0.1 to 9.1.0
    • Updated androidx-compose-bom from 2026.02.00 to 2026.02.01
    • Updated spotless from 8.2.1 to 8.3.0
  • Jetchat/gradle/libs.versions.toml
    • Updated androidGradlePlugin from 9.0.1 to 9.1.0
    • Updated androidx-compose-bom from 2026.02.00 to 2026.02.01
    • Updated spotless from 8.2.1 to 8.3.0
  • Jetsnack/gradle/libs.versions.toml
    • Updated androidGradlePlugin from 9.0.1 to 9.1.0
    • Updated androidx-compose-bom from 2026.02.00 to 2026.02.01
    • Updated spotless from 8.2.1 to 8.3.0
  • Reply/gradle/libs.versions.toml
    • Updated androidGradlePlugin from 9.0.1 to 9.1.0
    • Updated androidx-compose-bom from 2026.02.00 to 2026.02.01
    • Updated spotless from 8.2.1 to 8.3.0
Activity
  • The pull request was opened by compose-devrel-github-bot with the intention of updating dependencies.
  • No human review activity or comments have been recorded since the pull request was created.
Using Gemini Code Assist

The 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 /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

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 .gemini/ folder in the base of the repository. Detailed instructions can be found here.

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

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This PR updates dependencies across several sample projects. The changes highlight a significant amount of duplication, as the same versions are updated in multiple libs.versions.toml files. This increases maintenance overhead. I've added a comment suggesting a refactor to centralize dependency management into a single version catalog at the project root, which would greatly improve maintainability.

Note: Security Review has been skipped due to the limited scope of the PR.

Comment on lines +4 to +7
androidGradlePlugin = "9.1.0"
androidx-activity-compose = "1.12.4"
androidx-appcompat = "1.7.1"
androidx-compose-bom = "2026.02.00"
androidx-compose-bom = "2026.02.01"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

These dependency versions are updated identically across multiple libs.versions.toml files in this repository. This duplication of version catalogs increases maintenance overhead and makes it difficult to ensure consistency across projects.

A better approach would be to use a single libs.versions.toml file at the root of the repository. Gradle allows sub-projects to share a version catalog, which would centralize all dependency versions. This would simplify updates and ensure all modules use a consistent set of dependencies.

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