Repository navigation
Conversation
## Why `go.opentelemetry.io/otel/log` v0.21.0 removed `log.KeyValue`, `log.Value` and their constructors (`log.String`, `log.StringValue`, …) in favour of `attribute.KeyValue` / `attribute.Value`. Every release up to v3.0.0 uses the old API, so a consumer that raises `otel/sdk/log` to v0.21.0 — the release fixing GO-2026-6615 (BatchProcessor busy-spin when the export buffer is full) — can no longer compile `otel`, `grpc` or `rest`. ## What - Raise `otel`, `otel/sdk`, `otel/metric`, `otel/trace`, `otel/sdk/metric` to v1.45.0 and `otel/log`, `otel/sdk/log`, `otlploghttp` to v0.21.0. This also clears GO-2026-6505 (`otel/sdk`). - Port log record attributes and bodies in `otel`, `grpc` and `rest` to the `attribute` package. No exported signature changes. - The console exporter now renders slice and map attributes through `attribute.Value.AsInterface()` (plain Go values) instead of the old `log.Value` structs. - The bump raises `golang.org/x/net` to v0.57.0, which deprecates `http2/h2c`. `grpc/server.go` keeps it under `//nolint:staticcheck`: `http.Server.Protocols` drops the HTTP/1.1 `Upgrade: h2c` path, so replacing it is a behaviour change for its own PR. ## Not in this PR `govulncheck` still reports advisories unrelated to OpenTelemetry (grpc v1.83.0, x/crypto v0.54.0, moby/go-archive, argo-workflows, Go stdlib 1.26.1). ## Verification `task ci:check`, `go vet -tags='example integration argo' ./...` and `task test:integration` all pass locally.
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.
Promotes the one fix on
nextsince v3.0.0:Merge with a merge commit, never squash. A local simulation of this merge plus
semantic-release --dry-runcomputes 3.0.1.No breaking changes on the line, so
MIGRATION.mdis unchanged.task ci:check, taggedgo vetandtask test:integrationpassed on the fix before it merged intonext.