langgenius/dify-plugin-sdks
1
0
Fork 0
mirror of https://github.com/langgenius/dify-plugin-sdks.git synced 2026-07-22 02:15:22 -04:00
Code Issues 58 Packages Projects Releases 10 Wiki Activity

Update pydantic-settings version #26

New Issue
Closed
opened 2026-02-15 21:15:21 -05:00 by yindo · 0 comments
yindo commented 2026-02-15 21:15:21 -05:00
Owner
Copy Link
Copy Source

Originally created by @meme-dayo on GitHub (Apr 7, 2025).

My problem

The latest mcp python module requires pydantic_settings>=2.5.2
https://github.com/modelcontextprotocol/python-sdk

Other related issue:

Suggestion

pyproject.toml

-   "pydantic_settings~=2.3.4",
+   "pydantic_settings>=2.5.0",

The pydantic version been updated since 0.0.1-beta75 release. (Commits on Mar 25, 2025)
chore: update dependency constraint for pydantic

-   "pydantic~=2.8.2",
+   "pydantic>=2.8.2",

However, pydantic-settings version remains unchanged.
pydantic-settings~=2.3.4 is no longer compatible with pydantic>=2.8.2

Why >=2.5.0 ( instead of >=2.3.4)

✅I checked the pydantic-settings releases and found that pydantic_settings v2.5.0+ only supports pydantic>=2.8.2.
https://github.com/pydantic/pydantic-settings/compare/v2.4.0...v2.5.0

Note

If pydantic_settings>=2.5.0 seems too strict, consider relaxing the pydantic version requirement..

Tip

The pydantic_settings is used only following file.
https://github.com/langgenius/dify-plugin-sdks/blob/0216ed8187f46a492d75aec4351c0fe7060fe188/python/dify_plugin/config/config.py#L5
✅ I looked over pydantic-settings repository.
BaseSettings and SettingsConfigDict seems no breaking changes.

Pull request

✅ I forked the repository and created a branch named chore/update-pydantic-settings-version.
⚠️My pull request also includes an updated pdm.lock.

Warning

The plugin version should increment (to 0.0.1-beta77)

[project]
name = "dify_plugin"
version = "0.0.1-beta76"
Originally created by @meme-dayo on GitHub (Apr 7, 2025). ## My problem The latest mcp python module requires `pydantic_settings>=2.5.2` https://github.com/modelcontextprotocol/python-sdk ## Other related issue: - #18 ## Suggestion pyproject.toml ```diff - "pydantic_settings~=2.3.4", + "pydantic_settings>=2.5.0", ``` The `pydantic` version been updated since 0.0.1-beta75 release. (Commits on Mar 25, 2025) [chore: update dependency constraint for pydantic](https://github.com/langgenius/dify-plugin-sdks/commit/f1e62ad85b7c7a5f86f344cfc70ca475869d227b) ```diff - "pydantic~=2.8.2", + "pydantic>=2.8.2", ``` However, `pydantic-settings` version remains unchanged. `pydantic-settings~=2.3.4` is no longer compatible with `pydantic>=2.8.2` ### Why `>=2.5.0` ( instead of `>=2.3.4`) ✅I checked the pydantic-settings releases and found that pydantic_settings v2.5.0+ only supports `pydantic>=2.8.2`. https://github.com/pydantic/pydantic-settings/compare/v2.4.0...v2.5.0 > [!NOTE] > If `pydantic_settings>=2.5.0` seems too strict, consider relaxing the pydantic version requirement.. > [!TIP] > The `pydantic_settings` is used only following file. > https://github.com/langgenius/dify-plugin-sdks/blob/0216ed8187f46a492d75aec4351c0fe7060fe188/python/dify_plugin/config/config.py#L5 > ✅ I looked over pydantic-settings repository. > `BaseSettings` and `SettingsConfigDict` seems no breaking changes. ## Pull request ✅ I forked the repository and created a branch named `chore/update-pydantic-settings-version`. ⚠️My pull request also includes an updated `pdm.lock`. > [!WARNING] > The plugin version should increment (to 0.0.1-beta77) > ``` > [project] > name = "dify_plugin" > version = "0.0.1-beta76" > ```
yindo closed this issue 2026-02-15 21:15:21 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
documentation
enhancement
pull-request
Mirrored from GitHub Pull Request
 question
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify-plugin-sdks#26
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?