build(deps): Bump the pip group across 5 directories with 5 updates

[dependabot]

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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions
  You can disable automated security fix PRs for this repo from the Security Alerts page.

---

Summary by cubic

Update Python dependencies across the repo to pick up security and bug fixes. Applies to the root app and telemetry bridge functions; no code changes.

• Dependencies
  • Root requirements.txt: python-multipart 0.0.29, requests 2.34.2, cryptography 48.x, python-dotenv 1.2.2, aiohttp 3.13.5
  • requirements-test.txt: aiohttp 3.13.5
  • Telemetry bridge (aws_lambda, azure_function, edge_collector/collector_api, gcp_function): requests 2.33.0

^{Written for commit 89cff13. Summary will update on new commits. Review in cubic}

[augmentcode]

🤖 Augment PR Summary

Summary: This PR bumps a grouped set of Python dependencies across the root project and telemetry-bridge subcomponents.
Changes: Updates version constraints/pins for aiohttp, requests, python-multipart, python-dotenv, and cryptography in the corresponding requirements*.txt files.

_{🤖 Was this summary useful? React with 👍 or 👎}

[augmentcode]

Review completed. 1 suggestion posted.

Comment augment review to trigger a new review at any time.

[augmentcode]

requirements.txt:6: requests is now constrained to >=2.34.2,<3.0, but the telemetry bridge requirement files in this PR pin requests==2.33.0; if any build/install ever combines these requirement sets, pip will hit an unsatisfiable version conflict.

Severity: medium

Other Locations

• suite-core/telemetry_bridge/aws_lambda/requirements.txt:1
• suite-core/telemetry_bridge/azure_function/requirements.txt:2
• suite-core/telemetry_bridge/edge_collector/collector_api/requirements.txt:4
• suite-core/telemetry_bridge/gcp_function/requirements.txt:2

_{🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.}

[cubic-dev-ai]

1 issue found across 6 files

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="requirements.txt">

<violation number="1" location="requirements.txt:6">
P2: Version conflict: `requests>=2.34.2,<3.0` here is incompatible with the `requests==2.33.0` pin in the telemetry bridge requirement files (`suite-core/telemetry_bridge/*/requirements.txt`) updated in this same PR. If these requirement sets are ever composed (e.g., in CI or a shared venv), pip will fail with an unsatisfiable dependency error. Either bump the telemetry bridge pins to `>=2.34.2` or align this lower bound to accommodate `2.33.0`.</violation>
</file>

<sub>Reply with feedback, questions, or to request a fix.

Re-trigger cubic</sub>

[cubic-dev-ai]

P2: Version conflict: requests>=2.34.2,<3.0 here is incompatible with the requests==2.33.0 pin in the telemetry bridge requirement files (suite-core/telemetry_bridge/*/requirements.txt) updated in this same PR. If these requirement sets are ever composed (e.g., in CI or a shared venv), pip will fail with an unsatisfiable dependency error. Either bump the telemetry bridge pins to >=2.34.2 or align this lower bound to accommodate 2.33.0.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At requirements.txt, line 6:

<comment>Version conflict: `requests>=2.34.2,<3.0` here is incompatible with the `requests==2.33.0` pin in the telemetry bridge requirement files (`suite-core/telemetry_bridge/*/requirements.txt`) updated in this same PR. If these requirement sets are ever composed (e.g., in CI or a shared venv), pip will fail with an unsatisfiable dependency error. Either bump the telemetry bridge pins to `>=2.34.2` or align this lower bound to accommodate `2.33.0`.</comment>

<file context>
@@ -2,12 +2,12 @@ fastapi>=0.115,<0.128
-python-multipart>=0.0.26,<1.0
-requests>=2.33.0,<3.0
+python-multipart>=0.0.29,<1.0
+requests>=2.34.2,<3.0
 httpx>=0.27.0,<1.0
 pgmpy==0.1.24
</file context>