Repository navigation
chore(deps): OpenTelemetry 1.47.0, and the logger provider from the otel package - #105
Merged
Merged
Conversation
…tel package The Logs API is stable in 1.47.0 and go.opentelemetry.io/otel/log/global is deprecated: its functions now forward to go.opentelemetry.io/otel, so both names reach the same global provider. NewOTelHandler reads it with otel.GetLoggerProvider, and the comments and docs/api.md name otel.SetLoggerProvider. A binary that still installs its provider through the deprecated package keeps working. All OpenTelemetry modules move together (the exporters too, which the two dependabot PRs left at 1.45.0), with the otelslog bridge at v0.21.0. The measurement harness module follows, since it builds against this tree. Supersedes #99 and #100. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NSM9VYtekkTV1h9dK4WxM4
This was referenced Nov 14, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Moves every OpenTelemetry module to 1.47.0 (otelslog bridge to v0.21.0) and reads the global logger provider from
go.opentelemetry.io/otel.Why
#99 and #100 fail lint. In 1.47.0 the Logs API is stable and
go.opentelemetry.io/otel/log/globalis deprecated, so staticcheck (SA1019) rejectslogglobal.GetLoggerProvider()inpkg/logging/otel.go. Those two PRs also leave the OTLP exporters at 1.45.0 next to a 1.47.0 SDK.Behaviour
None changes. The deprecated package's functions forward to
otel.GetLoggerProvider/otel.SetLoggerProvider, so there is one global provider under both names. A binary that still callslog/global.SetLoggerProviderkeeps exporting throughNewOTelHandler.Changes
pkg/logging/otel.go:otel.GetLoggerProvider(); comments nameotel.SetLoggerProvider.docs/api.md: the same name.go.mod,go.sum: allgo.opentelemetry.io/otel*at 1.47.0, the exporters included.hack/rlgov-measure/go.mod,go.sum: follow, because that module builds against this tree.Checked locally
go build ./...,go vetand the tests ofpkg/loggingandpkg/telemetrypass.Supersedes #99 and #100.
🤖 Generated with Claude Code
https://claude.ai/code/session_01NSM9VYtekkTV1h9dK4WxM4