langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-21 03:55:25 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

[PR #22251] fix(plugin): introduce response_type parameter in plugin list API to enable paginated response support #29877

New Issue
Closed
opened 2026-02-21 20:46:25 -05:00 by yindo · 0 comments
yindo commented 2026-02-21 20:46:25 -05:00
Owner
Copy Link
Copy Source

Original Pull Request: https://github.com/langgenius/dify/pull/22251

State: closed
Merged: Yes

Important

  1. Make sure you have read our contribution guidelines
  2. Ensure there is an associated issue and you have been assigned to it
  3. Use the correct syntax to link this PR: Fixes #<issue number>.

Summary

Fixes https://github.com/langgenius/dify/issues/22250

During the upgrade process, we encountered an error (reference issue: xxx). I resolved this by introducing a new response_type parameter in the Plugin Daemon.

Fix Details:

  1. Added an optional response_type parameter to the /plugin/{tenantId}/management/list API:
  • If response_type=paged is specified, the endpoint returns a paginated response.
  • Otherwise, it returns the legacy non-paginated format, ensuring backward compatibility with older versions of Dify.
  1. In Dify v1.6.0, the response_type=paged parameter is now included by default when calling this endpoint, aligning it with the updated Plugin Daemon behavior.

Recommended Upgrade Paths:

  • For users who have not yet upgraded:

It's recommended to upgrade Plugin Daemon first, followed by Dify. This ensures a smooth and error-free transition.

  • For users who have already upgraded:

You should first upgrade Dify to v1.6.0 before upgrading Plugin Daemon, to ensure compatibility between components.

Screenshots

Before After
dify_error No Error

Checklist

  • This change requires a documentation update, included: Dify Document
  • I understand that this PR may be closed in case there was no previous discussion or issues. (This doesn't apply to typos!)
  • I've added a test for each change that was introduced, and I tried as much as possible to make a single atomic change.
  • I've updated the documentation accordingly.
  • I ran dev/reformat(backend) and cd web && npx lint-staged(frontend) to appease the lint gods
**Original Pull Request:** https://github.com/langgenius/dify/pull/22251 **State:** closed **Merged:** Yes --- > [!IMPORTANT] > > 1. Make sure you have read our [contribution guidelines](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) > 2. Ensure there is an associated issue and you have been assigned to it > 3. Use the correct syntax to link this PR: `Fixes #<issue number>`. ## Summary Fixes https://github.com/langgenius/dify/issues/22250 During the upgrade process, we encountered an error (reference issue: xxx). I resolved this by introducing a new response_type parameter in the Plugin Daemon. **Fix Details:** 1. Added an optional response_type parameter to the /plugin/{tenantId}/management/list API: - If response_type=paged is specified, the endpoint returns a paginated response. - Otherwise, it returns the legacy non-paginated format, ensuring backward compatibility with older versions of Dify. 2. In Dify v1.6.0, the response_type=paged parameter is now included by default when calling this endpoint, aligning it with the updated Plugin Daemon behavior. **Recommended Upgrade Paths:** - **For users who have not yet upgraded:** It's recommended to upgrade Plugin Daemon first, followed by Dify. This ensures a smooth and error-free transition. - **For users who have already upgraded:** You should first upgrade Dify to v1.6.0 before upgrading Plugin Daemon, to ensure compatibility between components. ## Screenshots | Before | After | |--------|-------| | <img width="432" height="239" alt="dify_error" src="https://github.com/user-attachments/assets/782a2e1d-31a2-4d85-adb7-ec64c8401777" />| No Error | ## Checklist - [ ] This change requires a documentation update, included: [Dify Document](https://github.com/langgenius/dify-docs) - [x] I understand that this PR may be closed in case there was no previous discussion or issues. (This doesn't apply to typos!) - [x] I've added a test for each change that was introduced, and I tried as much as possible to make a single atomic change. - [x] I've updated the documentation accordingly. - [x] I ran `dev/reformat`(backend) and `cd web && npx lint-staged`(frontend) to appease the lint gods
yindo added the pull-request label 2026-02-21 20:46:25 -05:00
yindo closed this issue 2026-02-21 20:46:25 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
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#29877
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?