feat: API regeneration: release-2026-03-18.08-02-55#3140
Conversation
Summary of ChangesHello, I'm Gemini Code Assist1! 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 represents a routine API regeneration across several Google Cloud services. The changes primarily involve updating API discovery documents to reflect the latest API definitions, introducing new methods and data schemas, refining existing property descriptions, and expanding supported configurations like machine types and regional endpoints. The corresponding C# client libraries have been updated to align with these upstream API changes, ensuring compatibility and access to the newest features. Highlights
Using Gemini Code AssistThe 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
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 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. Footnotes
|
There was a problem hiding this comment.
Code Review
This pull request is an API regeneration, introducing new features and endpoints across several services like Alert Center, API Hub, and App Engine. The changes are mostly additions and documentation updates in the API discovery documents and the corresponding generated C# client libraries. I've found a minor documentation issue in the Natural Language API definitions where new enum values are added without corresponding descriptions, which I've commented on.
| "", | ||
| "", | ||
| "", | ||
| "", | ||
| "", | ||
| "", | ||
| "", | ||
| "", | ||
| "", | ||
| "", | ||
| "", | ||
| "", | ||
| "", | ||
| "", | ||
| "", | ||
| "", | ||
| "", | ||
| "", | ||
| "", | ||
| "", | ||
| "", | ||
| "", | ||
| "", | ||
| "", | ||
| "", | ||
| "", | ||
| "", |
There was a problem hiding this comment.
The enumDescriptions for the newly added machine_type values are all empty strings. To improve the API's usability and self-documentation, please provide meaningful descriptions for each of the new machine types. This feedback also applies to the corresponding changes in language.v1beta2.json and language.v2.json.
Changes in this PR will be published to Nuget on the next release cycle.