chore(models/openrouter): sync dependencies

[Stream29]

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 @Stream29, 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 maintenance for the openrouter model by updating and synchronizing its Python dependencies. The primary goal is to ensure the model's environment is aligned with the latest dify-plugin SDK, leading to a cleaner and more efficient dependency management setup. This change helps maintain the stability and compatibility of the openrouter integration within the Dify ecosystem.

Highlights

• Dependency Synchronization: The requirements.txt file for the openrouter model has been significantly updated to synchronize its dependencies. This involved removing a large number of explicitly pinned transitive dependencies and streamlining the list to primarily include dify-plugin and sniffio.
• Dify Plugin SDK Update: The required version of the dify-plugin SDK has been updated from >=0.3.0,<0.6.0 to >=0.5.0,<0.6.0, ensuring compatibility with the latest SDK features and fixes.

🧠 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/openrouter/requirements.txt
  • Updated dify-plugin version from >=0.3.0,<0.6.0 to >=0.5.0,<0.6.0.
  • Removed numerous transitive dependencies, streamlining the requirements.txt file.

Activity

• The pull request description includes a comprehensive checklist for various types of changes and testing, indicating a structured approach to development and review.
• No human comments or reviews have 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 dependencies for the OpenRouter model plugin. The main change is in requirements.txt, where the list of pinned dependencies has been drastically shortened. While the intent to sync dependencies is clear, the current implementation replaces a dependency lock file with a list of abstract dependencies. This is a critical issue that can lead to non-reproducible builds and environment-specific bugs. My review comment provides details on how to fix this by regenerating the lock file. It's crucial to use a lock file for applications and plugins to ensure stability across different environments.

[gemini-code-assist]

This change replaces a fully pinned dependency lock file with a file containing only direct, abstract dependencies. This is a significant regression for reproducibility. A requirements.txt file for an application or plugin should be a lock file to ensure that the same versions of all dependencies (including transitive ones) are used in all environments (development, testing, production). This prevents "it works on my machine" issues and ensures stable deployments.

Please regenerate the lock file. Based on the comments in the previous version of this file and in pyproject.toml, you can do this by running the following command from the models/openrouter directory:

uv pip compile pyproject.toml -o requirements.txt

This will generate a complete, pinned list of all necessary dependencies.