[PR #2052] [MERGED] feat: update higress model plugin to v0.0.3 plugin #2041

Closed
opened 2026-02-22 18:15:15 -05:00 by yindo · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/langgenius/dify-plugins/pull/2052
Author: @EndlessSeeker
Created: 2/10/2026
Status: Merged
Merged: 2/10/2026
Merged by: @crazywoola

Base: mainHead: feat-higress-003


📝 Commits (1)

  • 84070b2 feat: add higress v0.0.3 plugin

📊 Changes

1 file changed (+0 additions, -0 deletions)

View changed files

📝 higress/model-plugin/higress-0.0.3.difypkg (+0 -0)

📄 Description

Change-Id: Ic8d8b433669fb3e8075764a9913c82b69fdb5426

Plugin Submission Form

1. Metadata

2. Submission Type

  • New plugin submission
  • Version update for existing plugin

3. Description

  • fix usage lost in llm node

4. Checklist

  • I have read and followed the Publish to Dify Marketplace guidelines
  • I have read and comply with the Plugin Developer Agreement
  • I confirm my plugin works properly on both Dify Community Edition and Cloud Version
  • I confirm my plugin has been thoroughly tested for completeness and functionality
  • My plugin brings new value to Dify

5. Documentation Checklist

Please confirm that your plugin README includes all necessary information:

  • Step-by-step setup instructions
  • Detailed usage instructions
  • All required APIs and credentials are clearly listed
  • Connection requirements and configuration details
  • Link to the repository for the plugin source code

6. Privacy Protection Information

Based on Dify Plugin Privacy Protection Guidelines:

Data Collection

This plugin does not collect personal data for its own use. It may process and forward the following data from Dify to the Higress AI Gateway Model API endpoint you configure:

Model inputs (e.g., prompts/messages/texts/documents depending on capability)
Model outputs returned by your configured endpoint
Configuration & credentials you set in Dify for this plugin (e.g., endpoint URL, API Key / HMAC key & secret, extra headers)
Optional user identifier passed by Dify to model APIs
The plugin itself does not store prompts/outputs in its own database, does not do analytics/tracking, and does not send data to any fixed third parties—data is sent only to the endpoint you configure (which may route to upstream providers based on your Higress settings).

Privacy Policy

  • I confirm that I have prepared and included a privacy policy in my plugin package based on the Plugin Privacy Protection Guidelines

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/langgenius/dify-plugins/pull/2052 **Author:** [@EndlessSeeker](https://github.com/EndlessSeeker) **Created:** 2/10/2026 **Status:** ✅ Merged **Merged:** 2/10/2026 **Merged by:** [@crazywoola](https://github.com/crazywoola) **Base:** `main` ← **Head:** `feat-higress-003` --- ### 📝 Commits (1) - [`84070b2`](https://github.com/langgenius/dify-plugins/commit/84070b28f219ee766ba0563fc95cabcbf947c715) feat: add higress v0.0.3 plugin ### 📊 Changes **1 file changed** (+0 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `higress/model-plugin/higress-0.0.3.difypkg` (+0 -0) </details> ### 📄 Description Change-Id: Ic8d8b433669fb3e8075764a9913c82b69fdb5426 # Plugin Submission Form ## 1. Metadata - **Plugin Author**: higress - **Plugin Name**: higress - **Repository URL**: https://github.com/higress-group/higress-dify-plugin ## 2. Submission Type - [ ] New plugin submission - [x] Version update for existing plugin ## 3. Description - fix usage lost in llm node ## 4. Checklist - [x] I have read and followed the Publish to Dify Marketplace guidelines - [x] I have read and comply with the Plugin Developer Agreement - [x] I confirm my plugin works properly on both Dify Community Edition and Cloud Version - [x] I confirm my plugin has been thoroughly tested for completeness and functionality - [x] My plugin brings new value to Dify ## 5. Documentation Checklist Please confirm that your plugin README includes all necessary information: - [x] Step-by-step setup instructions - [x] Detailed usage instructions - [x] All required APIs and credentials are clearly listed - [x] Connection requirements and configuration details - [x] Link to the repository for the plugin source code ## 6. Privacy Protection Information Based on Dify Plugin Privacy Protection [Guidelines](https://docs.dify.ai/plugins/publish-plugins/publish-to-dify-marketplace/plugin-privacy-protection-guidelines): ### Data Collection This plugin does not collect personal data for its own use. It may process and forward the following data from Dify to the Higress AI Gateway Model API endpoint you configure: Model inputs (e.g., prompts/messages/texts/documents depending on capability) Model outputs returned by your configured endpoint Configuration & credentials you set in Dify for this plugin (e.g., endpoint URL, API Key / HMAC key & secret, extra headers) Optional user identifier passed by Dify to model APIs The plugin itself does not store prompts/outputs in its own database, does not do analytics/tracking, and does not send data to any fixed third parties—data is sent only to the endpoint you configure (which may route to upstream providers based on your Higress settings). ### Privacy Policy - [x] I confirm that I have prepared and included a privacy policy in my plugin package based on the Plugin Privacy Protection Guidelines --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
yindo added the pull-request label 2026-02-22 18:15:15 -05:00
yindo closed this issue 2026-02-22 18:15:18 -05:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify-plugins#2041