deps(deps): bump requests from 2.31.0 to 2.33.0

[dependabot]

Bumps requests from 2.31.0 to 2.33.0.

Release notes

Sourced from requests's releases.

v2.33.0

2.33.0 (2026-03-25)

Announcements

• 📣 Requests is adding inline types. If you have a typed code base that uses Requests, please take a look at #7271. Give it a try, and report any gaps or feedback you may have in the issue. 📣

Security

• CVE-2026-25645 requests.utils.extract_zipped_paths now extracts contents to a non-deterministic location to prevent malicious file replacement. This does not affect default usage of Requests, only applications calling the utility function directly.

Improvements

• Migrated to a PEP 517 build system using setuptools. (#7012)

Bugfixes

• Fixed an issue where an empty netrc entry could cause malformed authentication to be applied to Requests on Python 3.11+. (#7205)

Deprecations

• Dropped support for Python 3.9 following its end of support. (#7196)

Documentation

• Various typo fixes and doc improvements.

New Contributors

• @​M0d3v1 made their first contribution in psf/requests#6865
• @​aminvakil made their first contribution in psf/requests#7220
• @​E8Price made their first contribution in psf/requests#6960
• @​mitre88 made their first contribution in psf/requests#7244
• @​magsen made their first contribution in psf/requests#6553
• @​Rohan5commit made their first contribution in psf/requests#7227

Full Changelog: https://github.com/psf/requests/blob/main/HISTORY.md#2330-2026-03-25

v2.32.5

2.32.5 (2025-08-18)

Bugfixes

• The SSLContext caching feature originally introduced in 2.32.0 has created a new class of issues in Requests that have had negative impact across a number of use cases. The Requests team has decided to revert this feature as long term maintenance of it is proving to be unsustainable in its current iteration.

Deprecations

• Added support for Python 3.14.
• Dropped support for Python 3.8 following its end of support.

v2.32.4

2.32.4 (2025-06-10)

... (truncated)

Changelog

Sourced from requests's changelog.

2.33.0 (2026-03-25)

Announcements

• 📣 Requests is adding inline types. If you have a typed code base that uses Requests, please take a look at #7271. Give it a try, and report any gaps or feedback you may have in the issue. 📣

Security

• CVE-2026-25645 requests.utils.extract_zipped_paths now extracts contents to a non-deterministic location to prevent malicious file replacement. This does not affect default usage of Requests, only applications calling the utility function directly.

Improvements

• Migrated to a PEP 517 build system using setuptools. (#7012)

Bugfixes

• Fixed an issue where an empty netrc entry could cause malformed authentication to be applied to Requests on Python 3.11+. (#7205)

Deprecations

• Dropped support for Python 3.9 following its end of support. (#7196)

Documentation

• Various typo fixes and doc improvements.

2.32.5 (2025-08-18)

Bugfixes

• The SSLContext caching feature originally introduced in 2.32.0 has created a new class of issues in Requests that have had negative impact across a number of use cases. The Requests team has decided to revert this feature as long term maintenance of it is proving to be unsustainable in its current iteration.

Deprecations

• Added support for Python 3.14.
• Dropped support for Python 3.8 following its end of support.

2.32.4 (2025-06-10)

Security

• CVE-2024-47081 Fixed an issue where a maliciously crafted URL and trusted environment will retrieve credentials for the wrong hostname/machine from a netrc file.

... (truncated)

Commits

• bc04dfd v2.33.0
• 66d21cb Merge commit from fork
• 8b9bc8f Move badges to top of README (#7293)
• e331a28 Remove unused extraction call (#7292)
• 753fd08 docs: fix FAQ grammar in httplib2 example
• 774a0b8 docs(socks): same block as other sections
• 9c72a41 Bump github/codeql-action from 4.33.0 to 4.34.1
• ebf7190 Bump github/codeql-action from 4.32.0 to 4.33.0
• 0e4ae38 docs: exclude Response.is_permanent_redirect from API docs (#7244)
• d568f47 docs: clarify Quickstart POST example (#6960)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Labels

The following labels could not be found: dependencies, python. Please create them before Dependabot can add them to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

[harper-new-line]

HarperBot

The provided diff shows a consistent upgrade of the requests library across pyproject.toml, requirements.in, and several requirements-pyXX.txt files. The version is updated from 2.32.5 (or 2.31.0 in the case of requirements-py38.txt) to 2.33.0.

Analysis of Changes:

1. Correctness:

   • Upgrading to a newer minor version (2.33.0) of requests is generally safe and backward-compatible within the 2.x major release. requests is a very stable library, and minor updates typically introduce bug fixes, performance improvements, and new features without breaking existing APIs.
   • The change is applied consistently across all relevant dependency files, which is crucial for maintaining a coherent dependency tree.

2. Code Quality & Best Practices:

   • Dependency Updates: Regularly updating dependencies is a good practice. It ensures access to the latest features, bug fixes, and crucially, security patches. requests is a fundamental library, so keeping it current is important.
   • Strict Pinning (==): All dependencies are strictly pinned to a specific version (requests==2.33.0). This is excellent for reproducibility, especially for requirements.txt files used in deployment or CI/CD environments. It ensures that builds are consistent across different environments and over time.
   • Multiple requirements-pyXX.txt files: The presence of separate requirements-py314-minimal.txt, requirements-py314.txt, requirements-py38.txt, and requirements-py39.txt indicates a well-structured approach to managing dependencies across different Python versions, which is a good practice for projects supporting a range of environments.
   • pyproject.toml and requirements.in: These files serve as the primary source for direct dependencies. Updating requests here first, and then generating (or manually updating) the requirements.txt files, is the correct workflow.

3. Performance:

   • Newer versions of libraries often include performance optimizations. While a minor version bump in requests might not lead to dramatic performance gains, it's possible that underlying components or specific network operations have been optimized, contributing to minor improvements.

4. Security:

   • This is a significant positive impact. Dependency updates frequently include patches for security vulnerabilities. Keeping requests updated helps mitigate potential risks associated with older, unpatched versions of the library or its transitive dependencies (like urllib3, charset_normalizer, idna, certifi).

Suggested Improvements:

The change itself is a positive improvement. To further enhance code quality and maintainability, especially for pyproject.toml and requirements.in which serve as the primary declaration points for direct dependencies, adding a brief comment explaining the rationale for the update can be beneficial. For the generated requirements-pyXX.txt files, strict pinning without comments is standard.

pyproject.toml
@@ -4,7 +4,7 @@
 dependencies = [
     "flask==3.1.2",
     "python-dotenv==1.1.1",
-    "requests==2.32.5",
+    "requests==2.33.0", # Updated for latest bug fixes and security patches.
     "gunicorn==23.0.0",
     "flask-openapi3==4.0.0",
     "pydantic==2.12.0",

requirements.in
@@ -1,5 +1,5 @@
 flask==3.1.2
 python-dotenv==1.1.1
-requests==2.32.5
+requests==2.33.0 # Updated for latest bug fixes and security patches.
 gunicorn==23.0.


<!-- harperbot-sha: 47ae74f1746125ddae5c8e39103abc8f6c70cdf3 -->
</details>

[harper-new-line]

HarperBot Analysis for 47ae74f

[harper-new-line]

Suggested change

	"requests==2.33.0",
	"requests==2.33.0", # Updated for latest bug fixes and security patches.

[dependabot]

Superseded by #25.