fix(deps): drop phantom starlette==1.0.0 pin, regenerate lockfile#54
Merged
Conversation
The previous requirements.txt pinned starlette==1.0.0 (not a real PyPI release). After mlflow-skinny 3.12.0 landed (#47) with its starlette<1 cap, deploys started failing at install time with an unresolvable conflict (fastapi>=0.46.0, mcp>=0.27, mlflow-skinny<1) plus "no matching distributions available for starlette==1.0.0". Re-ran `uv pip compile pyproject.toml -o requirements.txt` — resolver picks starlette==0.52.1, which satisfies all three constraints. Verified by installing the full lockfile into a clean Python 3.11 venv (matches the Databricks Apps runtime) and running `uv pip check`: all 67 packages compatible.
This was referenced May 20, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
requirements.txtwas pinningstarlette==1.0.0— a version that doesn't exist on PyPI. The lockfile was last generated before chore(deps): bump mlflow-skinny from 3.11.1 to 3.12.0 #47 bumpedmlflow-skinnyto3.12.0, which added a newstarlette<1cap on top of the conflict.uv pip compile pyproject.toml -o requirements.txt. Resolver settles onstarlette==0.52.1, which satisfies fastapi (≥0.46.0), mcp (≥0.27), and mlflow-skinny (<1).Diff
Three lines:
starlette==1.0.0→starlette==0.52.1, plus mlflow-skinny added to starlette'svialist (it now pulls starlette transitively under the new cap), plus pyproject.toml shows up under importlib-metadata'svialist (we already have an explicit<8.8cap there).Test plan
uv pip compile pyproject.toml -o requirements.txtsucceeds withexclude-newer = "7 days"(today: 2026-05-19)uv pip install -r requirements.txtinto a clean Python 3.11 venv installs all 67 packages with no conflictsuv pip checkreports "All installed packages are compatible"starlette,fastapi,mlflow,mcp,flask,flask_socketio,databricks.sdkall loadRUNNING