Repository navigation
Conversation
|
Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting |
Bumps [go.opentelemetry.io/otel/trace](https://github.com/open-telemetry/opentelemetry-go) from 1.43.0 to 1.47.0. - [Release notes](https://github.com/open-telemetry/opentelemetry-go/releases) - [Changelog](https://github.com/open-telemetry/opentelemetry-go/blob/main/CHANGELOG.md) - [Commits](open-telemetry/opentelemetry-go@v1.43.0...v1.47.0) --- updated-dependencies: - dependency-name: go.opentelemetry.io/otel/trace dependency-version: 1.47.0 dependency-type: indirect ... Signed-off-by: dependabot[bot] <[email protected]>
64e8191 to
a16a228
Compare
Updating tracing APIs alone leaves older SDKs selected in the telemetry modules. Those SDKs allow valid replacement-character runes to bypass attribute value length limits. Pin the SDK and metric SDK to 1.47.0 in both modules and regenerate their dependency metadata. Preserve the compression fix and workspace alignment already merged into the base branch.
bgentry
left a comment
There was a problem hiding this comment.
🤖 Codex review: Approved after dependency security and compatibility review of final head 111f47b14afd266f180b71a7b4e5366e074b8ffd.
Upgrade and repair
OpenTelemetry API/trace/metric 1.43.0 → 1.47.0 in datadogriver; selected SDK/metric SDK 1.43.0 → 1.47.0 there and explicit SDK/metric SDK 1.45.0 → 1.47.0 in otelriver. The current PR description includes the complete version table. Commit 111f47b14afd appends the SDK alignment after preserving Dependabot's rebase and the merged compression/workspace fixes.
Security review
Exact old/new archive and go.mod identities match the standard Go proxy/checksum database and pinned sums. The ledger covers 31 artifact identities and the applicable old/new source pairs, including inherited base changes. No same-version sum rewrite, fork, unexpected hook, credential harvesting, or unexplained external execution surface. New metric/x and x/sys graph selections and removed obsolete sum entries are reviewed.
GHSA-q7gw-24fr-5p69 is fixed in 1.47.0: valid replacement-character runes no longer bypass attribute-value length limits. The initial trace-only update leaves older SDKs selected; explicit SDK alignment closes that gap in both modules. Actual import analysis places SDK/SDK-metric use in dependency tests rather than datadogriver runtime packages; no unsupported runtime-exploit claim is made.
Compatibility verification
Final combined tree 4a4d354c4c48be26a633685463bca117ab2676dc: all five workspace race suites pass against isolated PostgreSQL; CI-pinned golangci-lint 2.11.4 with Go 1.26.8 reports 0 issues in all five modules; GOWORK=off go mod verify and go mod tidy -diff pass in both changed modules. Shared linter-runner contention is resolved by normal runner serialization, not check suppression.
Dependabot rebases while verification completes. Its exact repaired Git tree is proven identical to the fully tested snapshot, so unchanged artifact evidence and tree-specific results are reused rather than rerunning identical inputs. The final normal fast-forward push preserves the rebase; current-head CI build/test, lint, both CodeQL analyses and aggregate CodeQL pass. No history rewrite, force push, or policy bypass.
Residual risk
A source/integrity and consumer review does not prove absence of all upstream defects. Unused dependency-test/log graph entries are distinguished from linked application packages. No remaining blocker identified for the retained API/SDK update.
🤖 The Datadog and OpenTelemetry integrations now select OpenTelemetry 1.47.0 APIs and SDKs, fixing GHSA-q7gw-24fr-5p69. Attribute values containing valid U+FFFD replacement characters can bypass older SDK length limits. Updating trace APIs alone leaves the affected SDKs selected, so align the SDK and metric SDK in both modules as well.
The Datadog module's Go requirement aligns with the workspace's Go 1.26 floor. Preserve the compression security fix and workspace cleanup already on the base branch. The SDK appears through dependency tests rather than the Datadog runtime import path; this change fixes the selected graph without overstating runtime reachability.
1.43.01.47.01.43.01.47.01.43.01.47.01.43.01.47.01.43.01.47.01.45.01.47.01.45.01.47.0