langgenius/dify-official-plugins
1
0
Fork 0
mirror of https://github.com/langgenius/dify-official-plugins.git synced 2026-07-21 17:45:23 -04:00
Code Issues 54 Packages Projects Releases Wiki Activity

[PR #692] [MERGED] chore: update field content to update the plugin's checksum #1498

New Issue
Closed
opened 2026-02-16 10:23:07 -05:00 by yindo · 0 comments
yindo commented 2026-02-16 10:23:07 -05:00
Owner
Copy Link
Copy Source

📋 Pull Request Information

Original PR: https://github.com/langgenius/dify-official-plugins/pull/692
Author: @Nov1c444
Created: 4/10/2025
Status: ✅ Merged
Merged: 4/10/2025
Merged by: @Nov1c444

Base: main ← Head: chore/update-agent-checksum

📝 Commits (1)

  • 2e3cdac chore: update field content to update the plugin's checksum

📊 Changes

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

View changed files

📝 agent-strategies/cot_agent/manifest.yaml (+1 -1)

📄 Description

Related Issue or Context

Due to the addition of the Features field to the Agent plugin, and the fact that the previous checksum has not been updated, update the plugin to update the checksum so that Features can be properly transmitted.

Type of Change

  • Bug Fix (non-breaking change which fixes an Issue)
  • New Feature (non-breaking change which adds Functionality)
  • Breaking Change (fix or feature that may cause existing Functionality to not work as expected)
  • Documentation Update
  • Code Refactoring
  • Other

Version Control (if applicable)

  • Version bumped in Manifest.yaml (top-level Version field, not in Meta section)

Test Evidence (if applicable)

Important

Visual Proof is required for Bug Fixes, New Features, and Breaking Changes:

Screenshots or Video/GIF:

Note

For Non-LLM Models Changes:

  • Bug Fixes:
    • Show the Fix working
  • New Features:
    • Demonstrate the Functionality
  • Breaking Changes:
    • Show both Old and New Behavior

For LLM Models Changes:

  • Bug Fixes:
    • Show the Fix working with Example Inputs/Outputs
  • New Features:
    • Demonstrate the Functionality with Example Inputs/Outputs
  • Breaking Changes (requires comprehensive Testing):
    • Conversation & Interaction:
      • Message Flow Handling (System Messages and User→Assistant Turn-taking)
      • Tool Interaction Flow (Multi-round Usage and Output Handling if applicable)
    • Input/Output Handling:
      • Multimodal Input Handling (Images, PDFs, Audio, Video if applicable)
      • Multimodal Output Generation (Images, Audio, Video if applicable)
      • Structured Output Format (if applicable)
    • Metrics:
      • Token Consumption Metrics
    • Others:
      • e.g., Reasoning Process for Claude 3.7 Sonnet, Grounding for Gemini (if applicable)

Environment Verification

Important

At least one environment must be tested.

Local Deployment Environment

Local Deployment Dify Version:

  • Changes tested in a Clean Environment that matches Production Configuration

SaaS Environment

  • Testing performed on cloud.dify.ai
  • Changes tested in a Clean Environment that matches Production Configuration

🔄 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-official-plugins/pull/692 **Author:** [@Nov1c444](https://github.com/Nov1c444) **Created:** 4/10/2025 **Status:** ✅ Merged **Merged:** 4/10/2025 **Merged by:** [@Nov1c444](https://github.com/Nov1c444) **Base:** `main` ← **Head:** `chore/update-agent-checksum` --- ### 📝 Commits (1) - [`2e3cdac`](https://github.com/langgenius/dify-official-plugins/commit/2e3cdac2a55471363c6cc65d8a7933b0ef65a077) chore: update field content to update the plugin's checksum ### 📊 Changes **1 file changed** (+1 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `agent-strategies/cot_agent/manifest.yaml` (+1 -1) </details> ### 📄 Description ## Related Issue or Context Due to the addition of the Features field to the Agent plugin, and the fact that the previous checksum has not been updated, update the plugin to update the checksum so that Features can be properly transmitted. ## Type of Change <!-- Put an `x` in all the boxes that apply --> - [x] Bug Fix (non-breaking change which fixes an Issue) - [ ] New Feature (non-breaking change which adds Functionality) - [ ] Breaking Change (fix or feature that may cause existing Functionality to not work as expected) - [ ] Documentation Update - [ ] Code Refactoring - [ ] Other ## Version Control (if applicable) - [ ] Version bumped in Manifest.yaml (top-level `Version` field, not in Meta section) <!-- Version format: MAJOR.MINOR.PATCH - MAJOR (0.x.x): Reserved for Major Releases with widespread Breaking Changes - MINOR (x.0.x): For New Features or limited Breaking Changes - PATCH (x.x.0): For backwards-compatible Bug Fixes and minor Improvements - Note: Each version component (MAJOR, MINOR, PATCH) can be 2 digits, e.g., 10.11.22 --> ## Test Evidence (if applicable) > [!IMPORTANT] > Visual Proof is required for Bug Fixes, New Features, and Breaking Changes: ### Screenshots or Video/GIF: <!-- Provide your evidence here --> > [!NOTE] > For Non-LLM Models Changes: > - **Bug Fixes**: > - [ ] Show the Fix working > - **New Features**: > - [ ] Demonstrate the Functionality > - **Breaking Changes**: > - [ ] Show both Old and New Behavior > > For LLM Models Changes: > - **Bug Fixes**: > - [ ] Show the Fix working with Example Inputs/Outputs > - **New Features**: > - [ ] Demonstrate the Functionality with Example Inputs/Outputs > - **Breaking Changes** (requires comprehensive Testing): > - **Conversation & Interaction**: > - [ ] Message Flow Handling (System Messages and User→Assistant Turn-taking) > - [ ] Tool Interaction Flow (Multi-round Usage and Output Handling if applicable) > - **Input/Output Handling**: > - [ ] Multimodal Input Handling (Images, PDFs, Audio, Video if applicable) > - [ ] Multimodal Output Generation (Images, Audio, Video if applicable) > - [ ] Structured Output Format (if applicable) > - **Metrics**: > - [ ] Token Consumption Metrics > - **Others**: > - [ ] e.g., Reasoning Process for Claude 3.7 Sonnet, Grounding for Gemini (if applicable) <!-- LLM Models Test Example: --> <!-- https://github.com/langgenius/dify-official-plugins/blob/main/.assets/test-examples/llm-plugin-tests/llm_test_example.md --> ### Environment Verification > [!IMPORTANT] > At least one environment must be tested. #### Local Deployment Environment Local Deployment Dify Version: <!-- Specify your version (e.g., 1.1.3) --> - [ ] Changes tested in a Clean Environment that matches Production Configuration <!-- - Python virtual env matching Manifest.yaml & requirements.txt - No breaking changes in Dify that may affect the testing result --> #### SaaS Environment - [ ] Testing performed on cloud.dify.ai - [ ] Changes tested in a Clean Environment that matches Production Configuration <!-- - Python virtual env matching Manifest.yaml & requirements.txt --> --- <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-16 10:23:07 -05:00
yindo closed this issue 2026-02-16 10:23:07 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
bug
bug
dependencies
documentation
enhancement
good first issue
invalid
pull-request
Mirrored from GitHub Pull Request
 question
stale
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify-official-plugins#1498
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?