Release for v1.93.1

[github-actions]

This pull request is for the next release as v1.93.1 created by tagpr. Merging it will tag v1.93.1 to the merge commit and create a GitHub release.

You can modify this branch "tagpr-from-v1.93.0" directly before merging if you want to change the next version number or other files for the release.

How to change the next version as you like

There are two ways to do it.

• Version file
  • Edit and commit the version file specified in the .tagpr configuration file to describe the next version
  • If you want to use another version file, edit the configuration file.
• Labels convention
  • Add labels to this pull request like "tagpr:minor" or "tagpr:major"
  • If no conventional labels are added, the patch version is incremented as is.

---

What's Changed

• Update the Go version in e2e.yml by @ono-max in Update the Go version in e2e.yml #911
• Update dependency com.google.truth:truth to v1.4.3 by @renovate in Update dependency com.google.truth:truth to v1.4.3 #887
• Update dependency bazel to v7.3.2 by @renovate in Update dependency bazel to v7.3.2 #885
• LCHIB-35 removing a failed experiment by @kohsuke in [LCHIB-35] removing a failed experiment #914
• Update Songmu/tagpr action to v1.4.2 by @renovate in Update Songmu/tagpr action to v1.4.2 #919
• Update dependency com.google.truth:truth to v1.4.4 by @renovate in Update dependency com.google.truth:truth to v1.4.4 #918
• Update dependency rules_jvm_external to v6.1 by @renovate in Update dependency rules_jvm_external to v6.1 #845
• Improved a confusing message by @kohsuke in Improved a confusing message #922
• Attempting to fix the type check error by @kohsuke in Attempting to fix the type check error #925
• Make sure to report server side error message by @kohsuke in Make sure to report server side error message #926
• Update actions/checkout action to v4.2.2 by @renovate in Update actions/checkout action to v4.2.2 #924
• Update Songmu/tagpr action to v1.5.0 by @renovate in Update Songmu/tagpr action to v1.5.0 #923
• Update actions/cache action to v4.1.2 by @renovate in Update actions/cache action to v4.1.2 #921
• Update actions/setup-java action to v4.5.0 by @renovate in Update actions/setup-java action to v4.5.0 #930
• Update dependency bazel to v7.4.0 by @renovate in Update dependency bazel to v7.4.0 #934

Full Changelog: v1.93.0...v1.93.1

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

🪧 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.
  • Generate unit testing code for this file.
  • 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 generate unit testing code for this file.
  • @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 generate unit testing code.
  • @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.

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

[sonarqubecloud]

Please retry analysis of this Pull-Request directly on SonarCloud

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud