Bump rules_kotlin to 2.2.2

[agluszak]

Checklist

• I have filed an issue about this change and discussed potential changes with the maintainers.
• I have received the approval from the maintainers to make this change.
• This is not a stylistic, refactoring, or cleanup change.

Please note that the maintainers will not be reviewing this change until all checkboxes are ticked. See
the Contributions section in the README for more
details.

Discussion thread for this change

Issue number: <please reference the issue number or url here>

Description of this change

[gemini-code-assist]

Summary of Changes

Hello @agluszak, I'm Gemini Code Assist¹! 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 critical dependency upgrade for rules_kotlin to its latest stable version. This update triggers a cascade of necessary synchronizations across various Bazel module dependencies and a cleanup of the Maven dependency management configuration, ensuring the project remains current with its build tooling and libraries. The changes aim to improve stability, leverage new features, and maintain compatibility within the build system.

Highlights

• rules_kotlin Version Update: The primary change involves updating the rules_kotlin dependency from version 2.2.1 to 2.2.2 in the MODULE.bazel file.
• Bazel Module Dependency Sync: The MODULE.bazel.lock file has been updated to reflect new versions and hashes for several other Bazel modules, including abseil-cpp, bazel_skylib, bazel_worker_api, bazel_worker_java, protobuf, and rules_cc, ensuring consistency with the updated rules_kotlin.
• Maven Dependency Refinement: The maven_install.json file has been modified to update artifact hashes, remove explicit entries for protobuf-java and protobuf-java-util, and streamline conflict resolution by removing older versions of Guava, Truth, and Mockito.

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. ↩

[gemini-code-assist]

Code Review

This pull request updates the rules_kotlin dependency to version 2.2.2. This change also updates several transitive dependencies in MODULE.bazel.lock and cleans up the maven_install.json lock file, notably by removing Maven artifacts for protobuf which is now correctly handled as a Bazel module. The changes are consistent and look correct for a dependency update. However, the pull request description is empty and the checklist is not filled out. Please update the description and checklist as required by the project's contribution guidelines before this can be merged.