[Radhika Gupta (rads-1996)]

No description provided.

[Copilot]

🟡 Changes recommended

The dependency bumps leave uv.lock pinned below the new minimum versions with outdated dependency metadata, preventing uv sync --locked from accepting the committed lockfile.

1 open issue

• Regenerate uv.lock for the updated dependency requirements · New

What changed in this PR

Updates OpenTelemetry dependency minimums for the microsoft-opentelemetry distribution.

Changes:

• Raises the API and SDK minimums from 1.45.0 to 1.45.2.
• Raises ten instrumentation package minimums from 0.66b0 to 0.66b2, retaining the existing upper bounds.

Validation was limited to static inspection; dependency resolution and tests were not run.

File	Description
pyproject.toml	Updates API, SDK, and instrumentation dependency constraints.

_{Review effort: Balanced}

[github-actions]

Performance comparison

Threshold: regressions >15.0% on gating scenarios fail the build. Higher ops/s is better; positive Δ means the PR is slower.

Scenario	Gating	Baseline (ops/s)	Candidate (ops/s)	Δ %	Status
azure_monitor_log	yes	18,483.9	18,422.7	+0.33%	✅
azure_monitor_span	yes	157,679.0	158,428.4	-0.47%	✅
otel_log	no	21,214.3	21,377.6	-0.76%	✅
otel_span	no	39,893.1	38,672.8	+3.16%	✅

[Copilot]

🔵 Needs a closer look

The dependency minimums were raised without regenerating uv.lock, causing locked syncs to fail and frozen installs to retain versions below the new minimums.

1 open issue

• Regenerate uv.lock for the updated dependency requirements

_{Review effort: Balanced}

[Copilot]

🟢 Approval recommended

No active review issues remain for the OpenTelemetry dependency minimum updates, though dependency resolution and tests were not run.

No open issues 🎉

1 resolved since last review

• Regenerate uv.lock for the updated dependency requirements

_{Review effort: Balanced}