chore(internal): version bump

[shaeenhaque]

• I understand that this repository is auto-generated and my pull request may not be merged

Changes being requested

Additional context & links

[gemini-code-assist]

Summary of Changes

Hello @shaeenhaque, 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 represents a significant leap forward for the library, primarily driven by a major version increment. The core focus has been on expanding the API surface to expose new functionalities and refining existing ones, alongside a substantial cleanup of deprecated features and internal tooling. These changes aim to provide a more robust, feature-rich, and streamlined experience for developers, aligning the library with the latest API capabilities and best practices.

Highlights

• Major Version Bump: The library version has been updated from 1.30.1 to 1.107.2, indicating a substantial release with numerous changes.
• API Surface Expansion and Refactoring: The API surface has been significantly expanded with new endpoints and types across various domains including Chat Completions, Files, Images, Audio, Moderations, Fine-tuning, Batches, Uploads, Responses, Realtime, Conversations, Evals, and Containers. Many existing beta APIs (like Vector Stores) have been moved out of the beta namespace, and new methods have been added to existing resources. This includes new methods for retrieving, updating, listing, and deleting chat completions, as well as new capabilities for file search results in run steps.
• Dependency and Environment Updates: The minimum Python version requirement has been raised from 3.7+ to 3.8+. Key dependencies like typing-extensions have been updated, and cached-property and tqdm are no longer direct dependencies. The development environment now uses Rye with --all-features for dependency management, and Node.js is included in the devcontainer. Configuration for pyright and ruff has been updated, and black and isort are no longer explicitly used for formatting, relying solely on ruff format.
• Removal of Deprecated Features and Examples: All example files have been removed from the repository. The module-level client and Azure-specific client (AzureOpenAI) have been removed, streamlining the client instantiation process. Several helper functions for streaming, polling, and bulk uploads have been removed from the README.md and api.md, indicating a shift in how these functionalities are exposed or recommended. Old API symbols and CLI tools have also been removed.
• Documentation and Readme Improvements: The CONTRIBUTING.md and README.md files have been updated with clearer instructions for Rye usage, code modification guidelines, and revised command examples. Copyright year in LICENSE has been updated. The SECURITY.md file has updated contact information for reporting security issues.
• Internal Tooling Enhancements: New scripts for detecting breaking changes and uploading artifacts have been added, improving the release and development workflow. Updates to scripts/mock reflect a change in the underlying Prism CLI package used for mocking.

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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

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 issue 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 is a major version bump, introducing many changes including dependency updates, refactoring of the client, removal of the CLI and Azure-specific client, and updates to the API. My review focuses on improving documentation examples and fixing a bug in request serialization. The examples in the README for basic usage are incomplete as they don't show how to process the response. I've also identified a bug where requests with no body would incorrectly send a null JSON body.