Skip to content

fix(models/gemini): lock plugin dependencies for reproducible installs#2765

Merged
WH-2099 merged 1 commit intomainfrom
fix/gemini-lockfile
Mar 19, 2026
Merged

fix(models/gemini): lock plugin dependencies for reproducible installs#2765
WH-2099 merged 1 commit intomainfrom
fix/gemini-lockfile

Conversation

@WH-2099
Copy link
Member

@WH-2099 WH-2099 commented Mar 19, 2026

Related Issues or Context

2764

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

@dosubot dosubot bot added the size:M This PR changes 30-99 lines, ignoring generated files. label Mar 19, 2026
@WH-2099 WH-2099 self-assigned this Mar 19, 2026
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello, 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 focuses on enhancing the stability and reproducibility of the Gemini plugin by meticulously locking its Python dependencies. The changes involve updating the plugin's version, refining the dependency generation process to use a more explicit uv export command, and updating a wide array of package versions to ensure a consistent and reliable environment for the plugin's operation. This ensures that the plugin can be installed and run with the exact same dependency tree across different environments.

Highlights

  • Dependency Locking and Reproducibility: The plugin's dependencies have been locked to specific versions in requirements.txt to ensure reproducible installations, aligning with best practices for dependency management.
  • Updated Dependency Generation Command: The pyproject.toml file now reflects the use of uv export with specific flags (--format requirements.txt --no-dev --no-hashes --frozen --no-emit-project) for generating the requirements.txt file, replacing the older uv pip compile command.
  • Plugin Version Bump: The Gemini plugin's version has been incremented from 0.7.17 to 0.7.18 in manifest.yaml.
  • Dependency Updates: Numerous direct and transitive dependencies within requirements.txt have been updated to their latest compatible versions, including anyio, certifi, cryptography, google-api-core, google-generativeai, pydantic, and others, along with the addition of colorama and removal of setuptools.

🧠 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.

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.

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.

@WH-2099 WH-2099 deployed to models/gemini March 19, 2026 09:01 — with GitHub Actions Active
Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request aims to lock plugin dependencies for reproducible installs by using uv.lock. The changes to .gitignore to track the lock file and updating the generation command in pyproject.toml are appropriate. However, the generated requirements.txt file contains several package versions that appear to be invalid and do not exist on PyPI, which would break the installation. This critical issue needs to be addressed.

@dosubot dosubot bot added the lgtm This PR has been approved by a maintainer label Mar 19, 2026
@WH-2099 WH-2099 merged commit 0f20e5b into main Mar 19, 2026
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

lgtm This PR has been approved by a maintainer size:M This PR changes 30-99 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants