Pin compatible OpenTelemetry dependencies

[shuchenliu]

Summary

• pin the OpenTelemetry core and exporter packages to 1.43.0
• pin the instrumentation packages to the matching 0.64b0 cohort
• prevent fresh Docker builds from resolving incompatible release trains

Why

The telemetry extra used minimum-only constraints across tightly coupled OpenTelemetry packages. A newer core/instrumentation release train became available while Elasticsearch instrumentation remained at 0.64b0, and the pip 25.0.1 resolver failed while backtracking across those mixed versions. This blocked the CI Docker build before an image could be created.

Verification

• reproduced the original resolution failure with pip 25.0.1
• completed the exact pip wheel build successfully with pip 25.0.1 after pinning
• installed the resulting wheel set in a fresh environment and ran pip check successfully
• initialized NodeNorm telemetry with the installed package set
• ran 17 self-contained application tests successfully

[Copilot]

Copilot review overview

🟢 Approval recommended

Dependencies are aligned and verification completed successfully.

Review effort: Lite
Findings: None

What changed in this PR

Pins OpenTelemetry dependencies to compatible release trains to prevent Docker build resolver failures.

Changes:

• Pins core/exporter packages to 1.43.0.
• Pins instrumentation packages to 0.64b0.
• Documents the alignment requirement.

File	Description
pyproject.toml	Updates telemetry dependency constraints.

---

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