feat: API regeneration: release-2025-11-03.09-02-30

[amanda-tarafa]

Changes in this PR will be published to Nuget on the next release cycle.

[gemini-code-assist]

Summary of Changes

Hello @amanda-tarafa, 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 updating the Google API client libraries by regenerating them with the latest API definitions. These updates include changes to descriptions, revisions, and the addition of new enums and methods, ensuring that the client libraries accurately reflect the current state of the Google APIs.

Highlights

• API Regeneration: This PR includes the regeneration of various Google API client libraries with updated discovery documents.
• Description Updates: The descriptions for the extraLocationTypes parameter have been updated to discourage its use, clarifying that it is primarily for internal usage.
• Revision Updates: The revisions for several discovery documents have been updated to reflect the latest changes in the APIs.
• Enum Additions: The androidpublisher.v3, apphub.v1, and batch.v1 discovery documents have had enums added to them.
• New Methods: The artifactregistry.v1 and authorizedbuyersmarketplace.v1 discovery documents have had new methods added to them.
• IAM Policy Updates: The biglake.v1 discovery document has had IAM policy methods added to it.

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 contains a large number of updates from an automated API regeneration process. The changes span multiple services and include new features, description clarifications, and version bumps for both the discovery documents and the generated C# client libraries. The changes appear to be consistent and correctly generated. I have one piece of feedback regarding an internal TODO that has been exposed in a public-facing API description, which should be removed.

[gemini-code-assist]

The description for this field contains an internal TODO item (TODO(b/452163887)). This should be removed from the public API definition to avoid confusion for external users.

[gemini-code-assist]

This public-facing summary for the Observed property contains an internal TODO item (TODO(b/452163887)). This should be removed from the public API definition to avoid confusion for external users. This comment is a result of the change in the source discovery document.