mirror of https://github.com/langgenius/dify-plugin-sdks.git synced 2026-07-22 02:15:22 -04:00

Files

T

Harry 129c43dad0 fix: update EventConfiguration to use default_factory for parameters and enhance file_changes YAML schema

- Changed parameters in EventConfiguration to use default_factory for better initialization.
- Added parameters section in file_changes YAML to improve event documentation.

2025-10-27 11:29:30 +08:00

.mkdocs

feat: generate docs automatically (#121 )

2025-04-30 14:48:03 +08:00

.vscode

refactoring: fetch changes inside provider

2025-10-20 15:07:52 +08:00

dify_plugin

fix: update EventConfiguration to use default_factory for parameters and enhance file_changes YAML schema

2025-10-27 11:29:30 +08:00

examples

chore: update Dropbox trigger plugin version to 0.0.1

2025-10-27 11:23:07 +08:00

scripts

feat[0.3.0]: add plugin runner functionality (#144 )

2025-05-19 14:56:13 +08:00

tests

Merge remote-tracking branch 'origin/main' into feat/trigger

2025-10-20 14:39:39 +08:00

.gitignore

Merge remote-tracking branch 'origin/main' into feat/oauth-datasource

2025-07-02 14:08:12 +08:00

.ruff.toml

ci(python): Add CI Pipeline for Python SDK (#72 )

2025-04-14 20:25:19 +08:00

LICENSE

ci(python): Add CI Pipeline for Python SDK (#72 )

2025-04-14 20:25:19 +08:00

pdm.lock

refactor: enhance trigger subscription handling and improve type annotations

2025-10-11 21:09:12 +08:00

pyproject.toml

chore: bump plugin version to 0.6.0b13 and update response field in TriggerDispatchResponse model

2025-10-20 12:28:33 +08:00

README.md

docs/bump up sdk ver guide (#174 )

2025-07-09 20:17:32 +08:00

test.py

feat: implement 11 new Lark trigger events and convert JSON outputs to proper data structures

2025-10-14 16:16:50 +08:00

uv.lock

feat: implement 11 new Lark trigger events and convert JSON outputs to proper data structures

2025-10-14 16:16:50 +08:00

README.md

Dify Plugin SDK

A Python SDK for building plugins for Dify.

Version Management

This SDK follows Semantic Versioning (a.b.c):

a: Major version - Indicates significant architectural changes or incompatible API modifications
b: Minor version - Indicates new feature additions while maintaining backward compatibility
c: Patch version - Indicates backward-compatible bug fixes

For SDK Users

When depending on this SDK, it's recommended to specify version constraints that:

Allow patch and minor updates for bug fixes and new features
Prevent major version updates to avoid breaking changes

Example in your project's dependency management:

dify_plugin>=0.3.0,<0.5.0