chore(deps): update dependency bazel to v8.6.0

[renovate-bot]

This PR contains the following updates:

Package	Update	Change
bazel	minor	8.4.2 → 8.6.0

---

Release Notes

bazelbuild/bazel (bazel)

v8.6.0

Compare Source

Release Notes:

v8.5.1

Compare Source

Release Notes:

v8.5.0

Compare Source

Release Notes:

---

Configuration

📅 Schedule: Branch creation - Monday through Friday ( * * * * 1-5 ) (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[dpebot]

/gcbrun

[gemini-code-assist]

Summary of Changes

Hello @renovate-bot, 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 updates the Bazel version used in the project and its CI configurations. This ensures the project uses the latest features and bug fixes available in Bazel 8.5.1, and maintains consistency across the development and CI environments.

Highlights

• Dependency Update: This PR updates the Bazel dependency from version 8.4.2 to 8.5.1.
• Version Consistency: The .bazelversion files in the repository and CI directories have been updated to reflect the new Bazel version.

Changelog

• .bazelversion
  • Updated Bazel version from 8.4.2 to 8.5.1
• ci/verify_current_targets/.bazelversion
  • Updated Bazel version from 8.4.2 to 8.5.1
• ci/verify_deprecated_targets/.bazelversion
  • Updated Bazel version from 8.4.2 to 8.5.1

Activity

• The PR was created by renovate-bot to update the bazel dependency.
• The PR updates the bazel version in multiple .bazelversion files.
• The PR description includes release notes and configuration details for the update.

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 Bazel version from 8.4.2 to 8.5.1 across three .bazelversion files. The changes are consistent and correctly apply the version bump.

While reviewing, I observed that the repository uses multiple Bazel versions. The main development environment and some CI jobs will now use 8.5.1, while other parts of the CI system (for macOS and Windows) and the quickstart examples are pinned to version 7.6.1. This version is hardcoded in several places (e.g., ci/kokoro/macos/builds/bazel.sh, ci/kokoro/windows/lib/bazel.ps1). To improve maintainability and reduce the risk of inconsistencies, I recommend refactoring these scripts to read the Bazel version from a central configuration file, such as the root .bazelversion. This would centralize version management and simplify future updates. Since these files are not part of the current changes, this is a suggestion for a future improvement.

[scotthart]

/gcbrun

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 92.63%. Comparing base (0dcc03b) to head (4ba8f48).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main   #16002   +/-   ##
=======================================
  Coverage   92.63%   92.63%           
=======================================
  Files        2334     2334           
  Lines      214633   214633           
=======================================
  Hits       198828   198828           
  Misses      15805    15805           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[dpebot]

/gcbrun