Is 0.5.3 intentional for 1.13.3, or should we use 0.5.4-local?

[scdeng]

Self Checks

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

1. Is this request related to a challenge you're experiencing? Tell me about your story.

Dify 1.13.3’s docker-compose still uses langgenius/dify-plugin-daemon:0.5.3-local, while dify-plugin-daemon repo is at 0.5.4. Git history shows #33526 bumped compose to 0.5.4-local, then #34079 (1.13.3) reverted it to 0.5.3-local without explanation in the commit message.

2. Additional context or comments

No response

[dosubot[bot]]

The revert to 0.5.3-local in Dify 1.13.3 was intentional. PR #34079 includes an explicit commit titled fix: restore sandbox runtime compatibility that rolled back the plugin daemon version across all Docker Compose files [1].

Plugin daemon 0.5.4 introduced at least two confirmed regressions:

1. Broken agent tool calling — 0.5.4 added strict JSON validation that rejects content: null in PromptMessage.UnmarshalJSON(). Since LLM providers return content: null during function calls, this broke all agent tool usage with unmarshal json failed: content field is required .
2. Plugin dependency installation failures — 0.5.4 caused failed to install dependencies: failed to start command: context canceled errors during plugin installation [2].

So 0.5.3-local is the correct version for 1.13.3. The original bump to 0.5.4-local in PR #33526 was merged quickly to close a 1.13.1 release blocker [3], but the new regressions it introduced required rolling it back.

To reply, just mention @dosu.

---

Share context across your team and agents. Try Dosu.