Restore MOT version propagation after OneSettings initialization order caused the exporter version to take precedence over the Microsoft OpenTelemetry distro version

[Radhika Gupta (rads-1996)]

…

[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	40,099.4	39,402.7	+1.77%	✅
azure_monitor_span	yes	288,142.9	289,855.1	-0.59%	✅
otel_log	no	47,682.6	47,276.9	+0.86%	✅
otel_span	no	88,912.6	85,631.1	+3.83%	✅

[Copilot]

Copilot review overview

🟡 Changes recommended

Add regression coverage verifying the configuration manager receives the distro version.

Get a fresh assessment by requesting another Copilot review.

Review effort: Lite
Findings: 1

Open (1)

• Add regression test for exporter version import precedence · New

What changed in this PR

Restores Microsoft OpenTelemetry distro version precedence during OneSettings initialization.

Changes:

• Reorders initialization so the distro version is set before configuration loading.
• Adds an unreleased changelog entry.

File	Summary
src/​microsoft/​opentelemetry/​_distro.py	Ensures version propagation precedes OneSettings initialization.
CHANGELOG.md	Documents the version propagation fix.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.