Skip to content

Conversation

compose-devrel-github-bot
Copy link
Contributor

Updated depedencies

Copy link
Contributor

Summary of Changes

Hello @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 focuses on a routine maintenance task: updating various project dependencies to their latest stable versions. This ensures that the applications benefit from the most recent bug fixes, performance improvements, and new features provided by the updated libraries, thereby enhancing overall stability and developer experience. The changes are consistently applied across multiple projects, including JetLagged, JetNews, Jetchat, Jetsnack, and Reply.

Highlights

  • AndroidX Compose BOM Update: The AndroidX Compose Bill of Materials (BOM) has been updated from version "2025.09.00" to "2025.09.01" across all affected projects.
  • AndroidX Navigation Upgrade: The AndroidX Navigation library has been upgraded from version "2.9.4" to "2.9.5" in all relevant libs.versions.toml files.
  • AndroidX Wear Compose Update: The AndroidX Wear Compose dependency has been bumped from "1.5.1" to "1.5.2" for improved wearable UI development.
  • AndroidX Window Upgrade: The AndroidX Window library has been updated from version "1.4.0" to "1.5.0" to leverage the latest window management features.
  • Gradle Versions Plugin Update: The gradle-versions plugin has been upgraded from "0.52.0" to "0.53.0", which helps in managing and updating project dependencies.
  • Maps Compose Update: The maps-compose library has been updated from version "6.10.0" to "6.11.0" to incorporate the latest mapping functionalities.
  • Room Database Upgrade: The Room persistence library has been bumped from version "2.8.0" to "2.8.1" for potential bug fixes and minor enhancements.
  • Spotless Formatting Tool Update: The Spotless code formatter has been upgraded from version "7.2.1" to "8.0.0", ensuring consistent code style with the latest features.
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 pull request updates various dependencies across multiple sample projects. While most are minor and patch version bumps that seem safe, the update to the Spotless Gradle plugin is a major version change (from v7 to v8). I've left a comment highlighting the potential for breaking changes and suggesting verification steps to ensure a smooth transition. Apart from that, the dependency updates look good.

room = "2.8.1"
secrets = "2.0.1"
spotless = "7.2.1"
spotless = "8.0.0"
Copy link
Contributor

Choose a reason for hiding this comment

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

high

This is a major version update for Spotless (from 7.x to 8.x), which can introduce breaking changes in configuration or formatting rules. It's important to verify that the current Spotless configuration is still valid and to run spotlessApply to check for and apply any new formatting changes. This will help prevent unexpected formatting issues or build failures in future pull requests. Please check the Spotless v8.0.0 release notes for migration details.

room = "2.8.1"
secrets = "2.0.1"
spotless = "7.2.1"
spotless = "8.0.0"
Copy link
Contributor

Choose a reason for hiding this comment

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

high

This is a major version update for Spotless (from 7.x to 8.x), which can introduce breaking changes in configuration or formatting rules. It's important to verify that the current Spotless configuration is still valid and to run spotlessApply to check for and apply any new formatting changes. This will help prevent unexpected formatting issues or build failures in future pull requests. Please check the Spotless v8.0.0 release notes for migration details.

room = "2.8.1"
secrets = "2.0.1"
spotless = "7.2.1"
spotless = "8.0.0"
Copy link
Contributor

Choose a reason for hiding this comment

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

high

This is a major version update for Spotless (from 7.x to 8.x), which can introduce breaking changes in configuration or formatting rules. It's important to verify that the current Spotless configuration is still valid and to run spotlessApply to check for and apply any new formatting changes. This will help prevent unexpected formatting issues or build failures in future pull requests. Please check the Spotless v8.0.0 release notes for migration details.

room = "2.8.1"
secrets = "2.0.1"
spotless = "7.2.1"
spotless = "8.0.0"
Copy link
Contributor

Choose a reason for hiding this comment

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

high

This is a major version update for Spotless (from 7.x to 8.x), which can introduce breaking changes in configuration or formatting rules. It's important to verify that the current Spotless configuration is still valid and to run spotlessApply to check for and apply any new formatting changes. This will help prevent unexpected formatting issues or build failures in future pull requests. Please check the Spotless v8.0.0 release notes for migration details.

room = "2.8.1"
secrets = "2.0.1"
spotless = "7.2.1"
spotless = "8.0.0"
Copy link
Contributor

Choose a reason for hiding this comment

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

high

This is a major version update for Spotless (from 7.x to 8.x), which can introduce breaking changes in configuration or formatting rules. It's important to verify that the current Spotless configuration is still valid and to run spotlessApply to check for and apply any new formatting changes. This will help prevent unexpected formatting issues or build failures in future pull requests. Please check the Spotless v8.0.0 release notes for migration details.

@riggaroo riggaroo merged commit b6ddc9b into main Sep 26, 2025
19 checks passed
@riggaroo riggaroo deleted the bot-update-deps branch September 26, 2025 17:17
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.

2 participants