[Radhika Gupta (rads-1996)]

No description provided.

[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	21,878.5	21,666.6	+0.98%	✅
azure_monitor_span	yes	159,134.3	160,487.9	-0.84%	✅
otel_log	no	24,906.6	24,844.7	+0.25%	✅
otel_span	no	47,725.9	47,631.5	+0.20%	✅

[Copilot]

🟡 Changes recommended

The release bump to 1.6.0 leaves uv.lock recording version 1.5.0, so the stale lockfile must be regenerated and committed for uv sync --locked.

1 open issue

• Regenerate uv.lock for the 1.6.0 release · New

What changed in this PR

Prepares the Microsoft OpenTelemetry Python distribution for release 1.6.0.

Changes:

• Updates package metadata and the runtime version to 1.6.0.
• Converts the unreleased changelog section into the dated 1.6.0 release entry.

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

File	Description
src/​microsoft/​opentelemetry/​_version.py	Sets the runtime version to 1.6.0.
pyproject.toml	Sets the package version to 1.6.0.
CHANGELOG.md	Dates the 1.6.0 release as November 5, 2026.

_{Review effort: Balanced}

[Copilot]

🟡 Changes recommended

The exporter version bump conflicts with the CI workflow pin, blocking all three Agent365 storage jobs before tests run, and the stale lockfile prevents locked synchronization.

2 open issues

• Update PR validation to install the compatible exporter version · New
• Regenerate uv.lock for the 1.6.0 release

_{Review effort: Balanced}

[Copilot]

🔵 Needs a closer look

The stale lockfile conflicts with the updated manifest, causing locked synchronization to fail and frozen synchronization to retain an exporter below the new minimum.

1 open issue

• Regenerate uv.lock for the 1.6.0 release

1 previously missed issue

In code that hasn't changed since last review

Regenerate uv.lock to match the updated manifest

pyproject.toml:26

[P2] uv.lock still resolves exporter 1.0.0b58, records the old ~=1.0.0b58 requirement, and identifies the project as 1.5.0 (uv.lock:1038,2723,2793). Locked synchronization rejects this stale lockfile, while frozen synchronization retains an exporter below the new minimum. Regenerate the complete lockfile using the index procedure in CONTRIBUTING.md:27–37 so the release metadata, resolved versions, and artifacts match the manifest. Confidence: 99%

1 resolved since last review

• Update PR validation to install the compatible exporter version

_{Review effort: Balanced}

[Copilot]

🟢 Approval recommended

No active review issues block the changes preparing the distribution for release 1.6.0.

No open issues 🎉

1 resolved since last review

• Regenerate uv.lock for the 1.6.0 release

_{Review effort: Balanced}