chore(deps): bump rules_java to 7.3.1

[albertocavalcante]

Summary by CodeRabbit

• Chores
  • Updated an external dependency to a newer version for improved compatibility and security.
  • Minor whitespace adjustment in a comment for code clarity.

[coderabbitai]

Walkthrough

This update modifies the WORKSPACE.bazel file to reference a newer version of the rules_java external dependency, updating both its URL and SHA256 checksum. Additionally, a minor whitespace adjustment is made in the _fail_with_attr function within antlr/repositories.bzl, with no impact on logic or functionality.

Changes

File(s)	Change Summary
WORKSPACE.bazel	Updated rules_java dependency version from 6.5.2 to 7.3.1 and adjusted SHA256 checksum.
antlr/repositories.bzl	Minor whitespace change in _fail_with_attr function; no functional or logic modifications.

Possibly related PRs

• update repositories.bzl #62: Refactors antlr/repositories.bzl, including introducing and modifying the _fail_with_attr function, which is also touched in this PR.

Poem

A hop and a skip, to Java anew,
With rules updated, dependencies grew.
A tiny space, in code aligned,
All neat and tidy, whitespace refined.
The rabbit approves, with whiskers a-twitch—
Onward to builds that go without a hitch! 🐇✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between bed49c4 and de7cd6f.

📒 Files selected for processing (2)

• WORKSPACE.bazel (1 hunks)
• antlr/repositories.bzl (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: Build and Test

🔇 Additional comments (3)

antlr/repositories.bzl (1)

166-166: Approve whitespace-only adjustment
Repositioning the # type: ignore comment is purely stylistic and has no effect on functionality.

WORKSPACE.bazel (2)

9-9: Confirm updated URL for rules_java 7.3.1
The download URL has been correctly updated to the new release.

---

7-7:

Details

✅ Verification successful

Verify SHA256 for rules_java version bump
Ensure the new checksum matches the 7.3.1 release tarball before merging.

Run this command and compare the output to the updated value:

---

🏁 Script executed:

curl -sL https://github.com/bazelbuild/rules_java/releases/download/7.3.1/rules_java-7.3.1.tar.gz | sha256sum

Length of output: 211

---

🏁 Script executed:

#!/bin/bash
# Compute SHA-256 via Python since sha256sum is not available
curl -sL https://github.com/bazelbuild/rules_java/releases/download/7.3.1/rules_java-7.3.1.tar.gz \
  | python3 -c 'import sys,hashlib; print(hashlib.sha256(sys.stdin.buffer.read()).hexdigest())'

Length of output: 258

---

Validated SHA256 for rules_java 7.3.1
The SHA-256 checksum computed via Python matches the value already specified in WORKSPACE.bazel, so no update is needed.

• WORKSPACE.bazel (line 7): 4018e97c93f97680f1650ffd2a7530245b864ac543fd24fae8c02ba447cb2864

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[greptile-apps]

PR Summary

Your free trial has ended. If you'd like to continue receiving code reviews, you can add a payment method here: https://app.greptile.com/review/github.

_{2 file(s) reviewed, no comment(s)
Edit PR Review Bot Settings | Greptile}

[gemini-code-assist]

Hello @albertocavalcante, 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!

Summary of Changes

Hello, this is gemini-code-assist providing a summary of this pull request. The primary goal of this PR is to update the rules_java dependency used in the Bazel build system. Specifically, it bumps the version from 6.5.2 to 7.3.1 in the WORKSPACE.bazel file, along with the corresponding SHA256 hash. Additionally, there is a minor, non-functional change in antlr/repositories.bzl involving whitespace in a comment.

Highlights

• Dependency Update: Updates the rules_java Bazel dependency from version 6.5.2 to 7.3.1 in the WORKSPACE.bazel file.
• SHA256 Hash Update: Updates the SHA256 hash for the new rules_java version in WORKSPACE.bazel.
• Minor Code Style Change: Adjusts whitespace in a comment in the antlr/repositories.bzl file.

Changelog

• WORKSPACE.bazel
  • Updated rules_java dependency version from 6.5.2 to 7.3.1.
  • Updated SHA256 hash for the new rules_java version.
• antlr/repositories.bzl
  • Minor whitespace adjustment in a comment on line 166.

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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

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 issue 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 is currently in preview and 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 to provide feedback.

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 PR updates rules_java to version 7.3.1 and includes a minor stylistic fix in antlr/repositories.bzl. The dependency update from 6.5.2 to 7.3.1 is a significant one.

To improve clarity for reviewers and future maintainers, could you please consider adding a brief note to the PR description? Linking to the rules_java 7.x release notes (e.g., 7.0.0 for major changes and 7.3.1 for this specific version) would be very helpful to highlight key changes, such as the default JDK version moving to 17 and the Bazel 6+ requirement.

Summary of Findings

• rules_java Upgrade Implications: The update of rules_java to 7.3.1 brings significant changes, such as the default Java toolchain now being JDK 17 (previously JDK 11) and a requirement for Bazel 6.0.0+. Confirmation of testing and compatibility with these changes is recommended to ensure the project continues to build and function as expected.
• Stylistic Improvement (Low Severity): A stylistic improvement was made in antlr/repositories.bzl (line 166) by adding an extra space before an inline comment (# type: ignore). This aligns with common style practices like PEP 8, which recommends two spaces before inline comments. This is a positive change for code readability. (Not commented on directly due to review severity settings focusing on medium+ issues).

Merge Readiness

This pull request updates a key dependency, rules_java, to a significantly newer version. While the code changes themselves are minimal, the implications of this upgrade (such as a new default JDK version and Bazel version requirements) are important to consider.

I recommend that the author confirm that the project has been thoroughly tested with rules_java 7.3.1 and that it is compatible with the new defaults and requirements. Adding details about this verification and linking to the rules_java release notes in the PR description would greatly benefit the review process and future maintainability.

As a reviewer, I am not authorized to approve pull requests. Given the medium severity concern raised regarding the implications of the dependency upgrade, I suggest these points be addressed or confirmed before this PR is merged.

[gemini-code-assist]

Updating rules_java from 6.5.2 to 7.3.1 is a notable version jump. The 7.x series of rules_java introduces some important changes, including:

• The default Java toolchain is now based on JDK 17 (previously JDK 11).
• Bazel 6.0.0 or newer is required.

Could you confirm if:

1. The project has been tested with these new defaults, particularly the implications of using JDK 17 by default?
2. The Bazel version currently used by the project meets the new minimum requirement of 6.0.0+?

Understanding these aspects is crucial for ensuring a smooth upgrade. It might also be beneficial to explicitly state any necessary configuration changes or testing performed in the PR description.