dependabot[bot] opened a new pull request, #3864: URL: https://github.com/apache/causeway/pull/3864
Bumps [io.opentelemetry.javaagent:opentelemetry-javaagent](https://github.com/open-telemetry/opentelemetry-java-instrumentation) from 2.31.1 to 2.32.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/open-telemetry/opentelemetry-java-instrumentation/releases";>io.opentelemetry.javaagent:opentelemetry-javaagent's releases</a>.</em></p> <blockquote> <h2>Version 2.32.0</h2> <p>This release targets the OpenTelemetry SDK 1.66.0.</p> <p>Note that many artifacts have the <code>-alpha</code> suffix attached to their version number, reflecting that they will continue to have breaking changes. Please see <a href="https://github.com/open-telemetry/opentelemetry-java-instrumentation/blob/main/VERSIONING.md#opentelemetry-java-instrumentation-versioning";>VERSIONING.md</a> for more details.</p> <h3>⚠️ Breaking changes to non-stable APIs</h3> <ul> <li>Remove the deprecated <code>HostIdResource.REGISTRY_QUERY</code> constant. (<a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/19778";>#19778</a>)</li> <li>The <code>ExperimentalJmxMetricHandler</code> SPI now requires implementations to provide <code>getMetricNames()</code>. (<a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/19781";>#19781</a>)</li> <li>Add the required <code>isRequestStreaming(REQUEST)</code> method to <code>GenAiAttributesGetter</code>. (<a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/19879";>#19879</a>)</li> <li>The experimental <code>java.common.messaging.headers/development</code> YAML selector no longer configures header capture. Use <code>java.common.messaging.headers</code> instead. (<a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/20260";>#20260</a>)</li> </ul> <h3>🚫 Deprecations</h3> <ul> <li>Deprecate <code>otel.jmx.target.system</code> in favor of <code>otel.jmx.metrics.experimental.included</code>. (<a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/19783";>#19783</a>)</li> <li>Deprecate <code>otel.instrumentation.elasticsearch.capture-search-query</code>. It will be removed in 3.0, when search query bodies are always captured. There is no replacement. (<a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/19675";>#19675</a>)</li> <li>Deprecate <code>otel.instrumentation.opensearch.capture-search-query</code>. It will be removed in 3.0, when search query bodies are always captured. There is no replacement. Sanitization remains enabled by default and configurable with <code>otel.instrumentation.opensearch.query-sanitization.enabled</code>. (<a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/19837";>#19837</a>)</li> <li>Deprecate <code>otel.jmx.enabled</code> in favor of <code>otel.instrumentation.jmx.enabled</code> to align with other instrumentation enablement properties. (<a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/19945";>#19945</a>)</li> <li>Deprecate automatic rewriting of <code>VirtualField.find(Class, Class)</code> calls in inlined javaagent advice. Instead, look up the <code>VirtualField</code> once and store it in a helper class's <code>static final</code> field. The <code>find</code> method itself remains supported. (<a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/19980";>#19980</a>)</li> <li>Deprecate the Elasticsearch REST library instrumentation. Use the Elasticsearch Java API Client's native OpenTelemetry support, or the Java agent for direct <code>RestClient</code> usage. Java agent instrumentation is unaffected. (<a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/19995";>#19995</a>)</li> <li>Deprecate <code>otel.instrumentation.messaging.experimental.receive-telemetry.enabled</code> in favor of <code>otel.instrumentation.common.messaging.experimental.receive-telemetry.enabled</code>. For headers, replace <code>otel.instrumentation.messaging.experimental.headers.included</code> and <code>.excluded</code> with <code>otel.instrumentation.common.messaging.headers.included</code> and <code>.excluded</code>. Also deprecate <code>otel.instrumentation.messaging.experimental.capture-headers</code> in favor of <code>otel.instrumentation.common.messaging.headers.included</code>. Stable selectors take precedence per leaf. (<a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/20060";>#20060</a>, <a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/20260";>#20260</a>)</li> <li>Deprecate the <code>.included</code> / <code>.excluded</code> properties under <code>otel.instrumentation.log4j-appender.experimental.map-message-attributes</code>, <code>otel.instrumentation.logback-appender.experimental.key-value-pair-attributes</code>, <code>otel.instrumentation.logback-appender.experimental.logstash-marker-attributes</code>, and <code>otel.instrumentation.logback-appender.experimental.logstash-structured-argument-attributes</code> in favor of the stable and unified <code>otel.instrumentation.common.logging.structured-attributes.included</code> / <code>.excluded</code>. (<a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/20066";>#20066</a>)</li> <li>Deprecate <code>otel.instrumentation.couchbase.experimental-span-attributes</code> in favor of <code>otel.instrumentation.couchbase.emit-experimental-telemetry</code>, a broader name for experimental attributes and internal spans from the underlying Couchbase client. (<a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/20117";>#20117</a>)</li> <li>Deprecate <code>otel.traces.sampler=linksbased_parentbased_always_on</code> with no replacement and declarative <code>rule_based_routing</code> in favor of the SDK incubator composite/development <code>rule_based</code> sampler, whose configuration and matching behavior differ. (<a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/20249";>#20249</a>)</li> <li>Promote controller and view telemetry configuration to the stable properties <code>otel.instrumentation.common.controller-telemetry.enabled</code> and <code>otel.instrumentation.common.view-telemetry.enabled</code>, deprecating <code>otel.instrumentation.common.experimental.controller-telemetry.enabled</code> and <code>otel.instrumentation.common.experimental.view-telemetry.enabled</code>. (<a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/20258";>#20258</a>)</li> <li>Promote Java agent span suppression configuration to the stable property <code>otel.instrumentation.common.span-suppression-strategy</code>, deprecating <code>otel.instrumentation.experimental.span-suppression-strategy</code>. (<a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/20259";>#20259</a>)</li> <li>Deprecate <code>otel.instrumentation.oshi.experimental-metrics.enabled</code>, <code>ProcessMetrics</code>, and its <code>registerObservers(...)</code> methods in favor of <code>jvm.memory.used</code> and <code>jvm.cpu.time</code>. (<a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/20323";>#20323</a>)</li> <li>Deprecate <code>SystemMetrics.registerObservers(Meter)</code> in the OSHI library instrumentation in favor of <code>SystemMetrics.registerObservers(OpenTelemetry)</code>. (<a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/20263";>#20263</a>)</li> <li>In declarative configuration YAML, deprecate dotted selectors in the <code>distribution.javaagent.instrumentation.enabled</code> and <code>.disabled</code> lists. Use <code>reactor_3_1</code> instead of <code>reactor_3.1</code>. Flat-property names such as <code>otel.instrumentation.reactor-3.1.enabled</code> are unchanged. (<a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/20326";>#20326</a>)</li> </ul> <h3>🌟 New javaagent instrumentation</h3> <ul> <li>Add Redisson database connection pool metrics for versions 2.3.0 through 3.25. (<a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/19152";>#19152</a>, <a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/19634";>#19634</a>)</li> <li>Add Java agent instrumentation for Pekko remoting so trace context propagates across remote calls. (<a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/19823";>#19823</a>)</li> </ul> <h3>📈 Enhancements</h3> <ul> <li>Expand the upcoming 3.0 database semantic conventions behind <code>otel.semconv-stability.opt-in=database</code>, including configured server targets and span names, endpoint validation, network-peer attributes, Redis namespaces, operation names, error types, query text, and connection pool metric names and database identity for Cassandra, ClickHouse, Couchbase, Elasticsearch, Geode, HBase, JDBC, Redis clients, MongoDB, OpenSearch, R2DBC, Spymemcached, and Vert.x. (<a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/19728";>#19728</a>, <a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/19747";>#19747</a>, <a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/19749";>#19749</a>, <a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/19753";>#19753</a>, <a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instru mentation/pull/19757">#19757</a>, <a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/19795";>#19795</a>, <a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/19830";>#19830</a>, <a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/19831";>#19831</a>, <a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/19832";>#19832</a>, <a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/19834";>#19834</a>, <a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/19838";>#19838</a>, <a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/19839";>#19839</a>, <a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/19844";>#19844</a>, <a href="https://redirect.github.com/open-telemetry/opentelemetry-java-inst rumentation/pull/19845">#19845</a>, <a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/19846";>#19846</a>, <a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/19848";>#19848</a>, <a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/19850";>#19850</a>, <a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/19864";>#19864</a>, <a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/19868";>#19868</a>, <a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/19872";>#19872</a>, <a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/19877";>#19877</a>, <a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/19883";>#19883</a>, <a href="https://redirect.github.com/open-telemetry/opentelemetry-java-in strumentation/pull/19901">#19901</a>, <a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/19902";>#19902</a>, <a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/19903";>#19903</a>, <a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/19904";>#19904</a>, <a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/19981";>#19981</a>, <a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/19983";>#19983</a>, <a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/19986";>#19986</a>, <a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/19988";>#19988</a>, <a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/20008";>#20008</a>, <a href="https://redirect.github.com/open-telemetry/opentelemetry-java- instrumentation/pull/20011">#20011</a>, <a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/20015";>#20015</a>, <a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/20017";>#20017</a>, <a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/20041";>#20041</a>, <a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/20065";>#20065</a>, <a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/20068";>#20068</a>, <a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/20070";>#20070</a>, <a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/20071";>#20071</a>, <a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/20072";>#20072</a>, <a href="https://redirect.github.com/open-telemetry/opentelemetry-jav a-instrumentation/pull/20073">#20073</a>, <a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/20074";>#20074</a>, <a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/20075";>#20075</a>, <a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/20076";>#20076</a>, <a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/20077";>#20077</a>, <a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/20078";>#20078</a>, <a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/20080";>#20080</a>, <a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/20082";>#20082</a>, <a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/20084";>#20084</a>, <a href="https://redirect.github.com/open-telemetry/opentelemetry-j ava-instrumentation/pull/20086">#20086</a>, <a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/20089";>#20089</a>, <a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/20105";>#20105</a>)</li> <li>Expand the upcoming 3.0 messaging semantic conventions behind <code>otel.semconv-stability.opt-in=messaging</code>, including operation-based spans, client and process metrics, per-message batch creation and propagation, consistent timestamps, durable subscription names, and duplicate processing suppression for Camel, Kafka Connect, JMS, SQS, and RocketMQ. (<a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/19483";>#19483</a>, <a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/19485";>#19485</a>, <a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/19503";>#19503</a>, <a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/19517";>#19517</a>, <a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/19915";>#19915</a>, <a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instr umentation/pull/20045">#20045</a>, <a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/20067";>#20067</a>, <a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/20144";>#20144</a>)</li> <li>Kafka spans and metrics now include <code>messaging.kafka.cluster.id</code> once cluster metadata is resolved. (<a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/18978";>#18978</a>)</li> <li>Add SQL database attributes to AWS SDK v2 RDS Data API <code>ExecuteStatement</code> and <code>BatchExecuteStatement</code> spans. (<a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/19259";>#19259</a>)</li> <li>Add <code>WARNING</code> logs for invalid or empty extension locations and failed extension JAR loads, plus <code>FINE</code> logs for successfully loaded extension JARs. (<a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/19584";>#19584</a>)</li> <li>The JMX metrics library now includes the experimental Kafka broker metrics target. (<a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/19722";>#19722</a>)</li> <li>Update the descriptions of <code>kafka.connect.connector.status</code> and <code>kafka.connect.task.status</code> to omit the listed supported state values. (<a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/19724";>#19724</a>)</li> <li>Geode database client spans now include <code>server.address</code> and <code>server.port</code> when the region's pool has exactly one configured server. (<a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/19748";>#19748</a>)</li> <li>Add exception-log support for HBase database clients, SofaRPC clients and servers, and GWT RPC with <code>otel.semconv.exception.signal.preview=logs</code>. (<a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/19750";>#19750</a>, <a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/20253";>#20253</a>, <a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/20254";>#20254</a>)</li> <li>Add <code>server.address</code> and <code>server.port</code> attributes to Couchbase database spans. (<a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/19758";>#19758</a>)</li> <li>Add metric-name filtering for JMX metrics with <code>otel.jmx.metrics.included</code> and <code>otel.jmx.metrics.excluded</code>, or <code>JmxTelemetryBuilder.setMetrics(IncludeExclude)</code> in the library. (<a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/19782";>#19782</a>)</li> <li>RabbitMQ spans now include <code>messaging.rabbitmq.vhost.name</code> and <code>messaging.rabbitmq.cluster.name</code> when <code>otel.instrumentation.rabbitmq.experimental-span-attributes=true</code>. (<a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/19822";>#19822</a>)</li> <li>JMX metric creation messages are now logged at <code>FINE</code> instead of <code>INFO</code>, reducing default log noise. (<a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/19825";>#19825</a>)</li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/open-telemetry/opentelemetry-java-instrumentation/blob/main/CHANGELOG.md";>io.opentelemetry.javaagent:opentelemetry-javaagent's changelog</a>.</em></p> <blockquote> <h2>Version 2.32.0 (2026-10-03)</h2> <p>This release targets the OpenTelemetry SDK 1.66.0.</p> <p>Note that many artifacts have the <code>-alpha</code> suffix attached to their version number, reflecting that they will continue to have breaking changes. Please see <a href="https://github.com/open-telemetry/opentelemetry-java-instrumentation/blob/main/VERSIONING.md#opentelemetry-java-instrumentation-versioning";>VERSIONING.md</a> for more details.</p> <h3>⚠️ Breaking changes to non-stable APIs</h3> <ul> <li>Remove the deprecated <code>HostIdResource.REGISTRY_QUERY</code> constant. (<a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/19778";>#19778</a>)</li> <li>The <code>ExperimentalJmxMetricHandler</code> SPI now requires implementations to provide <code>getMetricNames()</code>. (<a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/19781";>#19781</a>)</li> <li>Add the required <code>isRequestStreaming(REQUEST)</code> method to <code>GenAiAttributesGetter</code>. (<a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/19879";>#19879</a>)</li> <li>The experimental <code>java.common.messaging.headers/development</code> YAML selector no longer configures header capture. Use <code>java.common.messaging.headers</code> instead. (<a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/20260";>#20260</a>)</li> </ul> <h3>🚫 Deprecations</h3> <ul> <li>Deprecate <code>otel.jmx.target.system</code> in favor of <code>otel.jmx.metrics.experimental.included</code>. (<a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/19783";>#19783</a>)</li> <li>Deprecate <code>otel.instrumentation.elasticsearch.capture-search-query</code>. It will be removed in 3.0, when search query bodies are always captured. There is no replacement. (<a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/19675";>#19675</a>)</li> <li>Deprecate <code>otel.instrumentation.opensearch.capture-search-query</code>. It will be removed in 3.0, when search query bodies are always captured. There is no replacement. Sanitization remains enabled by default and configurable with <code>otel.instrumentation.opensearch.query-sanitization.enabled</code>. (<a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/19837";>#19837</a>)</li> <li>Deprecate <code>otel.jmx.enabled</code> in favor of <code>otel.instrumentation.jmx.enabled</code> to align with other instrumentation enablement properties. (<a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/19945";>#19945</a>)</li> <li>Deprecate automatic rewriting of <code>VirtualField.find(Class, Class)</code> calls in inlined javaagent advice. Instead, look up the <code>VirtualField</code> once and store it in a helper class's <code>static final</code> field. The <code>find</code> method itself remains supported. (<a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/19980";>#19980</a>)</li> <li>Deprecate the Elasticsearch REST library instrumentation. Use the Elasticsearch Java API Client's native OpenTelemetry support, or the Java agent for direct <code>RestClient</code> usage. Java agent instrumentation is unaffected. (<a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/pull/19995";>#19995</a>)</li> <li>Deprecate <code>otel.instrumentation.messaging.experimental.receive-telemetry.enabled</code> in favor of <code>otel.instrumentation.common.messaging.experimental.receive-telemetry.enabled</code>. For headers, replace <code>otel.instrumentation.messaging.experimental.headers.included</code> and <code>.excluded</code> with <code>otel.instrumentation.common.messaging.headers.included</code> and <code>.excluded</code>. Also deprecate <code>otel.instrumentation.messaging.experimental.capture-headers</code> in favor of <code>otel.instrumentation.common.messaging.headers.included</code>. Stable selectors take precedence per leaf.</li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/open-telemetry/opentelemetry-java-instrumentation/commit/1b8644f8eb11d90295b1c313391aa84edeeec6e2";><code>1b8644f</code></a> [release/v2.32.x] Prepare release 2.32.0 (<a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/issues/20364";>#20364</a>)</li> <li><a href="https://github.com/open-telemetry/opentelemetry-java-instrumentation/commit/9eaf312ef2bca0f96ccd2d6bea49fe2e242d2577";><code>9eaf312</code></a> Draft release notes (<a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/issues/20347";>#20347</a>)</li> <li><a href="https://github.com/open-telemetry/opentelemetry-java-instrumentation/commit/9f5c507f86c8383614f0de8edc446687f1045975";><code>9f5c507</code></a> Gate DBCP pool name retention on stable database semantic conventions (<a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/issues/20361";>#20361</a>)</li> <li><a href="https://github.com/open-telemetry/opentelemetry-java-instrumentation/commit/50f8bad8e7314e641e8b4e7ec2020cd43578b3a2";><code>50f8bad</code></a> Restore Renovate Java updates and fix Weaver digest pinning (<a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/issues/20360";>#20360</a>)</li> <li><a href="https://github.com/open-telemetry/opentelemetry-java-instrumentation/commit/5eea4918e5e20a91add620a79eccf2b50d73594b";><code>5eea491</code></a> Align v3-preview javaagent enablement selectors with module identities (<a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/issues/20305";>#20305</a>)</li> <li><a href="https://github.com/open-telemetry/opentelemetry-java-instrumentation/commit/647a9c3a1302d53a3cae3b969a3859fa3715da35";><code>647a9c3</code></a> Comment out regex manager from renovate weekly updates (<a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/issues/20341";>#20341</a>)</li> <li><a href="https://github.com/open-telemetry/opentelemetry-java-instrumentation/commit/4f9429ca51569638a2d1906f43daebc9687f0e5a";><code>4f9429c</code></a> Update pinned latest dep versions (<a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/issues/20349";>#20349</a>)</li> <li><a href="https://github.com/open-telemetry/opentelemetry-java-instrumentation/commit/12afa2c0e1da5754d2b7b4c7c66e52e4b898f2d7";><code>12afa2c</code></a> Handle unavailable references when drafting release notes (<a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/issues/20343";>#20343</a>)</li> <li><a href="https://github.com/open-telemetry/opentelemetry-java-instrumentation/commit/a401278c11b8b981526e818177a80f035adf5161";><code>a401278</code></a> Run native tests only on GraalVM 25 LTS (<a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/issues/20332";>#20332</a>)</li> <li><a href="https://github.com/open-telemetry/opentelemetry-java-instrumentation/commit/a3a0fca5f148465983a1fb4464d95dccc21aaf96";><code>a3a0fca</code></a> chore(deps): update jdx/mise-action action to v5 (<a href="https://redirect.github.com/open-telemetry/opentelemetry-java-instrumentation/issues/20316";>#20316</a>)</li> <li>Additional commits viewable in <a href="https://github.com/open-telemetry/opentelemetry-java-instrumentation/compare/v2.31.1...v2.32.0";>compare view</a></li> </ul> </details> <br /> [](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]
