{Packaging} Bump requests to 2.32.4#31708
Conversation
️✔️AzureCLI-FullTest
|
️✔️AzureCLI-BreakingChangeTest
|
|
Thank you for your contribution! We will review the pull request and get back to you soon. |
|
The git hooks are available for azure-cli and azure-cli-extensions repos. They could help you run required checks before creating the PR. Please sync the latest code with latest dev branch (for azure-cli) or main branch (for azure-cli-extensions). pip install azdev --upgrade
azdev setup -c <your azure-cli repo path> -r <your azure-cli-extensions repo path>
|
| python-dateutil==2.8.0 | ||
| requests-oauthlib==1.2.0 | ||
| requests[socks]==2.32.3 | ||
| requests==2.32.4 |
There was a problem hiding this comment.
I split requests[socks] to requests and PySocks, so the dependabot can automatically create PR for us when it contains CVE. For example: #31669
extras_require={
"security": [],
"socks": ["PySocks>=1.5.6, !=1.5.7"],
Ref: https://github.com/psf/requests/blob/91a3eabd3dcc4d7f36dd8249e4777a90ef9b4305/setup.py#L100
| PyJWT==2.4.0 | ||
| PyNaCl==1.5.0 | ||
| pyOpenSSL==25.0.0 | ||
| PySocks==1.7.1 |
There was a problem hiding this comment.
Do we directly rely on PySocks? What is the problem if PySocks==1.7.1 is installed via requests[socks]?
There was a problem hiding this comment.
|
Please release a new version with this security issue fixed |
(cherry picked from commit 5ed9bdd)
Description
Close #31704
History Notes
[Core] Resolve CVE-2024-47081