Skip to content

build(deps): bump gunicorn from 22.0.0 to 25.3.0 #18

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

Closed
dependabot wants to merge 1 commit into from
Closed

build(deps): bump gunicorn from 22.0.0 to 25.3.0 #18

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.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ python-dotenv==1.2.2
Flask==3.1.3
Flask-Limiter==3.8.0
twilio==9.10.5
gunicorn==22.0.0
gunicorn==25.3.0
Copy link
Copy Markdown

@cursor cursor Bot Apr 22, 2026

Choose a reason for hiding this comment

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

Lock files not updated, CI will fail

Medium Severity

requirements.txt bumps gunicorn to 25.3.0 but both requirements.lock and requirements-dev.lock still pin gunicorn==22.0.0. The CI workflow checks that lock files are updated whenever requirements.txt changes and will exit 1 if they diverge. Even if merged, CI installs from requirements-dev.lock, so the upgrade would have no effect in practice — production would still run gunicorn 22.0.0.

Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit 77e66a6. Configure here.


# Data and utilities
PyYAML==6.0.3
Expand Down
Loading