chore(deps): update googleapis digest to dc50596

[renovate-bot]

This PR contains the following updates:

Package	Type	Update	Change
googleapis	http_archive	digest	edfe798 → dc50596

---

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.

---

This change is 

[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 googleapis dependency to a newer digest, ensuring the project utilizes the latest version of the library. This change primarily involves updating the Bazel build configuration to fetch the correct archive and verify its integrity with the new SHA256 hash.

Highlights

• Dependency Update: The googleapis dependency has been updated to digest dc50596 from edfe798.
• Bazel Configuration: The bazel/workspace0.bzl file was modified to reflect the new googleapis archive URL, SHA256 hash, and strip prefix.

Changelog

• bazel/workspace0.bzl
  • Updated the urls attribute for the googleapis http_archive to point to the new digest dc50596.
  • Updated the sha256 hash to reflect the new archive content.
  • Updated the strip_prefix to match the new digest.

Activity

• The pull request was automatically generated by Mend Renovate.
• Automerge is disabled, requiring manual merging.
• The PR is configured to rebase whenever it becomes conflicted or the rebase/retry checkbox is ticked.

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

[dpebot]

/gcbrun

[gemini-code-assist]

Code Review

This pull request updates the googleapis digest to dc50596. The changes in bazel/workspace0.bzl correctly reflect the new digest in the URL, SHA256 hash, and strip prefix. This is a routine dependency update and appears to be correct and straightforward. No further issues were found.