chore(release): publish Plugin SDK v0.11.0 for Dify 1.19 #413

Publish dify-plugin==0.11.0 so the SDK fixes planned for Dify 1.19.0 can be consumed from released artifacts.
Target product milestone: Dify 1.19.0.

Current status — 2026-11-02

• Prepare package version 0.11.0 in chore(release): prepare v0.11.0 #391.
• Merge the SDK fixes listed below, including fix(model): validate responses and stabilize token estimates #412.
• Merge fix(model): validate responses and stabilize token estimates #412 on 2026-11-02 (99ada637), covering response validation and stable token estimates.
• Upgrade dependencies and CI Actions in chore(deps): refresh SDK dependencies and CI actions #408, approved and merged on 2026-11-02 (6fb518bc).
• Publish the GitHub release and PyPI wheel/source distribution.

The latest public GitHub release and PyPI version are still 0.10.2.
Merging #391 updated release metadata; it did not publish 0.11.0.

Release scope — updated 2026-11-02

SDK 0.11.0 includes the merged SDK fixes and dependency refresh in #408.
It retains the existing HTTP clients and gevent runtime.

Native synchronous HTTPX2 (#414 / #415) and removal of gevent/import-time monkey patching (#340) are scheduled for the separate SDK 0.12.0 milestone.
Those changes are deferred from SDK 0.11.0 and are not prerequisites for this publication.
#415 remains a draft for SDK 0.12.0.

Priority work for Dify 1.19

Delivery and acceptance tracking: #366, #387, #389, #394, #397, #398, #399, #400, #401, and #409.
Generate the final release notes from all changes since v0.10.2, including the additional interfaces and dependency changes recorded in #391 and subsequent merged work.

Publication checklist

• Confirm the final release commit includes the intended fixes and document the SDK 0.11 compatibility changes in the release notes.
• Run just check, just test, and just build on that commit and verify Python 3.12/3.13 CI.
• Publish the v0.11.0 tag/GitHub release and dify-plugin==0.11.0 to PyPI through the repository release workflow.
• Install the published wheel in a clean environment and verify its version, import, and representative message/response contracts.
• Record release links and artifact hashes here, then update the linked delivery trackers.

Current main 6fb518bc includes #412 and the dependency refresh in #408.
The #408 candidate passed 1,803 tests and coverage gates on Python 3.12 and 3.13, plus just check, just build, and CodeQL.
Its merged tree matches the validated candidate.
All 54 resolved Python dependencies were checked against current stable PyPI versions; 16 packages and the build backend were updated, together with CI Action pins.

Earlier #412 protocol comparisons remain recorded in that PR.
Any additional change to the selected release commit needs the relevant checks before publication.

Dify 1.19 rollout dependencies

langgenius/dify#41092 and #44502 track complete Agent messages and restored history.
Their Graphon candidate must be refreshed and replaced with the selected production dependency before rollout.

Official plugins #4034 supplies the provider/Agent complete-call and signed-replay changes needed by that host path.
Its OpenAI-compatible SDK upgrade must incorporate the response-hook adaptation in #4156: #411 now supplies tools to the response hooks.
Replace review Git pins with the published SDK, reconcile overlapping files/locks, and verify the resulting plugin archives before declaring those delivery tasks complete.
OpenAI/endpoint #4035 remains a separate downstream SDK adoption task; no independent Dify 1.19 release blocker has been established for that PR.

langgenius/dify-plugin-daemon#828 remains an external transport dependency for the complete replay path.
Daemon issues and PRs are not assigned to a 1.19 milestone by this tracking update.

Publishing the SDK makes the package available; installed plugins receive it when their own packages are rebuilt and upgraded.
Close this issue after SDK artifacts are published and verified, while retaining outstanding plugin/deployment acceptance in the linked issues.
Live vendor inference and verification in the original reporter's deployment remain unverified.