#25210 [Bug]: python-dotenv pinned to ==1.0.1 since v1.83.1 causes dependency conflicts for library consumers
### Check for existing issues
- [X] I have searched the existing issues and checked that my issue is not a duplicate.
### What happened?
Since `litellm==1.83.1`, the `python-dotenv` dependency changed from `>=0.2.0` to an exact pin `==1.0.1` in `pyproject.toml` ([commit 5f63873d](https://github.com/BerriAI/litellm/commit/5f63873dcad12d0aee51eabc974273eda5278205)). This makes litellm uninstallable alongside any library that requires `python-dotenv>=1.1.0` (e.g. `fastmcp[tasks]==3.2.0`).
Exact pins in published package metadata propagate to every consumer's resolver — reproducible Docker builds should use a lockfile instead.
### Steps to Reproduce
1. `uv add litellm==1.83.3 "fastmcp[tasks]==3.2.0"` 2. Resolution fails immediately
### Relevant log output
```shell × No solution found when resolving dependencies: ╰─▶ Because fastmcp==3.2.0 depends on python-dotenv>=1.1.0 and litellm==1.83.3 depends on python-dotenv==1.0.1, we can conclude that litellm==1.83.3 and fastmcp[tasks]==3.2.0 are incompatible. ```
### What part of LiteLLM is this about?
SDK (litellm Python package)
### What LiteLLM version are you on ?
1.83.1, 1.83.2, 1.83.3
### Twitter / LinkedIn details
…