chore(deps): update dependency protobuf to v6.33.5 [security]

[renovate-bot]

This PR contains the following updates:

Package	Change	Age	Confidence
protobuf	==6.33.0 → ==6.33.5

GitHub Vulnerability Alerts

CVE-2026-0994

A denial-of-service (DoS) vulnerability exists in google.protobuf.json_format.ParseDict() in Python, where the max_recursion_depth limit can be bypassed when parsing nested google.protobuf.Any messages.

Due to missing recursion depth accounting inside the internal Any-handling logic, an attacker can supply deeply nested Any structures that bypass the intended recursion limit, eventually exhausting Python’s recursion stack and causing a RecursionError.

---

Configuration

📅 Schedule: Branch creation - "" (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.

[gemini-code-assist]

Summary of Changes

Hello, 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 protobuf dependency to version 6.33.5 to incorporate a critical security fix. The update mitigates a denial-of-service vulnerability related to recursion depth bypass when parsing nested google.protobuf.Any messages, enhancing the overall security posture of the project.

Highlights

• Dependency Update: Updated the protobuf dependency from version 6.33.0 to 6.33.5.
• Security Fix: Addressed CVE-2026-0994, a denial-of-service vulnerability in google.protobuf.json_format.ParseDict() that allowed bypassing the max_recursion_depth limit.

Changelog

• requirements.txt
  • Updated the protobuf package version to 6.33.5.
  • Refreshed the SHA256 hashes corresponding to the new protobuf version.

Activity

• This pull request was automatically generated by renovate-bot.
• Automerge is disabled, requiring manual review and merging.

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 protobuf dependency to version 6.33.5 to patch a security vulnerability (CVE-2026-0994). The changes in requirements.txt correctly update the version and associated hashes. A review comment has been added to suggest a more robust way of managing this transitive dependency pin to improve long-term maintainability.

_{Note: Security Review has been skipped due to the limited scope of the PR.}

[gemini-code-assist]

While pinning protobuf to version 6.33.5 here correctly addresses the security vulnerability, this requirements.txt file is auto-generated by pip-compile. Having a bot edit it can lead to these changes being accidentally overwritten if a developer regenerates the file from requirements.in without being aware of this security pin.

A more robust approach would be to specify the constraint in requirements.in. You could add protobuf>=6.33.5 to requirements.in and regenerate requirements.txt. This makes the security fix explicit in your primary dependency file and ensures it's preserved across regenerations.