Skip to content

build(deps): bump python-multipart from 0.0.27 to 0.0.31 #28

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
haasonsaas merged 1 commit into from
Jun 20, 2026
Merged

build(deps): bump python-multipart from 0.0.27 to 0.0.31 #28

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion requirements_lock.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -214,7 +214,7 @@ python-dotenv==1.2.2
# agent-pm
# pydantic-settings
# uvicorn
python-multipart==0.0.27
python-multipart==0.0.31

@cursor cursor Bot Jun 16, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lock files pin different versions

Medium Severity

This PR bumps python-multipart to 0.0.31 only in requirements_lock.txt, but uv.lock still resolves python-multipart at 0.0.27. Docker and uv sync follow uv.lock, while Bazel uses requirements_lock.txt, so the upgrade does not apply consistently and make bazel-check can regenerate and revert this file.

Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit dbc5e11. Configure here.

# via mcp
pytz==2025.2
# via
Expand Down
Loading