Upgrade OpenTelemetry packages to 0.56b0 with SDK 1.36.0 and azure-monitor-opentelemetry to 1.6.13

[Copilot]

Fix Dependabot upgrade for opentelemetry-instrumentation-urllib

This PR addresses the CI failure in Dependabot PR #2602 which tried to upgrade opentelemetry-instrumentation-urllib from 0.52b1 to 0.56b0.

Problem Analysis

The issue occurred because:

• opentelemetry-instrumentation-urllib is a transitive dependency of azure-monitor-opentelemetry
• Upgrading only this one package while leaving others at 0.52b1 creates version incompatibilities
• The dependency conflict was: azure-monitor-opentelemetry==1.6.13 requires opentelemetry-sdk>=1.36.0,<1.37.dev0 but we had opentelemetry-sdk==1.31.1

Solution Implemented ✅

This PR upgrades all necessary packages to compatible versions:

• azure-monitor-opentelemetry: 1.6.1 → 1.6.13 (supports newer OpenTelemetry ecosystem)
• OpenTelemetry SDK & API: 1.31.1 → 1.36.0 (to satisfy azure-monitor-opentelemetry 1.6.13 requirements)
• All OpenTelemetry instrumentation packages: 0.52b1 → 0.56b0
• OpenTelemetry semantic conventions & utilities: 0.52b1 → 0.56b0

Changes Made

1. app/backend/requirements.in: Updated azure-monitor-opentelemetry>=1.6.13 to support newer OpenTelemetry versions
2. app/backend/requirements.txt: Comprehensive upgrade of:
   • OpenTelemetry core packages (SDK, API) from 1.31.1 to 1.36.0
   • All opentelemetry-instrumentation-* packages from 0.52b1 to 0.56b0
   • opentelemetry-semantic-conventions and opentelemetry-util-http from 0.52b1 to 0.56b0

Technical Details

• Root Cause: azure-monitor-opentelemetry 1.6.13 has strict dependency requirements that weren't satisfied by the previous partial upgrade
• Dependency Resolution: Upgrading the core OpenTelemetry packages (SDK/API) to 1.36.0 satisfies azure-monitor-opentelemetry requirements while maintaining compatibility with 0.56b0 instrumentation packages
• Future Compatibility: Enables future Dependabot upgrades to work seamlessly by maintaining a consistent OpenTelemetry ecosystem

This approach follows best practices of upgrading dependencies rather than constraining them, ensuring the entire OpenTelemetry ecosystem remains consistent and up-to-date.

Fixes #2637.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[pamelafox]

@copilot Upgrade all the necessary packages instead of pinning lower version for one.

[Copilot]

@copilot Upgrade all the necessary packages instead of pinning lower version for one.

You're absolutely right! I've changed the approach from pinning a lower version to properly upgrading all necessary packages.

The solution now:

• Upgrades azure-monitor-opentelemetry from 1.6.1 to 1.6.13
• Upgrades all OpenTelemetry instrumentation packages from 0.52b1 to 0.56b0
• Removes the previous constraint that was blocking upgrades

This resolves the original Dependabot issue by ensuring all OpenTelemetry packages are at compatible versions rather than constraining individual packages. Commit: 4737f94

Warning

Firewall rules blocked me from connecting to one or more addresses

I tried to connect to the following addresses, but was blocked by firewall rules:

• astral.sh
  • Triggering command: curl -LsSf REDACTED (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

[pamelafox]

@copilot Error

Run uv pip install -r requirements-dev.txt
× No solution found when resolving dependencies:
╰─▶ Because azure-monitor-opentelemetry==1.6.13 depends on
opentelemetry-sdk>=1.36.0,<1.37.dev0 and you require
azure-monitor-opentelemetry==1.6.13, we can conclude that you require
opentelemetry-sdk>=1.36.0,<1.37.dev0.
And because you require opentelemetry-sdk==1.31.1, we can conclude that
your requirements are unsatisfiable.

[Copilot]

@copilot Error

Run uv pip install -r requirements-dev.txt
...

Fixed the dependency conflict by upgrading OpenTelemetry SDK from 1.31.1 to 1.36.0. The issue was that azure-monitor-opentelemetry 1.6.13 requires opentelemetry-sdk>=1.36.0, but we had SDK at 1.31.1. The solution upgrades both the SDK and API to 1.36.0 while keeping all instrumentation packages at 0.56b0 as originally planned. Commit: a932931