Make validate credentials max tokens configurable

[Yeuoly]

Summary

• allow overriding validate credential ping max_tokens via validate_credentials_max_tokens credential value with default fallback
• keep stream validation default max_tokens at 10 (per PR feat: add minimum_dify_version field to PluginConfiguration for version validation #93) but allow overriding via credentials when specified
• bump SDK version to 0.7.1

Testing

• Not run (not requested)

---

Codex Task

[gemini-code-assist]

Summary of Changes

Hello @Yeuoly, 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 introduces greater flexibility in the credential validation process for OpenAI-compatible LLMs by making the max_tokens parameter configurable. Users can now specify a custom max_tokens value for both standard and streaming credential validation pings, allowing for more tailored validation behavior. Additionally, the Dify Plugin SDK version has been incremented to 0.7.1.

Highlights

• Configurable max_tokens for credential validation: The max_tokens parameter used during the validate_credentials ping can now be overridden via a validate_credentials_max_tokens credential value, with a default fallback of 5.
• Stream validation max_tokens override: The default max_tokens for stream validation remains at 10 (as per PR feat: add minimum_dify_version field to PluginConfiguration for version validation #93), but it can now also be overridden through the validate_credentials_max_tokens credential.
• SDK Version Bump: The Dify Plugin SDK version has been updated from 0.7.0 to 0.7.1.

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

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 makes the max_tokens for credential validation configurable, with different defaults for streaming and non-streaming modes. The changes look good and address the goal. I've added a couple of minor suggestions to improve the readability and consistency of how the new configuration value is retrieved. The version bumps for the SDK are also included as described.