Bump go.opentelemetry.io/otel from 1.37.0 to 1.41.0

[dependabot]

Bumps go.opentelemetry.io/otel from 1.37.0 to 1.41.0.

Changelog

Sourced from go.opentelemetry.io/otel's changelog.

[1.41.0/0.63.0/0.17.0/0.0.15] 2026-03-02

This release is the last to support [Go 1.24]. The next release will require at least [Go 1.25].

Added

• Support testing of [Go 1.26]. (#7902)

Fixed

• Update Baggage in go.opentelemetry.io/otel/propagation and Parse and New in go.opentelemetry.io/otel/baggage to comply with W3C Baggage specification limits. New and Parse now return partial baggage along with an error when limits are exceeded. Errors from baggage extraction are reported to the global error handler. (#7880)
• Return an error when the endpoint is configured as insecure and with TLS configuration in go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploghttp. (#7914)
• Return an error when the endpoint is configured as insecure and with TLS configuration in go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetrichttp. (#7914)
• Return an error when the endpoint is configured as insecure and with TLS configuration in go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp. (#7914)

[1.40.0/0.62.0/0.16.0] 2026-02-02

Added

• Add AlwaysRecord sampler in go.opentelemetry.io/otel/sdk/trace. (#7724)
• Add Enabled method to all synchronous instrument interfaces (Float64Counter, Float64UpDownCounter, Float64Histogram, Float64Gauge, Int64Counter, Int64UpDownCounter, Int64Histogram, Int64Gauge,) in go.opentelemetry.io/otel/metric. This stabilizes the synchronous instrument enabled feature, allowing users to check if an instrument will process measurements before performing computationally expensive operations. (#7763)
• Add go.opentelemetry.io/otel/semconv/v1.39.0 package. The package contains semantic conventions from the v1.39.0 version of the OpenTelemetry Semantic Conventions. See the migration documentation for information on how to upgrade from go.opentelemetry.io/otel/semconv/v1.38.0. (#7783, #7789)

Changed

• Improve the concurrent performance of HistogramReservoir in go.opentelemetry.io/otel/sdk/metric/exemplar by 4x. (#7443)
• Improve the concurrent performance of FixedSizeReservoir in go.opentelemetry.io/otel/sdk/metric/exemplar. (#7447)
• Improve performance of concurrent histogram measurements in go.opentelemetry.io/otel/sdk/metric. (#7474)
• Improve performance of concurrent synchronous gauge measurements in go.opentelemetry.io/otel/sdk/metric. (#7478)
• Add experimental observability metrics in go.opentelemetry.io/otel/exporters/stdout/stdoutmetric. (#7492)
• Exporter in go.opentelemetry.io/otel/exporters/prometheus ignores metrics with the scope go.opentelemetry.io/contrib/bridges/prometheus. This prevents scrape failures when the Prometheus exporter is misconfigured to get data from the Prometheus bridge. (#7688)
• Improve performance of concurrent exponential histogram measurements in go.opentelemetry.io/otel/sdk/metric. (#7702)
• The rpc.grpc.status_code attribute in the experimental metrics emitted from go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc is replaced with the rpc.response.status_code attribute to align with the semantic conventions. (#7854)
• The rpc.grpc.status_code attribute in the experimental metrics emitted from go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploggrpc is replaced with the rpc.response.status_code attribute to align with the semantic conventions. (#7854)

Fixed

• Fix bad log message when key-value pairs are dropped because of key duplication in go.opentelemetry.io/otel/sdk/log. (#7662)
• Fix DroppedAttributes on Record in go.opentelemetry.io/otel/sdk/log to not count the non-attribute key-value pairs dropped because of key duplication. (#7662)
• Fix SetAttributes on Record in go.opentelemetry.io/otel/sdk/log to not log that attributes are dropped when they are actually not dropped. (#7662)
• Fix missing request.GetBody in go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp to correctly handle HTTP/2 GOAWAY frame. (#7794)
• WithHostID detector in go.opentelemetry.io/otel/sdk/resource to use full path for ioreg command on Darwin (macOS). (#7818)

... (truncated)

Commits

• 4575a97 Release 1.41.0/0.63.0/0.17.0/0.0.15 (#7977)
• 66fc10d fix: add error handling for insecure HTTP endpoints with TLS client configura...
• 76e6eec chore(deps): update github/codeql-action action to v4.32.5 (#7980)
• 0d50f90 Revert "Generate semconv/v1.40.0" (#7978)
• c38a4a5 Generate semconv/v1.40.0 (#7929)
• 0f1a224 chore(deps): update module github.com/securego/gosec/v2 to v2.23.0 (#7899)
• c79ebf4 chore(deps): update module github.com/daixiang0/gci to v0.14.0 (#7973)
• f758157 chore(deps): update module github.com/sonatard/noctx to v0.5.0 (#7968)
• 92a1164 fix(deps): update github.com/opentracing-contrib/go-grpc/test digest to d566b...
• 3cd7c27 chore(deps): update module github.com/protonmail/go-crypto to v1.4.0 (#7969)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[greptile-apps]

Greptile Summary

This dependabot PR bumps go.opentelemetry.io/otel, otel/metric, and otel/trace from v1.37.0 to v1.41.0, and also upgrades go.opentelemetry.io/auto/sdk (v1.1.0 → v1.2.1), github.com/stretchr/testify (v1.10.0 → v1.11.1), and github.com/rogpeppe/go-internal (v1.13.1 → v1.14.1) — none of the latter three are mentioned in the PR title.

• The otel SDK packages (otel/sdk v1.36.0, otel/sdk/metric v1.36.0) were not bumped alongside the API packages, creating a 5-minor-version skew. v1.40.0 stabilised Enabled() on all synchronous instrument interfaces; an SDK at v1.36.0 may not implement those updated interfaces, risking compilation failure or silent no-op behaviour.

Confidence Score: 3/5

Not safe to merge until the otel SDK/SDK-metric versions are aligned with the updated API packages.

A P1 version-skew issue exists between the otel API (v1.41.0) and SDK (v1.36.0); the Enabled() interface change in v1.40.0 means the unupdated SDK may not satisfy the new API contracts, potentially breaking builds or producing silent no-ops.

go.mod — specifically the otel/sdk and otel/sdk/metric indirect dependency lines that were not bumped as part of this update.

Important Files Changed

Filename	Overview
go.mod	Bumps otel core (v1.37.0 → v1.41.0), otel/auto/sdk (v1.1.0 → v1.2.1), testify (v1.10.0 → v1.11.1), and rogpeppe/go-internal (v1.13.1 → v1.14.1); otel/sdk and otel/sdk/metric remain at v1.36.0, creating a 5-minor-version API/SDK skew.
go.sum	Checksum entries updated to match the new versions in go.mod; no issues found.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Application Code] --> B[otel API\nv1.41.0]
    A --> C[otel/metric API\nv1.41.0]
    A --> D[otel/trace API\nv1.41.0]
    B --> E[otel/sdk\nv1.36.0 ⚠️]
    C --> F[otel/sdk/metric\nv1.36.0 ⚠️]
    E --> G[Exporters\notlptrace v1.29.0\notlptracehttp v1.27.0\nstdoutmetric v1.36.0]
    F --> G
    style E fill:#ff9999,stroke:#cc0000
    style F fill:#ff9999,stroke:#cc0000

Loading

Prompt To Fix All With AI

This is a comment left during a code review.
Path: go.mod
Line: 75-76

Comment:
**OTel SDK/API version skew**

`otel`, `otel/metric`, and `otel/trace` are bumped to v1.41.0, but `otel/sdk` and `otel/sdk/metric` remain at v1.36.0. In the opentelemetry-go release model, all modules are cut together and the SDK is expected to implement the current API contracts. v1.40.0 added `Enabled()` to all synchronous instrument interfaces (`Float64Counter`, `Int64Counter`, etc.) as a stable API. With `otel/sdk/metric` pinned at v1.36.0, those instrument types may not satisfy the updated interfaces, risking compile failures or silent no-op behaviour if the new `Enabled()` path is exercised by any instrumentation library pulling otel v1.41.0. Consider also bumping `otel/sdk` and `otel/sdk/metric` to v1.41.0 to keep the whole stack in sync.

How can I resolve this? If you propose a fix, please make it concise.

_{Reviews (1): Last reviewed commit: "Bump go.opentelemetry.io/otel from 1.37...." | Re-trigger Greptile}

[greptile-apps]

OTel SDK/API version skew

otel, otel/metric, and otel/trace are bumped to v1.41.0, but otel/sdk and otel/sdk/metric remain at v1.36.0. In the opentelemetry-go release model, all modules are cut together and the SDK is expected to implement the current API contracts. v1.40.0 added Enabled() to all synchronous instrument interfaces (Float64Counter, Int64Counter, etc.) as a stable API. With otel/sdk/metric pinned at v1.36.0, those instrument types may not satisfy the updated interfaces, risking compile failures or silent no-op behaviour if the new Enabled() path is exercised by any instrumentation library pulling otel v1.41.0. Consider also bumping otel/sdk and otel/sdk/metric to v1.41.0 to keep the whole stack in sync.

Prompt To Fix With AI

This is a comment left during a code review.
Path: go.mod
Line: 75-76

Comment:
**OTel SDK/API version skew**

`otel`, `otel/metric`, and `otel/trace` are bumped to v1.41.0, but `otel/sdk` and `otel/sdk/metric` remain at v1.36.0. In the opentelemetry-go release model, all modules are cut together and the SDK is expected to implement the current API contracts. v1.40.0 added `Enabled()` to all synchronous instrument interfaces (`Float64Counter`, `Int64Counter`, etc.) as a stable API. With `otel/sdk/metric` pinned at v1.36.0, those instrument types may not satisfy the updated interfaces, risking compile failures or silent no-op behaviour if the new `Enabled()` path is exercised by any instrumentation library pulling otel v1.41.0. Consider also bumping `otel/sdk` and `otel/sdk/metric` to v1.41.0 to keep the whole stack in sync.

How can I resolve this? If you propose a fix, please make it concise.