update bytes to 1.11.1 and cargo-audit to 0.22.1

[jadamcrain]

• Update bytes 1.10.1 -> 1.11.1 to resolve CVE-2026-25541 (integer overflow in BytesMut::reserve)
• Update cargo-audit 0.22.0 -> 0.22.1 in CI to fix CVSS v4.0 advisory parsing

[gemini-code-assist]

Summary of Changes

Hello @jadamcrain, 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 focuses on essential dependency updates to enhance both security and development tooling. It includes a critical security fix for the bytes crate, mitigating a known vulnerability, and an update to cargo-audit to improve the accuracy and compatibility of security checks within the CI system. These changes ensure the project remains secure and its automated security scanning processes are up-to-date.

Highlights

• Security Update: The bytes crate has been updated from version 1.10.1 to 1.11.1 to resolve CVE-2026-25541, which addresses an integer overflow vulnerability in BytesMut::reserve.
• CI Tooling Improvement: The cargo-audit tool used in continuous integration has been updated from 0.22.0 to 0.22.1. This update specifically fixes an issue with parsing CVSS v4.0 advisories, ensuring more accurate security scanning in the CI pipeline.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog

• Cargo.lock
  • Updated the bytes dependency from version 1.10.1 to 1.11.1.
  • The checksum for the bytes crate was updated to reflect the new version.

Ignored Files

• Ignored by pattern: .github/workflows/** (1)
  • .github/workflows/security-audit.yml

Activity

• No human activity (comments, reviews) has been recorded on this pull request yet.

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 bytes dependency to version 1.11.1. The change in Cargo.lock is correct. The PR description also mentions an update to cargo-audit in CI, which is not present in the provided diffs. While the stated reason for the bytes update is to resolve a CVE, the previous version 1.10.1 was not affected by the recent vulnerability (CVE-2024-36053). Nevertheless, keeping dependencies current is good practice. The change is approved.