Self Checks

• This is only for bug report, if you would like to ask a question, please head to Discussions.
• I have searched for existing issues search for existing issues, including closed ones.
• I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
• [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:)
• Please do not modify this template :) and fill in all the required fields.

Dify version

1.6.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

We attempted to upgrade our standalone deployment from Dify v1.4.1 and Plugin Daemon v0.1.0 to the newer versions Dify v1.6.0 and Plugin Daemon v0.1.3 .

However, we encountered a critical compatibility issue:No matter whether we upgrade Plugin Daemon first or Dify first, errors occur.

Steps Taken:

Upgraded Plugin Daemon first (v0.1.0 → v0.1.3) while keeping Dify at v1.4.1 → ❌ Frontend error occurred
Upgraded Dify first (v1.4.1 → v1.6.0) while keeping Plugin Daemon at v0.1.0 → ❌ Frontend error occurred

After investigation, we found that:

The /plugin/{tenantId}/management/list API endpoint in Plugin Daemon v0.1.3 has changed its response structure, which is not compatible with Dify v1.4.1

Conversely, Dify v1.6.0 expects a response format or behavior from Plugin Daemon that is not supported by v0.1.0

This creates a mutual incompatibility , where neither component can be upgraded independently without breaking the system.

✔️ Expected Behavior

A smooth and seamless upgrade process without breaking changes.

❌ Actual Behavior

Frontend errors occurred, blocking the upgrade process.