Skip to content

chore(deps): update dependency rules_jvm_external to v6.10#8151

Open
LeFrosch wants to merge 2 commits intobazelbuild:masterfrom
LeFrosch:pull/ee142ffcd0c1278d14ca45e4f0e552fdca71b9b7
Open

chore(deps): update dependency rules_jvm_external to v6.10#8151
LeFrosch wants to merge 2 commits intobazelbuild:masterfrom
LeFrosch:pull/ee142ffcd0c1278d14ca45e4f0e552fdca71b9b7

Conversation

@LeFrosch
Copy link
Collaborator

@LeFrosch LeFrosch commented Feb 10, 2026

Follow up for: #8137

Apparently requires us to fix rules android again, since older versions don't play nicely with Bazel 9.

@gemini-code-assist
Copy link

Summary of Changes

Hello @LeFrosch, 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 primarily focuses on updating the project's Bazel dependency ecosystem. The core change involves upgrading rules_jvm_external to its latest version, which necessitated cascading updates across several other Bazel modules and their corresponding lock file entries. Additionally, a specific compatibility issue with rules_android was resolved by explicitly declaring its dependency. The changes ensure the build system remains current and stable with the latest rule sets.

Highlights

  • Dependency Update: Updated the rules_jvm_external Bazel dependency from version 6.9 to 6.10.
  • Android Rules Compatibility: Added an explicit bazel_dep for rules_android version 0.7.1 to address a compatibility issue.
  • Bazel Module Lock File Updates: Synchronized the MODULE.bazel.lock file to reflect updated hashes and new entries for various Bazel modules, including gazelle, package_metadata, rules_android, rules_go, rules_java, rules_jvm_external, and rules_kotlin.
  • Maven Install Lock File Format Change: Updated the maven_install.json lock file, changing the format of artifact hashes from a single integer to a detailed object mapping, and incremented its internal version from 2 to 3.
Changelog
  • MODULE.bazel
    • Updated rules_jvm_external dependency from 6.9 to 6.10.
    • Added rules_android dependency at version 0.7.1.
  • MODULE.bazel.lock
    • Updated gazelle module entries to include version 0.47.0.
    • Updated package_metadata module entries to include versions 0.0.5 and 0.0.7.
    • Updated rules_android module entries to include versions 0.6.6 and 0.7.1.
    • Added rules_go module entry for version 0.53.0.
    • Added rules_java module entries for versions 8.13.0 and 9.4.0.
    • Added rules_jvm_external module entries for version 6.10 and removed 6.9 source.json.
    • Added rules_kotlin module entry for version 2.1.3.
    • Updated usagesDigest for apksig_extension and android_sdk_repository_extension.
    • Added com_android_dex_extension with its bzlTransitiveDigest, usagesDigest, and generatedRepoSpecs.
  • maven_install.json
    • Updated __INPUT_ARTIFACTS_HASH and __RESOLVED_ARTIFACTS_HASH from single integer values to detailed object maps of artifact hashes.
    • Removed com.google.code.gson and com.google.guava entries from conflict_resolution.
    • Incremented the internal version from 2 to 3.
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

@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 the rules_jvm_external dependency to version 6.10. This also brings in updates to several transitive dependencies and a format change in maven_install.json, which are correctly reflected in the lock files. The explicit override for rules_android to version 0.7.1 to fix a compatibility issue is a good and well-documented change. The changes look correct and are a straightforward dependency upgrade.

@LeFrosch LeFrosch marked this pull request as ready for review February 10, 2026 17:33
@github-actions github-actions bot added the awaiting-review Awaiting review from Bazel team on PRs label Feb 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

awaiting-review Awaiting review from Bazel team on PRs

Projects

Status: Untriaged

Development

Successfully merging this pull request may close these issues.

2 participants