Skip to content
This repository was archived by the owner on Mar 26, 2026. It is now read-only.

chore(deps): update dependency requests to v2.33.0 [security] #2597

Closed
renovate-bot wants to merge 1 commit into from
+3 −3
Closed

chore(deps): update dependency requests to v2.33.0 [security] #2597

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
6 changes: 3 additions & 3 deletions requirements.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1070,9 +1070,9 @@ pyyaml==6.0.3 \
# via
# -r requirements.in
# libcst
requests==2.32.5 \
--hash=sha256:2462f94637a34fd532264295e186976db0f5d453d1cdd31473c85a6a161affb6 \
--hash=sha256:dbba0bac56e100853db0ea71b82b4dfd5fe2bf6d3754a8893c3af500cec7d7cf
requests==2.33.0 \
--hash=sha256:3324635456fa185245e24865e810cecec7b4caf933d7eb133dcde67d48cee69b \
--hash=sha256:c7ebc5e8b0f21837386ad0e1c8fe8b829fa5f544d8df3b2253bff14ef29d7652
Comment on lines +1073 to +1075
Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist bot Mar 26, 2026

Choose a reason for hiding this comment

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

high

While updating requests to v2.33.0 is correct for addressing the security vulnerability, modifying requirements.txt directly is not the right approach for this project. This file is autogenerated from requirements.in.

Any direct changes here will be lost the next time dependencies are compiled. To ensure the update is permanent, you should add requests>=2.33.0 to requirements.in and then regenerate requirements.txt by running the pip-compile command specified at the top of this file.

This ensures that the source of dependencies is updated, not just the generated output.

References
  1. Changes to generated code should be made by updating the generator template and then regenerating the output files, rather than directly modifying the generated files.
  2. For generated code, apply fixes to the generator templates rather than patching individual output files to ensure consistency across the codebase.

# via google-api-core
rsa==4.9.1 \
--hash=sha256:68635866661c6836b8d39430f97a996acbd61bfa49406748ea243539fe239762 \
Expand Down
Loading