Skip to content

Update the OpenTelemetry SDK version to 1.60.0#16407

Merged
laurit merged 15 commits intomainfrom
otelbot/update-opentelemetry-sdk-to-1.60.0
Mar 9, 2026
Merged

Update the OpenTelemetry SDK version to 1.60.0#16407
laurit merged 15 commits intomainfrom
otelbot/update-opentelemetry-sdk-to-1.60.0

Conversation

@otelbot
Copy link
Copy Markdown
Contributor

@otelbot otelbot Bot commented Mar 6, 2026

Update the OpenTelemetry SDK version to 1.60.0.

@otelbot otelbot Bot requested a review from a team as a code owner March 6, 2026 21:55
@github-actions github-actions Bot added the test native This label can be applied to PRs to trigger them to run native tests label Mar 6, 2026
@trask trask marked this pull request as draft March 6, 2026 22:24
trask added 11 commits March 6, 2026 14:39
…g defaults

The SDK 1.60.0 added a new default method isTraceIdRandom() to the TraceFlags
interface. BridgedTraceFlags implements both the application and agent versions
of TraceFlags, which causes a compilation error due to conflicting unrelated
default methods. Adding an explicit override that delegates to the application's
TraceFlags resolves the ambiguity.
…RecordBuilder150Incubator

Add 'deprecation' to @SuppressWarnings on convertExtendedAttributes method to
handle OtelDeprecatedApiUsage errors for deprecated ExtendedAttributes,
ExtendedAttributesBuilder, and ExtendedAttributeKey usage. This is needed to
support applications still using the EXTENDED_ATTRIBUTES feature.
SDK 1.60.0 sets the isTraceIdRandom bit in trace flags for randomly generated
trace IDs, changing the value from 0x01 to 0x03. Update MDC tests to use
span.getSpanContext().getTraceFlags().asHex() for expected values.
…new API method

Compute the random trace ID flag from the byte value directly instead
of delegating to the application's TraceFlags.isTraceIdRandom() which
does not exist in API versions < 1.60. The previous implementation
created a bytecode reference that muzzle detected as missing, causing
all opentelemetry-api bridge instrumentation modules to be disabled.
…tomizer interface change

DeclarativeConfigurationCustomizer is no longer a functional interface
in SDK 1.60.0 (it now has addSpanExporterCustomizer, addMetricExporterCustomizer,
and addLogRecordExporterCustomizer in addition to addModelCustomizer).
Replace the lambda with an anonymous class implementation.
…terface change

DeclarativeConfigurationCustomizer is no longer a functional interface
in SDK 1.60.0. Replace lambdas with anonymous class implementations in
SpanLoggingCustomizerProviderTest and ResourceCustomizerProviderTest.
Filter out otel.sdk.* metrics in metric assertions to avoid coupling
tests to SDK internal self-diagnostics metrics which changed in 1.60.0.
The otel.experimental.config.file property is deprecated in SDK 1.60.0
and will be removed after 1.62.0. Rename all usages to otel.config.file.
Also add the SDK deprecation warning to IGNORED_WARNINGS in the Spring
smoke tests since the SDK may still emit it during initialization.
SDK 1.60.0 emits self-diagnostics metrics, so the exported metrics list
contains more than just the test metric. Use anySatisfy instead of
checking exact size to avoid coupling to SDK internal metrics.
@trask trask force-pushed the otelbot/update-opentelemetry-sdk-to-1.60.0 branch from 36d48ff to 079f481 Compare March 7, 2026 03:45
trask added 3 commits March 6, 2026 19:52
SDK 1.60.0 has a bug in maybeConfigureFromFile() where the condition
is inverted, causing it to warn about otel.experimental.config.file
being deprecated even when the property is not set.
@trask trask marked this pull request as ready for review March 7, 2026 18:37
@laurit laurit merged commit 8e18185 into main Mar 9, 2026
96 checks passed
@laurit laurit deleted the otelbot/update-opentelemetry-sdk-to-1.60.0 branch March 9, 2026 07:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

test native This label can be applied to PRs to trigger them to run native tests

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants