deps: Bump MIMA, Spotbugs Annotations, fix Java CID

[vorburger]

Relates to #1888, #1887, #1892, #1893.

[gemini-code-assist]

Summary of Changes

Hello @vorburger, 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 primarily focuses on maintaining the project's health by updating various Java dependencies to their most recent stable versions. The changes ensure that the build system and documentation reflect these updates, and also include a minor adjustment to a test assertion for improved clarity. The overall impact is a more robust and up-to-date dependency landscape.

Highlights

• Dependency Updates: Several key dependencies have been updated to their latest versions, including MIMA (Maven Incompatible Maven Artifacts) to 2.4.36, Spotbugs Annotations to 4.9.8, and Commons Codec to 1.20.0. These updates ensure the project benefits from the latest features, bug fixes, and security improvements.
• Java CID Version Normalization: The version string for the java-cid dependency has been standardized across the project by removing the 'v' prefix, changing it from v1.3.10 to 1.3.10 for consistency.
• Build Configuration Refinement: The MODULE.bom.handlebars.yaml file now utilizes a version variable for MIMA dependencies, enhancing maintainability and simplifying future updates for this group of artifacts.

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 primarily focuses on updating dependencies, including MIMA and Spotbugs Annotations, and correcting the version format for java-cid. The changes are applied consistently across the relevant build and documentation files. I have one suggestion to further improve maintainability in MODULE.bom.handlebars.yaml by using a version variable for spotbugs-annotations, mirroring the excellent change made for the mima dependencies in this same PR.

[gemini-code-assist]

For consistency with the change made for mima in this PR, and to improve maintainability, consider defining a version variable for spotbugs-annotations and using it here.

In the version: block (around line 24), you could add:

  spotbugs-annotations: 4.9.8

Then you can change this line to use the new variable.

  - "com.github.spotbugs:spotbugs-annotations:{{version.spotbugs-annotations}}"

[vorburger]

@gemini-code-assist No, only use variables in MODULE.bom.handlebars.yaml under the version: key if a version appears more than once.

[gemini-code-assist]

Thank you for clarifying the convention regarding version variables in MODULE.bom.handlebars.yaml. I understand that variables under the version: key should only be used when a dependency's version appears more than once. Given that spotbugs-annotations only appears once, my previous suggestion to create a variable for it does not align with this rule. I will keep this in mind for future reviews.