Records/golang/go.opentelemetry.io/otel/trace/v1.35.0/go.opentelemetry.io/otel/baggage.NewMember

shared with 2 packages — this evidence cannot say whose API it is

Published samples

• go.opentelemetry.io/otel v1.35.0: Baggage validates RFC 7230 token keys and delimiter-free values while resolving duplicate keys with last-value-wins semantics, and CompositeTextMapPropagator coordinates W3C TraceContext and Baggage header extraction and injection Built ? This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWgo.opentelemetry.io/otel/baggage.Newgo.opentelemetry.io/otel/baggage.NewMembergo.opentelemetry.io/otel/baggage.FromContextgo.opentelemetry.io/otel/baggage.Baggage.DeleteMembergo.opentelemetry.io/otel/baggage.Baggage.Membergo.opentelemetry.io/otel/baggage.Baggage.Lengo.opentelemetry.io/otel/propagation.NewCompositeTextMapPropagatorgo.opentelemetry.io/otel/propagation.TraceContextgo.opentelemetry.io/otel/propagation.Baggagego.opentelemetry.io/otel/propagation.HeaderCarriergo MIT-0 · 2026-08-17

Compatibility matrix

Project-level observations and symbol/contract verifications are counted separately and never combined.

These counts do not distinguish how the symbol was called: overloads, argument shapes and options are pooled together. What a particular call shape does is proven by a sample's contract, not by these numbers.

snapshot · 2026-08-30

Failure clusters

• observed PROJECT_TEST Evidence gap ×2 v1.35.0 → v1.45.0 os=linux · runtime=go@1.26
  Evidence quality: legacy-evidence-incomplete · Environment variants: 2 · First recorded: 2026-08-20 · Last seen: 2026-08-30
  Diagnostic re-verification candidate