Bump aihubmix deps and version

[crazywoola]

Related Issues or Context

This PR contains Changes to Non-Plugin

• Documentation
• Other

This PR contains Changes to Non-LLM Models Plugin

• I have Run Comprehensive Tests Relevant to My Changes

This PR contains Changes to LLM Models Plugin

• My Changes Affect Message Flow Handling (System Messages and User→Assistant Turn-Taking)

• My Changes Affect Tool Interaction Flow (Multi-Round Usage and Output Handling, for both Agent App and Agent Node)

• My Changes Affect Multimodal Input Handling (Images, PDFs, Audio, Video, etc.)

• My Changes Affect Multimodal Output Generation (Images, Audio, Video, etc.)

• My Changes Affect Structured Output Format (JSON, XML, etc.)

• My Changes Affect Token Consumption Metrics

• My Changes Affect Other LLM Functionalities (Reasoning Process, Grounding, Prompt Caching, etc.)

• Other Changes (Add New Models, Fix Model Parameters etc.)

Version Control (Any Changes to the Plugin Will Require Bumping the Version)

• I have Bumped Up the Version in Manifest.yaml (Top-Level Version Field, Not in Meta Section)

Dify Plugin SDK Version

• I have Ensured dify_plugin>=0.3.0,<0.6.0 is in requirements.txt (SDK docs)

Environment Verification (If Any Code Changes)

Local Deployment Environment

• Dify Version is: , I have Tested My Changes on Local Deployment Dify with a Clean Environment That Matches the Production Configuration.

SaaS Environment

• I have Tested My Changes on cloud.dify.ai with a Clean Environment That Matches the Production Configuration

[gemini-code-assist]

Summary of Changes

Hello @crazywoola, 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 maintaining the aihubmix plugin by updating its internal version and refreshing its Python dependencies. The changes ensure that the plugin utilizes the latest stable versions of critical libraries like google-auth, google-genai, and urllib3, which can bring performance improvements, bug fixes, and security enhancements. This is a standard maintenance task to keep the plugin up-to-date with its ecosystem.

Highlights

• Plugin Version Bump: The aihubmix plugin version has been updated from 0.0.14 to 0.0.15 in its manifest file.
• New Dependency Added: The urllib3 library, version 2.6.3 or higher, has been added as a new dependency for the aihubmix plugin across pyproject.toml and requirements.txt.
• Google Dependencies Updated: The google-auth dependency has been updated to version 2.48.0 and google-genai to version 1.62.0. These updates also involved changes in their sub-dependencies, including the removal of cachetools and the addition of cryptography, distro, and sniffio.

🧠 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

• models/aihubmix/manifest.yaml
  • Updated the plugin version from 0.0.14 to 0.0.15.
• models/aihubmix/pyproject.toml
  • Added urllib3 with version 2.6.3 or higher to the project dependencies.
• models/aihubmix/requirements.txt
  • Added urllib3 with version 2.6.3 or higher to the requirements file.
• models/aihubmix/uv.lock
  • Updated google-genai dependency specification to >=1.56.0.
  • Added urllib3 as a new package dependency.
  • Removed cachetools package.
  • Added cryptography package.
  • Updated google-auth package version to 2.48.0.
  • Updated google-genai package version to 1.62.0.
  • Modified google-auth dependencies to use cryptography instead of cachetools.
  • Added distro and sniffio as dependencies for google-genai.
  • Updated google-auth dependency for google-genai to include requests extra.

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 several dependencies for the aihubmix model, including a significant version bump for google-genai. While updating dependencies is good practice, the update to google-genai introduces a critical breaking change. The library's public API has changed, and the existing code uses a now-internal class (genai.Client), which will likely cause failures. This needs to be addressed by refactoring the code to use the new recommended API.