Nightly dependency update: OpenTelemetry 1.43.0/0.64b0#799
Nightly dependency update: OpenTelemetry 1.43.0/0.64b0#799aws-application-signals-bot wants to merge 1 commit into
Conversation
|
Claude finished @aws-application-signals-bot's task in 1m 58s —— View job Claude Code PR Review
SummaryFound one substantive issue and posted it as an inline comment on
The rest of the changes (mock-collector, contract-tests, lambda-layer tests, tox.ini upstream release branches) are internally consistent. |
| "opentelemetry-instrumentation-sqlite3 == 0.64b0", | ||
| "opentelemetry-instrumentation-starlette == 0.64b0", | ||
| "opentelemetry-instrumentation-system-metrics == 0.64b0", | ||
| "opentelemetry-instrumentation-threading == 0.63b1", |
There was a problem hiding this comment.
Missed version bump. This line was overlooked while bumping 0.63b1 → 0.64b0 for all other contrib packages. With opentelemetry-instrumentation == 0.64b0 (line 38) pinned alongside opentelemetry-instrumentation-threading == 0.63b1, pip cannot resolve the dependency tree since instrumentation-threading 0.63b1 depends on opentelemetry-instrumentation ~= 0.63b1. This is the likely cause of the failed build linked in the PR description.
| "opentelemetry-instrumentation-threading == 0.63b1", | |
| "opentelemetry-instrumentation-threading == 0.64b0", |
Automated update of OpenTelemetry dependencies.
Build Status: ❌ failure
Updated versions:
Upstream releases with breaking changes:
Note: the mechanism to detect upstream breaking changes is not perfect. Be sure to check all new releases and understand if any additional changes need to be addressed.