[WH-2099]

Summary

Prepare SDK 0.11.0 from the latest main branch and upgrade runtime, development, build, and CI dependencies to their latest stable releases.

• Update runtime dependency minimums and refresh 26 packages in uv.lock, including Pydantic 2.14.1, pydantic-settings 2.15.0, gevent 26.9.0, Werkzeug 3.1.9, tiktoken 0.14.0, and Ruff 0.17.0.
• Upgrade uv_build to 0.13.0 and refresh the pinned setup-uv, upload-artifact, and download-artifact actions.
• Apply the two annotation/import changes required by the new Ruff rules.
• Set the package and lockfile version to 0.11.0.
• Improve README setup and documentation links while preserving polling guidance, version management, and historical compatibility tables; add verified 0.10.0 and 0.11.0 feature requirements, including pending Dify integration.

The changes since 0.10.2 include:

• fix(yaml)!: raise missing file errors by default #381: missing YAML files raise FileNotFoundError by default, including missing endpoint-provider declarations.
• fix(entities): add BINARY_LINK to InvokeMessage.MessageType #385: recognize BINARY_LINK tool messages.
• fix(openai-compatible): serialize image content across message roles #386: serialize OpenAI-compatible chat content across message roles and count literal special-token text safely.
• feat(datasource): add optional online-drive remote metadata #388: add optional remote metadata to online-drive files.
• feat: support reset_on_change for tool parameters #378: preserve reset_on_change tool parameter metadata.
• fix(model): preserve reasoning streams and final results #382: preserve reasoning streams, tool state, final usage, and stream errors.

0.11.0 includes the planned breaking YAML behavior from #381 and additive SDK interfaces.
Plugins must include their declared YAML files; code that intentionally reads optional YAML files can pass ignore_error=True.
The gevent runtime migration in #340 remains separate.
Refs #387 for downstream plugin rollout and user verification.

Validation

• just check: passed.
• Python 3.12 and 3.13: 277 tests passed and one skipped on each, using the identical SDK source and dependency versions; the skip requires the Dify plugin CLI.
• Clean Python 3.13 environment: installed dependencies are compatible and none are outdated.
• just build: passed for the 0.11.0 wheel and source distribution.
• Verified wheel and source-distribution versions and dependency metadata against pyproject.toml and the lockfile.
• README compatibility: checked SDK source, Dify release tags, and daemon release tags; app_id requires Dify 1.16.0, and tool multi-select requires Dify 1.16.1 plus daemon 0.5.0.
• Daemon 0.6.11 includes reset_on_change and online-drive remote metadata; Dify support remains pending, including langgenius/dify#43040 for tool parameter resets.

Release follow-up

This PR merged on October 13 and prepared the package version; SDK 0.11.0 has not been published.
Publication for Dify 1.19.0 is now tracked in #413, including later fixes through #412.
The existing release workflow verifies the tag against the package version/main, runs tests/build, creates a GitHub draft release, publishes TestPyPI, and then publishes PyPI and the GitHub release through the configured environments.
Plugin dependency updates and verified repackaging follow SDK publication.

Pull Request Checklist

Compatibility Check

• I have checked whether this change affects the backward compatibility of the plugin declared in README.md.
• I have checked whether this change affects the forward compatibility of the plugin declared in README.md.
• The breaking YAML behavior was reviewed in fix(yaml)!: raise missing file errors by default #381 for 0.11.0 and is described above.
• The compatibility impact and release version are described above.
• The package version and README setup and compatibility guidance are updated.

Available Checks

• just build has passed.
• Relevant documentation has been updated.

[Copilot]

🔵 Needs a closer look

The release combines a public version bump with broad dependency and CI action upgrades requiring final human compatibility review.

0 open findings

What changed in this PR

Prepares SDK v0.11.0 by updating package metadata, dependencies, CI tooling, compatibility guidance, and Ruff-required annotations.

Changes:

• Bumps the SDK and lockfile to 0.11.0 and refreshes dependencies.
• Updates pinned GitHub Actions and build tooling.
• Documents the breaking YAML behavior and bounded pre-1.0 upgrades.

File	Description
.github/​workflows/​mkdocs.yml	Updates setup-uv.
.github/​workflows/​pr.yml	Updates setup-uv.
.github/​workflows/​release.yml	Updates setup-uv and artifact actions.
.github/​workflows/​test.yml	Updates setup-uv.
README.md	Adds 0.11.0 upgrade guidance.
pyproject.toml	Bumps version and dependency minimums.
src/​dify_plugin/​core/​entities/​plugin/​setup.py	Adjusts the datetime import for Ruff.
src/​dify_plugin/​core/​session_context.py	Uses a precise generator annotation.
uv.lock	Refreshes resolved dependencies and package version.

🧠 Review effort: Balanced

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[Copilot]

🔵 Needs a closer look

The 0.11.0 release scope conflicts with the still-open gevent and requests removal requirements in issue #340.

0 open findings

Previously missed (1)

In code that hasn't changed since last review

0.11.0 release retains gevent and requests despite #340 criteria

pyproject.toml:9

This prepares and validates 0.11.0 while retaining/upgrading gevent, but the still-open #340 explicitly targets 0.11.0 and requires removing both gevent and requests before that release. Publishing this state would miss those acceptance criteria; either complete #340 before tagging 0.11.0 or formally retarget it and update the release scope.

🧠 Review effort: Balanced

[Copilot]

🟡 Changes recommended

The published README would contain broken relative links and identify the released SDK version as unreleased.

1 open finding

• Remove stale unreleased qualifier for SDK 0.11.0 · New

Previously missed (1)

In code that hasn't changed since last review

Use an absolute URL for the setup guidance link

README.md:36

README.md is also the package long description, so this relative target is rendered under pypi.org rather than against the GitHub repository and will be broken on the 0.11.0 project page. Use an absolute repository URL so the setup guidance works in both locations.

🧠 Review effort: Balanced