dependabot[bot] opened a new pull request, #4910:
URL: https://github.com/apache/arrow-adbc/pull/4910

   Bumps 
[go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc](https://github.com/open-telemetry/opentelemetry-go-contrib)
 from 0.71.0 to 0.72.0.
   <details>
   <summary>Changelog</summary>
   <p><em>Sourced from <a 
href="https://github.com/open-telemetry/opentelemetry-go-contrib/blob/main/CHANGELOG.md";>go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc's
 changelog</a>.</em></p>
   <blockquote>
   <h2>[1.47.0/2.6.0/0.72.0/0.38.0/0.27.0/0.21.0/0.17.0/0.19.0] - 
2026-10-03</h2>
   <h3>Added</h3>
   <ul>
   <li>Add <code>NewResourceDetectorWithOptions</code> and the 
<code>WithAWSLogger</code> option to 
<code>go.opentelemetry.io/contrib/detectors/aws/ec2/v2</code>, allowing a 
custom AWS SDK <code>logging.Logger</code> to be supplied to the EC2 resource 
detector. (<a 
href="https://redirect.github.com/open-telemetry/opentelemetry-go-contrib/issues/9132";>#9132</a>)</li>
   <li>Add <code>go.opentelemetry.io/contrib/detectors/openshift</code>, a new 
resource detector for OpenShift 4 clusters, ported from 
<code>processor/resourcedetectionprocessor/internal/openshift</code> in 
<code>opentelemetry-collector-contrib</code>. Detects 
<code>k8s.cluster.name</code>, and <code>cloud.provider</code>, 
<code>cloud.platform</code> and <code>cloud.region</code> for clusters running 
on AWS, Google Cloud and IBM Cloud; Azure clusters report 
<code>cloud.provider</code> and <code>cloud.platform</code> only. (<a 
href="https://redirect.github.com/open-telemetry/opentelemetry-go-contrib/issues/9499";>#9499</a>)</li>
   <li>Add <code>go.opentelemetry.io/contrib/detectors/kubeadm</code>, a new 
resource detector for kubeadm-provisioned Kubernetes clusters, ported from 
<code>processor/resourcedetectionprocessor/internal/kubeadm</code> in 
<code>opentelemetry-collector-contrib</code>. Detects 
<code>k8s.cluster.name</code> from the <code>ClusterConfiguration</code> 
document in the <code>kube-system/kubeadm-config</code> ConfigMap and 
<code>k8s.cluster.uid</code> from the <code>kube-system</code> namespace UID. 
(<a 
href="https://redirect.github.com/open-telemetry/opentelemetry-go-contrib/issues/9500";>#9500</a>)</li>
   </ul>
   <h3>Changed</h3>
   <ul>
   <li>Client metrics in 
<code>go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp</code> no 
longer include attributes from the server-side <code>Labeler</code>, preventing 
attributes such as <code>http.route</code> from leaking into outbound requests.
   This is a breaking change for applications that use 
<code>ContextWithLabeler</code> to add custom client metric attributes: use 
<code>ContextWithClientLabeler</code> / <code>ClientLabelerFromContext</code> 
or the <code>WithMetricAttributesFn</code> option instead.
   Server-side use of <code>ContextWithLabeler</code> / 
<code>LabelerFromContext</code> is unchanged. (<a 
href="https://redirect.github.com/open-telemetry/opentelemetry-go-contrib/issues/8924";>#8924</a>)</li>
   <li>Stop emitting the legacy <code>http.read_bytes</code> and 
<code>http.wrote_bytes</code> attributes on the per-operation span events 
enabled by <code>WithMessageEvents</code> in 
<code>go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp</code>.
   The <code>read</code> and <code>write</code> events remain, while total body 
sizes continue to be recorded on the server span as 
<code>http.request.body.size</code> and <code>http.response.body.size</code> 
according to HTTP semantic conventions. (<a 
href="https://redirect.github.com/open-telemetry/opentelemetry-go-contrib/issues/9624";>#9624</a>)</li>
   </ul>
   <h3>Deprecated</h3>
   <ul>
   <li>Deprecate 
<code>go.opentelemetry.io/contrib/instrumentation/github.com/aws/aws-sdk-go-v2/otelaws</code>.
 (<a 
href="https://redirect.github.com/open-telemetry/opentelemetry-go-contrib/issues/9707";>#9707</a>)</li>
   <li>Deprecate <code>go.opentelemetry.io/contrib/propagators/aws</code>. (<a 
href="https://redirect.github.com/open-telemetry/opentelemetry-go-contrib/issues/9706";>#9706</a>)</li>
   <li>Deprecate 
<code>go.opentelemetry.io/contrib/samplers/probability/consistent</code>. (<a 
href="https://redirect.github.com/open-telemetry/opentelemetry-go-contrib/issues/9633";>#9633</a>)</li>
   <li>Deprecate <code>ReadBytesKey</code>, <code>ReadErrorKey</code>, 
<code>WroteBytesKey</code>, and <code>WriteErrorKey</code> in 
<code>go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp</code>.
   The identifiers remain available and their values are unchanged, but 
<code>WithMessageEvents</code> no longer emits <code>http.read_bytes</code> or 
<code>http.wrote_bytes</code>.
   There is no semantic-convention replacement for per-read or per-write byte 
counts or the human-readable error fields.
   Use <code>HTTPRequestBodySizeKey</code> and 
<code>HTTPResponseBodySizeKey</code> from 
<code>go.opentelemetry.io/otel/semconv/v1.43.0</code> to record total body 
sizes on the span.
   If an error causes the HTTP request to fail, set the span status to Error 
and record <code>ErrorType(err)</code> from 
<code>go.opentelemetry.io/otel/semconv/v1.43.0</code> on the span. (<a 
href="https://redirect.github.com/open-telemetry/opentelemetry-go-contrib/issues/9624";>#9624</a>)</li>
   </ul>
   <h3>Fixed</h3>
   <ul>
   <li>Treat empty Prometheus exporter environment variable values as unset in 
<code>go.opentelemetry.io/contrib/exporters/autoexport</code>, restoring the 
documented defaults. (<a 
href="https://redirect.github.com/open-telemetry/opentelemetry-go-contrib/issues/9636";>#9636</a>)</li>
   <li>Bound converter-owned recursive map, slice, array, and pointer traversal 
in <code>go.opentelemetry.io/contrib/bridges/otellogr</code>, 
<code>go.opentelemetry.io/contrib/bridges/otellogrus</code>, 
<code>go.opentelemetry.io/contrib/bridges/otelslog</code>, and 
<code>go.opentelemetry.io/contrib/bridges/otelzap</code>.
   A field requiring more than 100 such levels is replaced with 
<code>&lt;max-depth-exceeded&gt;</code> and the record continues to be emitted. 
Existing <code>fmt</code> and user-method behavior remains unchanged. (<a 
href="https://redirect.github.com/open-telemetry/opentelemetry-go-contrib/issues/9691";>#9691</a>)</li>
   <li>Format span attributes in 
<code>go.opentelemetry.io/contrib/zpages</code> using 
<code>attribute.Value.String</code> instead of the deprecated 
<code>attribute.Value.Emit</code>, following the OpenTelemetry AnyValue 
representation for non-OTLP protocols. (<a 
href="https://redirect.github.com/open-telemetry/opentelemetry-go-contrib/issues/9453";>#9453</a>)</li>
   <li>Set <code>error.type</code> on the span and on the request-duration, 
request-body-size, and response-body-size metrics when a client disconnects 
mid-request in 
<code>go.opentelemetry.io/contrib/instrumentation/github.com/gin-gonic/gin/otelgin</code>,
 using the request context's cancellation error as the classification source 
when the handler has not already recorded an error via <code>c.Error</code>. 
Previously a disconnect was recorded with span status <code>Error</code> and no 
<code>error.type</code>, indistinguishable from a genuine server fault. (<a 
href="https://redirect.github.com/open-telemetry/opentelemetry-go-contrib/issues/9394";>#9394</a>)</li>
   <li>Report Prometheus metrics HTTP server errors in 
<code>go.opentelemetry.io/contrib/otelconf</code> when using the 
<code>v0.2.0</code> configuration schema.
   The error check was inverted, so a clean shutdown 
(<code>http.ErrServerClosed</code>) was reported as unexpected while real 
<code>Serve</code> errors were ignored. (<a 
href="https://redirect.github.com/open-telemetry/opentelemetry-go-contrib/issues/9653";>#9653</a>)</li>
   <li>Fix temporary file cleanup for multipart requests in 
<code>go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp</code> by 
copying the parsed multipart form back to the original request during deferred 
cleanup, preserving <code>net/http</code> cleanup during panic unwinding for 
HTTP/2 panic handling and outer recovery middleware paths. Unrecovered HTTP/1 
handler panics remain uncleaned because <code>net/http</code> skips 
<code>finishRequest</code> in that path. (<a 
href="https://redirect.github.com/open-telemetry/opentelemetry-go-contrib/issues/9685";>#9685</a>)</li>
   <li>Fix <code>http.client.request.body.size</code> recording for streaming 
request bodies in 
<code>go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp</code>. (<a 
href="https://redirect.github.com/open-telemetry/opentelemetry-go-contrib/issues/8684";>#8684</a>)</li>
   <li>Bound Kubernetes ConfigMap requests in 
<code>go.opentelemetry.io/contrib/detectors/aws/eks</code> with a 10-second 
timeout so <code>Detect</code> cannot hang indefinitely when the 
caller-provided context has no deadline. (<a 
href="https://redirect.github.com/open-telemetry/opentelemetry-go-contrib/issues/9419";>#9419</a>)</li>
   </ul>
   <h3>Removed</h3>
   <ul>
   <li>Drop support for [Go 1.25]. (<a 
href="https://redirect.github.com/open-telemetry/opentelemetry-go-contrib/issues/9584";>#9584</a>)</li>
   <li>Remove 
<code>go.opentelemetry.io/contrib/instrumentation/github.com/labstack/echo/otelecho</code>.
 Use <code>github.com/labstack/echo-opentelemetry</code> instead. (<a 
href="https://redirect.github.com/open-telemetry/opentelemetry-go-contrib/issues/9613";>#9613</a>)</li>
   </ul>
   </blockquote>
   </details>
   <details>
   <summary>Commits</summary>
   <ul>
   <li><a 
href="https://github.com/open-telemetry/opentelemetry-go-contrib/commit/0c76f6137a2ceea80984d55e3de165924d823f71";><code>0c76f61</code></a>
 Release v1.47.0/v2.6.0/v0.72.0/v0.38.0/v0.27.0/v0.21.0/v0.17.0/v0.19.0 (<a 
href="https://redirect.github.com/open-telemetry/opentelemetry-go-contrib/issues/9802";>#9802</a>)</li>
   <li><a 
href="https://github.com/open-telemetry/opentelemetry-go-contrib/commit/318f5f91d789469a87f062b28e41c6ebbdffb220";><code>318f5f9</code></a>
 Add timeout on Kubernetes API calls for EKS detector (<a 
href="https://redirect.github.com/open-telemetry/opentelemetry-go-contrib/issues/9419";>#9419</a>)</li>
   <li><a 
href="https://github.com/open-telemetry/opentelemetry-go-contrib/commit/f848a156d803093fa063b014281d6358618268eb";><code>f848a15</code></a>
 test(detector/ecs): increase unit test coverage (<a 
href="https://redirect.github.com/open-telemetry/opentelemetry-go-contrib/issues/9774";>#9774</a>)</li>
   <li><a 
href="https://github.com/open-telemetry/opentelemetry-go-contrib/commit/c0d84debea84819d97ccf3eecad081211da5ad62";><code>c0d84de</code></a>
 Restore gofumpt clothe-returns and balance-calls (<a 
href="https://redirect.github.com/open-telemetry/opentelemetry-go-contrib/issues/9793";>#9793</a>)</li>
   <li><a 
href="https://github.com/open-telemetry/opentelemetry-go-contrib/commit/6215054285946acefefe815587f9edfa490ebf43";><code>6215054</code></a>
 fix(deps): update aws-sdk-go-v2 monorepo (<a 
href="https://redirect.github.com/open-telemetry/opentelemetry-go-contrib/issues/9785";>#9785</a>)</li>
   <li><a 
href="https://github.com/open-telemetry/opentelemetry-go-contrib/commit/9a2e8ea28ea8034baa11dec82d7b32ac70133845";><code>9a2e8ea</code></a>
 fix(deps): update kubernetes monorepo to v0.37.1</li>
   <li><a 
href="https://github.com/open-telemetry/opentelemetry-go-contrib/commit/3d8e3382db254dc604659d3d6716b62da0b2f420";><code>3d8e338</code></a>
 chore(deps): update sigs.k8s.io/json digest to 11ed52e</li>
   <li><a 
href="https://github.com/open-telemetry/opentelemetry-go-contrib/commit/be5b68808a1a120b6a2960ede4f89d113798476d";><code>be5b688</code></a>
 chore(deps): update go-openapi packages</li>
   <li><a 
href="https://github.com/open-telemetry/opentelemetry-go-contrib/commit/e382b4d621b97497e615ff5440e2400877f1f748";><code>e382b4d</code></a>
 chore(deps): update module github.com/fxamacker/cbor/v2 to v2.9.4</li>
   <li><a 
href="https://github.com/open-telemetry/opentelemetry-go-contrib/commit/97f9e880dd52afe9fcab08036936bf3233590a83";><code>97f9e88</code></a>
 fix(deps): update module github.com/moby/moby/client to v0.6.1</li>
   <li>Additional commits viewable in <a 
href="https://github.com/open-telemetry/opentelemetry-go-contrib/compare/zpages/v0.71.0...zpages/v0.72.0";>compare
 view</a></li>
   </ul>
   </details>
   <br />
   
   
   [![Dependabot compatibility 
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc&package-manager=go_modules&previous-version=0.71.0&new-version=0.72.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
   
   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-automerge-start)
   [//]: # (dependabot-automerge-end)
   
   ---
   
   <details>
   <summary>Dependabot commands and options</summary>
   <br />
   
   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)
   
   
   </details>


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to