Skip to content
This repository was archived by the owner on Nov 6, 2026. It is now read-only.

chore(deps): bump the quotes-backend-gradle group in /quotes-backend with 10 updates - #319

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/gradle/quotes-backend/quotes-backend-gradle-25fa8549bf
Open

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/gradle/quotes-backend/quotes-backend-gradle-25fa8549bf

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 1, 2026

Copy link
Copy Markdown
Contributor

Bumps the quotes-backend-gradle group in /quotes-backend with 10 updates:

Package From To
org.jetbrains.kotlinx:kotlinx-serialization-core 1.11.0 1.12.0
org.jetbrains.kotlinx:kotlinx-serialization-json 1.11.0 1.12.0
ch.qos.logback:logback-classic 1.6.5 1.6.6
io.opentelemetry.instrumentation:opentelemetry-logback-mdc-1.0 2.32.0-alpha 2.33.1-alpha
io.opentelemetry.instrumentation:opentelemetry-ktor-3.0 2.32.0-alpha 2.33.1-alpha
org.jetbrains.exposed:exposed-core 1.5.1 1.6.0
org.jetbrains.exposed:exposed-dao 1.5.1 1.6.0
org.jetbrains.exposed:exposed-jdbc 1.5.1 1.6.0
io.getunleash:unleash-client-java 12.3.0 12.3.1
gradle-wrapper 9.8.1 9.8.2

Updates org.jetbrains.kotlinx:kotlinx-serialization-core from 1.11.0 to 1.12.0

Release notes

Sourced from org.jetbrains.kotlinx:kotlinx-serialization-core's releases.

v1.12.0

This release is based on Kotlin 2.4.10 and contains all of the changes from 1.12.0-RC.

Additionally, it includes a fix removing unnecessary leading whitespaces from Proguard rules (#3270), and two changes stabilizing kotlin.uuid.Uuid serializer (#3263) and kotlin.time.Instant serializers (#3261).

For your convenience, the changelog for 1.12.0-RC is duplicated below:

API stabilization and deprecations

A big portion of the Json and Core APIs has been stabilized. Most important ones include: @KeepGeneratedSerializer and @SerialInfo annotations, JsonNamingStrategy, and ContextualSerializer. Additionally, various descriptor builders such as listDescriptor and JsonElementBuilder's addAll functions are also stable and can be freely used. There is also one deprecation: ChunkedDecoder interface. Since there is no demand for it, we plan to remove it in the future. See details in the #3238, #3239, and #3216.

Also, kotlin.time.Instant and kotlin.uuid.Uuid serializers are no longer annotated with experimental annotations from the Kotlin standard library (see #3261 and #3263)

Performance improvements

We also improved performance in various areas. ASCII-specific parser (#3225) brings performance of decoding from Okio and kotlinx-io sources closer to decoding performance from String. #3220 makes decoding significantly faster in case JsonElement present in your serializable classes. And #3248 should bring overall performance improvements (up to 30%) on large strings.

Exceptions rework

We continue to improve exception handling in Json encoders and decoders. #3235 makes a big change around custom serializers and @Serializable classes constructors: from now on, every exception thrown during deserialization is wrapped by decoder into a JsonException. This way, it is more predictable to write a catch and it is easier to understand what went wrong: JsonDecodingException also includes context information such as Json path and input. Besides that, #3246 limits maximum nesting depth of Json document, so you will get a proper JsonDecodingException instead of a random stack overflow error.

CBOR improvements

CBOR format also gets many improvements in this release. The most important one is memory optimization for definitely-sized collections (#3191, #3192).

The others include:

  • Encode unsigned integer types as positive integers (#3194) (thanks to Eyüp Can Akman)
  • Correctly decode CborLabel values (#3195)
  • Include actual tag info into CborDecodingException (#3197)

Protobuf improvements

Protocol buffers format received a big new feature: support for unknown fields. Using a new ProtoUnknownFieldHolder class, you can now decode and store unknown fields in Protobuf messages to retransmit them back later. See documentation updates and #2860 for details.

... (truncated)

Changelog

Sourced from org.jetbrains.kotlinx:kotlinx-serialization-core's changelog.

1.12.0 / 2026-10-19

This release is based on Kotlin 2.4.10 and contains all of the changes from 1.12.0-RC.

Additionally, it includes a fix removing unnecessary leading whitespaces from Proguard rules (#3270), and two changes stabilizing kotlin.uuid.Uuid serializer (#3263) and kotlin.time.Instant serializers (#3261).

For your convenience, the changelog for 1.12.0-RC is duplicated below:

API stabilization and deprecations

A big portion of the Json and Core APIs has been stabilized. Most important ones include: @KeepGeneratedSerializer and @SerialInfo annotations, JsonNamingStrategy, and ContextualSerializer. Additionally, various descriptor builders such as listDescriptor and JsonElementBuilder's addAll functions are also stable and can be freely used. There is also one deprecation: ChunkedDecoder interface. Since there is no demand for it, we plan to remove it in the future. See details in the #3238, #3239, and #3216.

Also, kotlin.time.Instant and kotlin.uuid.Uuid serializers are no longer annotated with experimental annotations from the Kotlin standard library (see [#3261](Kotlin/kotlinx.serialization#3261 and #3263)

Performance improvements

We also improved performance in various areas. ASCII-specific parser (#3225) brings performance of decoding from Okio and kotlinx-io sources closer to decoding performance from String. #3220 makes decoding significantly faster in case JsonElement present in your serializable classes. And #3248 should bring overall performance improvements (up to 30%) on large strings.

Exceptions rework

We continue to improve exception handling in Json encoders and decoders. #3235 makes a big change around custom serializers and @Serializable classes constructors: from now on, every exception thrown during deserialization is wrapped by decoder into a JsonException. This way, it is more predictable to write a catch and it is easier to understand what went wrong: JsonDecodingException also includes context information such as Json path and input. Besides that, #3246 limits maximum nesting depth of Json document, so you will get a proper JsonDecodingException instead of a random stack overflow error.

CBOR improvements

CBOR format also gets many improvements in this release. The most important one is memory optimization for definitely-sized collections (#3191, #3192).

... (truncated)

Commits

Updates org.jetbrains.kotlinx:kotlinx-serialization-json from 1.11.0 to 1.12.0

Release notes

Sourced from org.jetbrains.kotlinx:kotlinx-serialization-json's releases.

v1.12.0

This release is based on Kotlin 2.4.10 and contains all of the changes from 1.12.0-RC.

Additionally, it includes a fix removing unnecessary leading whitespaces from Proguard rules (#3270), and two changes stabilizing kotlin.uuid.Uuid serializer (#3263) and kotlin.time.Instant serializers (#3261).

For your convenience, the changelog for 1.12.0-RC is duplicated below:

API stabilization and deprecations

A big portion of the Json and Core APIs has been stabilized. Most important ones include: @KeepGeneratedSerializer and @SerialInfo annotations, JsonNamingStrategy, and ContextualSerializer. Additionally, various descriptor builders such as listDescriptor and JsonElementBuilder's addAll functions are also stable and can be freely used. There is also one deprecation: ChunkedDecoder interface. Since there is no demand for it, we plan to remove it in the future. See details in the #3238, #3239, and #3216.

Also, kotlin.time.Instant and kotlin.uuid.Uuid serializers are no longer annotated with experimental annotations from the Kotlin standard library (see #3261 and #3263)

Performance improvements

We also improved performance in various areas. ASCII-specific parser (#3225) brings performance of decoding from Okio and kotlinx-io sources closer to decoding performance from String. #3220 makes decoding significantly faster in case JsonElement present in your serializable classes. And #3248 should bring overall performance improvements (up to 30%) on large strings.

Exceptions rework

We continue to improve exception handling in Json encoders and decoders. #3235 makes a big change around custom serializers and @Serializable classes constructors: from now on, every exception thrown during deserialization is wrapped by decoder into a JsonException. This way, it is more predictable to write a catch and it is easier to understand what went wrong: JsonDecodingException also includes context information such as Json path and input. Besides that, #3246 limits maximum nesting depth of Json document, so you will get a proper JsonDecodingException instead of a random stack overflow error.

CBOR improvements

CBOR format also gets many improvements in this release. The most important one is memory optimization for definitely-sized collections (#3191, #3192).

The others include:

  • Encode unsigned integer types as positive integers (#3194) (thanks to Eyüp Can Akman)
  • Correctly decode CborLabel values (#3195)
  • Include actual tag info into CborDecodingException (#3197)

Protobuf improvements

Protocol buffers format received a big new feature: support for unknown fields. Using a new ProtoUnknownFieldHolder class, you can now decode and store unknown fields in Protobuf messages to retransmit them back later. See documentation updates and #2860 for details.

... (truncated)

Changelog

Sourced from org.jetbrains.kotlinx:kotlinx-serialization-json's changelog.

1.12.0 / 2026-10-19

This release is based on Kotlin 2.4.10 and contains all of the changes from 1.12.0-RC.

Additionally, it includes a fix removing unnecessary leading whitespaces from Proguard rules (#3270), and two changes stabilizing kotlin.uuid.Uuid serializer (#3263) and kotlin.time.Instant serializers (#3261).

For your convenience, the changelog for 1.12.0-RC is duplicated below:

API stabilization and deprecations

A big portion of the Json and Core APIs has been stabilized. Most important ones include: @KeepGeneratedSerializer and @SerialInfo annotations, JsonNamingStrategy, and ContextualSerializer. Additionally, various descriptor builders such as listDescriptor and JsonElementBuilder's addAll functions are also stable and can be freely used. There is also one deprecation: ChunkedDecoder interface. Since there is no demand for it, we plan to remove it in the future. See details in the #3238, #3239, and #3216.

Also, kotlin.time.Instant and kotlin.uuid.Uuid serializers are no longer annotated with experimental annotations from the Kotlin standard library (see [#3261](Kotlin/kotlinx.serialization#3261 and #3263)

Performance improvements

We also improved performance in various areas. ASCII-specific parser (#3225) brings performance of decoding from Okio and kotlinx-io sources closer to decoding performance from String. #3220 makes decoding significantly faster in case JsonElement present in your serializable classes. And #3248 should bring overall performance improvements (up to 30%) on large strings.

Exceptions rework

We continue to improve exception handling in Json encoders and decoders. #3235 makes a big change around custom serializers and @Serializable classes constructors: from now on, every exception thrown during deserialization is wrapped by decoder into a JsonException. This way, it is more predictable to write a catch and it is easier to understand what went wrong: JsonDecodingException also includes context information such as Json path and input. Besides that, #3246 limits maximum nesting depth of Json document, so you will get a proper JsonDecodingException instead of a random stack overflow error.

CBOR improvements

CBOR format also gets many improvements in this release. The most important one is memory optimization for definitely-sized collections (#3191, #3192).

... (truncated)

Commits

Updates org.jetbrains.kotlinx:kotlinx-serialization-json from 1.11.0 to 1.12.0

Release notes

Sourced from org.jetbrains.kotlinx:kotlinx-serialization-json's releases.

v1.12.0

This release is based on Kotlin 2.4.10 and contains all of the changes from 1.12.0-RC.

Additionally, it includes a fix removing unnecessary leading whitespaces from Proguard rules (#3270), and two changes stabilizing kotlin.uuid.Uuid serializer (#3263) and kotlin.time.Instant serializers (#3261).

For your convenience, the changelog for 1.12.0-RC is duplicated below:

API stabilization and deprecations

A big portion of the Json and Core APIs has been stabilized. Most important ones include: @KeepGeneratedSerializer and @SerialInfo annotations, JsonNamingStrategy, and ContextualSerializer. Additionally, various descriptor builders such as listDescriptor and JsonElementBuilder's addAll functions are also stable and can be freely used. There is also one deprecation: ChunkedDecoder interface. Since there is no demand for it, we plan to remove it in the future. See details in the #3238, #3239, and #3216.

Also, kotlin.time.Instant and kotlin.uuid.Uuid serializers are no longer annotated with experimental annotations from the Kotlin standard library (see #3261 and #3263)

Performance improvements

We also improved performance in various areas. ASCII-specific parser (#3225) brings performance of decoding from Okio and kotlinx-io sources closer to decoding performance from String. #3220 makes decoding significantly faster in case JsonElement present in your serializable classes. And #3248 should bring overall performance improvements (up to 30%) on large strings.

Exceptions rework

We continue to improve exception handling in Json encoders and decoders. #3235 makes a big change around custom serializers and @Serializable classes constructors: from now on, every exception thrown during deserialization is wrapped by decoder into a JsonException. This way, it is more predictable to write a catch and it is easier to understand what went wrong: JsonDecodingException also includes context information such as Json path and input. Besides that, #3246 limits maximum nesting depth of Json document, so you will get a proper JsonDecodingException instead of a random stack overflow error.

CBOR improvements

CBOR format also gets many improvements in this release. The most important one is memory optimization for definitely-sized collections (#3191, #3192).

The others include:

  • Encode unsigned integer types as positive integers (#3194) (thanks to Eyüp Can Akman)
  • Correctly decode CborLabel values (#3195)
  • Include actual tag info into CborDecodingException (#3197)

Protobuf improvements

Protocol buffers format received a big new feature: support for unknown fields. Using a new ProtoUnknownFieldHolder class, you can now decode and store unknown fields in Protobuf messages to retransmit them back later. See documentation updates and #2860 for details.

... (truncated)

Changelog

Sourced from org.jetbrains.kotlinx:kotlinx-serialization-json's changelog.

1.12.0 / 2026-10-19

This release is based on Kotlin 2.4.10 and contains all of the changes from 1.12.0-RC.

Additionally, it includes a fix removing unnecessary leading whitespaces from Proguard rules (#3270), and two changes stabilizing kotlin.uuid.Uuid serializer (#3263) and kotlin.time.Instant serializers (#3261).

For your convenience, the changelog for 1.12.0-RC is duplicated below:

API stabilization and deprecations

A big portion of the Json and Core APIs has been stabilized. Most important ones include: @KeepGeneratedSerializer and @SerialInfo annotations, JsonNamingStrategy, and ContextualSerializer. Additionally, various descriptor builders such as listDescriptor and JsonElementBuilder's addAll functions are also stable and can be freely used. There is also one deprecation: ChunkedDecoder interface. Since there is no demand for it, we plan to remove it in the future. See details in the #3238, #3239, and #3216.

Also, kotlin.time.Instant and kotlin.uuid.Uuid serializers are no longer annotated with experimental annotations from the Kotlin standard library (see [#3261](Kotlin/kotlinx.serialization#3261 and #3263)

Performance improvements

We also improved performance in various areas. ASCII-specific parser (#3225) brings performance of decoding from Okio and kotlinx-io sources closer to decoding performance from String. #3220 makes decoding significantly faster in case JsonElement present in your serializable classes. And #3248 should bring overall performance improvements (up to 30%) on large strings.

Exceptions rework

We continue to improve exception handling in Json encoders and decoders. #3235 makes a big change around custom serializers and @Serializable classes constructors: from now on, every exception thrown during deserialization is wrapped by decoder into a JsonException. This way, it is more predictable to write a catch and it is easier to understand what went wrong: JsonDecodingException also includes context information such as Json path and input. Besides that, #3246 limits maximum nesting depth of Json document, so you will get a proper JsonDecodingException instead of a random stack overflow error.

CBOR improvements

CBOR format also gets many improvements in this release. The most important one is memory optimization for definitely-sized collections (#3191, #3192).

... (truncated)

Commits

Updates ch.qos.logback:logback-classic from 1.6.5 to 1.6.6

Release notes

Sourced from ch.qos.logback:logback-classic's releases.

Logback 1.6.6

2026-10-25 Release of logback version 1.6.6

• LoggingEventVO now rejects, during deserialization, throwable proxies whose cause or suppressed entries point back into the graph of proxies, for example to their own parent. Such graphs cannot be produced by logback itself. However, a crafted stream sent to a socket receiver could use serialization back-references to build them, after which DefaultThrowableRenderer and SyslogAppender would loop forever and the recursive converters would overflow the stack. These streams are now rejected with an InvalidObjectException. Circular exceptions logged by the application are still transmitted correctly. This issue was reported and fixed in [PR #1079](qos-ch/logback#1079) by arfa-21.

• FileNamePattern now escapes characters with a special meaning in regular expressions, such as (, [ or +, when converting the literal parts of a file name pattern into a regex. Previously, RollingFileAppender failed to start when the path contained an unbalanced parenthesis, as in C:/Users/Michael(Financ. This issue was reported in issues/914 by danamlund. Moreover, with SizeAndTimeBasedRollingPolicy and a pattern such as app.%d.(%i).log, existing archives were not recognized. After a restart within the same period, the next rollover could overwrite an existing archive, and maxHistory and totalSizeCap never removed such archives. This issue was reported in issues/933 by GeoffreyBoulay. The fix was contributed in [PR #1077](qos-ch/logback#1077) by Jialin Chen. Regex metacharacters in %d{...} date patterns are now escaped as well.

• The conversion of date patterns into regular expressions now follows the rules of DateTimeFormatter, which logback uses to format dates, instead of those of SimpleDateFormat. In particular, the L (stand-alone month) pattern letter is now supported.

• SyslogOutputStream now connects its DatagramSocket to the syslog host. Previously, the socket was bound to the wildcard address, so that hardened environments saw an unconnected UDP listener on all interfaces for as long as the application ran. This issue was reported in issues/939 by joao-rebelo. The fix was contributed in [PR #1076](qos-ch/logback#1076) by Lyin-OTTF.

If the socket cannot be connected, for example because the network is not yet available, SyslogOutputStream falls back to an unconnected socket and SyslogAppenderBase emits a warning. When a datagram sent on a connected socket fails due to an ICMP "port unreachable" message caused by an earlier datagram, the datagram is sent once more so that no message is lost. If the retry also fails, a single warning is emitted instead of one error per event.

• OutputStreamAppender now stops its encoder when the appender is stopped. Previously, encoders holding resources until they were stopped, such as those of logstash-logback-encoder, were never released, causing heap growth at each reconfiguration. This issue was fixed in [PR #1072](qos-ch/logback#1072) by Samuel Fernandes.

• During variable substitution, an unmatched right curly brace now causes an error to be reported, with the original value left unchanged. Previously, the brace and all subsequent characters were silently dropped, so that %m}some text became %m. This issue was reported in issues/836 by philsttr.

• LogbackMDCAdapter now stores MDC entries in a LinkedHashMap, so that the %X converter outputs them in insertion order. This issue was reported in LOGBACK-1337 and fixed by Craig P. Motlin.

• A bit-wise identical binary of this version can be reproduced by building from source code at commit a9ee8019ee183e076ff5477957dbf90c4b04dd92 associated with the tag v_1.6.6. The release was built using Java "21" 2023-10-17 LTS build 21.0.1.+12-LTS-29 under Linux Debian 11.6.

Commits
  • a9ee801 prepare release 1.6.6
  • 7fa8e8e throw ScanException on unmatched '}' during variable substitution, fixes #836
  • 355b931 Test round trip of circular exceptions through LoggingEventVO
  • c7b8e2f reject cyclic throwable proxies in LoggingEventVO.readObject
  • 6217f11 fix loging of ThrowableProxy constructor taking isCyclic boolean
  • 0b95858 LOGBACK-1337 LogbackMDCAdapter should store mdc in LinkedHashMap to predict o...
  • 5c1f577 add LinkedHashMap to HardenedObjectInputStream whitelist
  • 7c36c71 Escape regex metacharacters in date patterns, harden rolling tests
  • d268774 Align date pattern to regex conversion with DateTimeFormatter
  • b4b4828 Escape regex metacharacters of literal text in FileNamePattern regexes
  • Additional commits viewable in compare view

Updates io.opentelemetry.instrumentation:opentelemetry-logback-mdc-1.0 from 2.32.0-alpha to 2.33.1-alpha

Release notes

Sourced from io.opentelemetry.instrumentation:opentelemetry-logback-mdc-1.0's releases.

Version 2.33.0

This release targets the OpenTelemetry SDK 1.67.0.

Note that many artifacts have the -alpha suffix attached to their version number, reflecting that they will continue to have breaking changes. Please see VERSIONING.md for more details.

📈 Enhancements

  • Update the OpenTelemetry SDK version to 1.67.0. (#20598)

🛠️ Bug fixes

  • Preserve repeated baggage header values when extracting context through the Java agent's OpenTelemetry API bridge. (#20598)
  • Avoid converting lists and maps to strings in Spring Boot declarative configuration. (#20598)
  • Improve SQL parsing. (#20864)

🙇 Thank you

This release was possible thanks to the following contributors who shared their brilliant ideas and awesome pull requests:

@​ishg @​jack-berg @​jamesylgan @​laurit @​opentelemetry-pr-dashboard @​safris @​steverao @​trask

Version 2.32.0

This release targets the OpenTelemetry SDK 1.66.0.

Note that many artifacts have the -alpha suffix attached to their version number, reflecting that they will continue to have breaking changes. Please see VERSIONING.md for more details.

⚠️ Breaking changes to non-stable APIs

  • Remove the deprecated HostIdResource.REGISTRY_QUERY constant. (#19778)
  • The ExperimentalJmxMetricHandler SPI now requires implementations to provide getMetricNames(). (#19781)
  • Add the required isRequestStreaming(REQUEST) method to GenAiAttributesGetter. (#19879)
  • The experimental java.common.messaging.headers/development YAML selector no longer configures header capture. Use java.common.messaging.headers instead. (#20260)

🚫 Deprecations

  • Deprecate otel.jmx.target.system in favor of otel.jmx.metrics.experimental.included. (#19783)
  • Deprecate otel.instrumentation.elasticsearch.capture-search-query. It will be removed in 3.0, when search query bodies are always captured. There is no replacement. (#19675)
  • Deprecate otel.instrumentation.opensearch.capture-search-query. 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 otel.instrumentation.opensearch.query-sanitization.enabled. (#19837)
  • Deprecate otel.jmx.enabled in favor of otel.instrumentation.jmx.enabled to align with other instrumentation enablement properties. (#19945)
  • Deprecate automatic rewriting of VirtualField.find(Class, Class) calls in inlined javaagent advice. Instead, look up the VirtualField once and store it in a helper class's static final field. The find method itself remains supported. (#19980)
  • Deprecate the Elasticsearch REST library instrumentation. Use the Elasticsearch Java API Client's native OpenTelemetry support, or the Java agent for direct RestClient usage. Java agent instrumentation is unaffected. (#19995)
  • Deprecate otel.instrumentation.messaging.experimental.receive-telemetry.enabled in favor of otel.instrumentation.common.messaging.experimental.receive-telemetry.enabled. For headers, replace otel.instrumentation.messaging.experimental.headers.included and .excluded with otel.instrumentation.common.messaging.headers.included and .excluded. Also deprecate otel.instrumentation.messaging.experimental.capture-headers in favor of otel.instrumentation.common.messaging.headers.included. Stable selectors take precedence per leaf. (#20060, #20260)
  • Deprecate the .included / .excluded properties under otel.instrumentation.log4j-appender.experimental.map-message-attributes, otel.instrumentation.logback-appender.experimental.key-value-pair-attributes, otel.instrumentation.logback-appender.experimental.logstash-marker-attributes, and otel.instrumentation.logback-appender.experimental.logstash-structured-argument-attributes in favor of the stable and unified otel.instrumentation.common.logging.structured-attributes.included / .excluded. (#20066)

... (truncated)

Changelog

Sourced from io.opentelemetry.instrumentation:opentelemetry-logback-mdc-1.0's changelog.

Changelog

Unreleased

⚠️ Breaking changes

  • Configured service mappings now emit server.service.name and server.service.namespace, and no longer emit peer.service, service.peer.name, or service.peer.namespace. Rename otel.instrumentation.common.peer-service-mapping to otel.instrumentation.common.server-service-mapping; in YAML, use java.common.server_service_mapping with target instead of peer.
  • Rename otel.instrumentation.grpc.{client,server}.request-metadata.{included,excluded} to otel.instrumentation.grpc.{client,server}.request-headers.{included,excluded}.
  • Captured gRPC request attributes now use rpc.request.header.<key> instead of rpc.request.metadata.<key>.
  • Rename messaging.system to messaging.system.name (aws_sqs becomes aws.sqs) and adopt the system-specific attribute renames from [semantic-conventions #4250](open-telemetry/semantic-conventions#4250). Experimental messaging attributes also lose the messaging. prefix (for example, messaging.kafka.bootstrap.servers becomes kafka.bootstrap.servers).
  • AWS Lambda invocation spans now replace alias suffixes in cloud.resource_id with the resolved function version when available.
  • AWS Lambda spans now use faas.invocation.id instead of faas.invocation_id for invocation IDs.
  • Replace SpringWebfluxClientTelemetry.addFilter(list) and addFilterAndRegisterReactorHook(list) with createFilter() and createFilterAndRegisterReactorHook(), used with WebClient.Builder.filter(...).
  • RPC telemetry now uses only the conventions with schema version 1.44.0: rpc.system.name, fully qualified rpc.method, rpc.status_code, and error.type, with updated span names. RPC duration metrics use rpc.client.call.duration and rpc.server.call.duration in seconds. RPC opt-in/preview flags and general.rpc.semconv settings no longer select legacy or dual emission.
  • GenAI error type getters now return the final value. Returning null omits error.type; overrides should return error == null ? null : error.getClass().getName() for the exception-class fallback.
  • HTTP client and server getters now determine error.type; their returned value, including null, is used as-is.
  • RPC attribute getters return the final error.type; returning null omits it even when an exception exists.
  • Messaging MessagingAttributesGetter.getErrorType() overrides now provide the final error.type value. Return null to omit it, or return error == null ? null : error.getClass().getName() for exception-class fallback.
  • Require R2DBC SPI 1.0 or later.
  • Rename the Spark Java instrumentation selector from spark-2.3 to spark-2.4.
  • Spring Boot Java agent resource providers move from io.opentelemetry.instrumentation.spring.resources to io.opentelemetry.javaagent.instrumentation.spring.boot.resources. Update class names in otel.java.enabled.resource.providers and otel.java.disabled.resource.providers.
  • Spring Rabbit 1.0 is no longer supported. Use the spring-rabbit-1.1 selector; telemetry scope changes from io.opentelemetry.spring-rabbit-1.0 to io.opentelemetry.spring-rabbit-1.1.
  • InstrumenterBuilder no longer infers a schema URL from attribute extractors. Call setSchemaUrl() with the schema for the conventions defining the instrumenter's signals; otherwise its telemetry has no schema URL.
  • Remove the Spring Boot starter-provided ConfigProperties bean in declarative mode. Read configuration through ConfigProvider and DeclarativeConfigProperties instead.
  • @WithSpan and @AddingSpanAttributes no longer allow targeting constructors (which didn't work properly anyways).

... (truncated)

Commits

Updates io.opentelemetry.instrumentation:opentelemetry-ktor-3.0 from 2.32.0-alpha to 2.33.1-alpha

Release notes

Sourced from io.opentelemetry.instrumentation:opentelemetry-ktor-3.0's releases.

Version 2.33.0

This release targets the OpenTelemetry SDK 1.67.0.

Note that many artifacts have the -alpha suffix attached to their version number, reflecting that they will continue to have breaking changes. Please see VERSIONING.md for more details.

📈 Enhancements

  • Update the OpenTelemetry SDK version to 1.67.0. (#20598)

🛠️ Bug fixes

  • Preserve repeated baggage header values when extracting context through the Java agent's OpenTelemetry API bridge. (#20598)
  • Avoid converting lists and maps to strings in Spring Boot declarative configuration. (#20598)
  • Improve SQL parsing. (#20864)

🙇 Thank you

This release was possible thanks to the following contributors who shared their brilliant ideas and awesome pull requests:

@​ishg @​jack-berg @​jamesylgan @​laurit @​opentelemetry-pr-dashboard @​safris @​steverao @​trask

Version 2.32.0

This release targets the OpenTelemetry SDK 1.66.0.

Note that many artifacts have the -alpha suffix attached to their version number, reflecting that they will continue to have breaking changes. Please see VERSIONING.md for more details.

⚠️ Breaking changes to non-stable APIs

  • Remove the deprecated HostIdResource.REGISTRY_QUERY constant. (#19778)
  • The ExperimentalJmxMetricHandler SPI now requires implementations to provide getMetricNames(). (#19781)
  • Add the required isRequestStreaming(REQUEST) method to GenAiAttributesGetter. (#19879)
  • The experimental java.common.messaging.headers/development YAML selector no longer configures header capture. Use java.common.messaging.headers instead. (#20260)

🚫 Deprecations

  • Deprecate otel.jmx.target.system in favor of otel.jmx.metrics.experimental.included. (#19783)
  • Deprecate otel.instrumentation.elasticsearch.capture-search-query. It will be removed in 3.0, when search query bodies are always captured. There is no replacement. (#19675)
  • Deprecate otel.instrumentation.opensearch.capture-search-query. 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 otel.instrumentation.opensearch.query-sanitization.enabled. (#19837)
  • Deprecate otel.jmx.enabled in favor of otel.instrumentation.jmx.enabled to align with other instrumentation enablement properties. (#19945)
  • Deprecate automatic rewriting of VirtualField.find(Class, Class) calls in inlined javaagent advice. Instead, look up the VirtualField once and store it in a helper class's static final field. The find method itself remains supported. (#19980)
  • Deprecate the Elasticsearch REST library instrumentation. Use the Elasticsearch Java API Client's native OpenTelemetry support, or the Java agent for direct RestClient usage. Java agent instrumentation is unaffected. (#19995)
  • Deprecate otel.instrumentation.messaging.experimental.receive-telemetry.enabled in favor of otel.instrumentation.common.messaging.experimental.receive-telemetry.enabled. For headers, replace otel.instrumentation.messaging.experimental.headers.included and .excluded with otel.instrumentation.common.messaging.headers.included and .excluded. Also deprecate otel.instrumentation.messaging.experimental.capture-headers in favor of otel.instrumentation.common.messaging.headers.included. Stable selectors take precedence per leaf. (#20060, #20260)
  • Deprecate the .included / .excluded properties under otel.instrumentation.log4j-appender.experimental.map-message-attributes, otel.instrumentation.logback-appender.experimental.key-v...

    Description has been truncated

Bumps the quotes-backend-gradle group in /quotes-backend with 10 updates:

| Package | From | To |
| --- | --- | --- |
| [org.jetbrains.kotlinx:kotlinx-serialization-core](https://github.com/Kotlin/kotlinx.serialization) | `1.11.0` | `1.12.0` |
| [org.jetbrains.kotlinx:kotlinx-serialization-json](https://github.com/Kotlin/kotlinx.serialization) | `1.11.0` | `1.12.0` |
| [ch.qos.logback:logback-classic](https://github.com/qos-ch/logback) | `1.6.5` | `1.6.6` |
| [io.opentelemetry.instrumentation:opentelemetry-logback-mdc-1.0](https://github.com/open-telemetry/opentelemetry-java-instrumentation) | `2.32.0-alpha` | `2.33.1-alpha` |
| [io.opentelemetry.instrumentation:opentelemetry-ktor-3.0](https://github.com/open-telemetry/opentelemetry-java-instrumentation) | `2.32.0-alpha` | `2.33.1-alpha` |
| [org.jetbrains.exposed:exposed-core](https://github.com/JetBrains/Exposed) | `1.5.1` | `1.6.0` |
| [org.jetbrains.exposed:exposed-dao](https://github.com/JetBrains/Exposed) | `1.5.1` | `1.6.0` |
| [org.jetbrains.exposed:exposed-jdbc](https://github.com/JetBrains/Exposed) | `1.5.1` | `1.6.0` |
| [io.getunleash:unleash-client-java](https://github.com/Unleash/unleash-java-sdk) | `12.3.0` | `12.3.1` |
| [gradle-wrapper](https://github.com/gradle/gradle) | `9.8.1` | `9.8.2` |


Updates `org.jetbrains.kotlinx:kotlinx-serialization-core` from 1.11.0 to 1.12.0
- [Release notes](https://github.com/Kotlin/kotlinx.serialization/releases)
- [Changelog](https://github.com/Kotlin/kotlinx.serialization/blob/master/CHANGELOG.md)
- [Commits](Kotlin/kotlinx.serialization@v1.11.0...v1.12.0)

Updates `org.jetbrains.kotlinx:kotlinx-serialization-json` from 1.11.0 to 1.12.0
- [Release notes](https://github.com/Kotlin/kotlinx.serialization/releases)
- [Changelog](https://github.com/Kotlin/kotlinx.serialization/blob/master/CHANGELOG.md)
- [Commits](Kotlin/kotlinx.serialization@v1.11.0...v1.12.0)

Updates `org.jetbrains.kotlinx:kotlinx-serialization-json` from 1.11.0 to 1.12.0
- [Release notes](https://github.com/Kotlin/kotlinx.serialization/releases)
- [Changelog](https://github.com/Kotlin/kotlinx.serialization/blob/master/CHANGELOG.md)
- [Commits](Kotlin/kotlinx.serialization@v1.11.0...v1.12.0)

Updates `ch.qos.logback:logback-classic` from 1.6.5 to 1.6.6
- [Release notes](https://github.com/qos-ch/logback/releases)
- [Commits](qos-ch/logback@v_1.6.5...v_1.6.6)

Updates `io.opentelemetry.instrumentation:opentelemetry-logback-mdc-1.0` from 2.32.0-alpha to 2.33.1-alpha
- [Release notes](https://github.com/open-telemetry/opentelemetry-java-instrumentation/releases)
- [Changelog](https://github.com/open-telemetry/opentelemetry-java-instrumentation/blob/main/CHANGELOG.md)
- [Commits](https://github.com/open-telemetry/opentelemetry-java-instrumentation/commits)

Updates `io.opentelemetry.instrumentation:opentelemetry-ktor-3.0` from 2.32.0-alpha to 2.33.1-alpha
- [Release notes](https://github.com/open-telemetry/opentelemetry-java-instrumentation/releases)
- [Changelog](https://github.com/open-telemetry/opentelemetry-java-instrumentation/blob/main/CHANGELOG.md)
- [Commits](https://github.com/open-telemetry/opentelemetry-java-instrumentation/commits)

Updates `io.opentelemetry.instrumentation:opentelemetry-ktor-3.0` from 2.32.0-alpha to 2.33.1-alpha
- [Release notes](https://github.com/open-telemetry/opentelemetry-java-instrumentation/releases)
- [Changelog](https://github.com/open-telemetry/opentelemetry-java-instrumentation/blob/main/CHANGELOG.md)
- [Commits](https://github.com/open-telemetry/opentelemetry-java-instrumentation/commits)

Updates `org.jetbrains.exposed:exposed-core` from 1.5.1 to 1.6.0
- [Release notes](https://github.com/JetBrains/Exposed/releases)
- [Changelog](https://github.com/JetBrains/Exposed/blob/main/CHANGELOG.md)
- [Commits](JetBrains/Exposed@1.5.1...1.6.0)

Updates `org.jetbrains.exposed:exposed-dao` from 1.5.1 to 1.6.0
- [Release notes](https://github.com/JetBrains/Exposed/releases)
- [Changelog](https://github.com/JetBrains/Exposed/blob/main/CHANGELOG.md)
- [Commits](JetBrains/Exposed@1.5.1...1.6.0)

Updates `org.jetbrains.exposed:exposed-jdbc` from 1.5.1 to 1.6.0
- [Release notes](https://github.com/JetBrains/Exposed/releases)
- [Changelog](https://github.com/JetBrains/Exposed/blob/main/CHANGELOG.md)
- [Commits](JetBrains/Exposed@1.5.1...1.6.0)

Updates `org.jetbrains.exposed:exposed-dao` from 1.5.1 to 1.6.0
- [Release notes](https://github.com/JetBrains/Exposed/releases)
- [Changelog](https://github.com/JetBrains/Exposed/blob/main/CHANGELOG.md)
- [Commits](JetBrains/Exposed@1.5.1...1.6.0)

Updates `org.jetbrains.exposed:exposed-jdbc` from 1.5.1 to 1.6.0
- [Release notes](https://github.com/JetBrains/Exposed/releases)
- [Changelog](https://github.com/JetBrains/Exposed/blob/main/CHANGELOG.md)
- [Commits](JetBrains/Exposed@1.5.1...1.6.0)

Updates `io.getunleash:unleash-client-java` from 12.3.0 to 12.3.1
- [Release notes](https://github.com/Unleash/unleash-java-sdk/releases)
- [Changelog](https://github.com/Unleash/unleash-java-sdk/blob/main/CHANGELOG.md)
- [Commits](Unleash/unleash-java-sdk@v12.3.0...v12.3.1)

Updates `gradle-wrapper` from 9.8.1 to 9.8.2
- [Release notes](https://github.com/gradle/gradle/releases)
- [Commits](gradle/gradle@v9.8.1...v9.8.2)

---
updated-dependencies:
- dependency-name: org.jetbrains.kotlinx:kotlinx-serialization-core
  dependency-version: 1.12.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: quotes-backend-gradle
- dependency-name: org.jetbrains.kotlinx:kotlinx-serialization-json
  dependency-version: 1.12.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: quotes-backend-gradle
- dependency-name: org.jetbrains.kotlinx:kotlinx-serialization-json
  dependency-version: 1.12.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: quotes-backend-gradle
- dependency-name: ch.qos.logback:logback-classic
  dependency-version: 1.6.6
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: quotes-backend-gradle
- dependency-name: io.opentelemetry.instrumentation:opentelemetry-logback-mdc-1.0
  dependency-version: 2.33.1-alpha
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: quotes-backend-gradle
- dependency-name: io.opentelemetry.instrumentation:opentelemetry-ktor-3.0
  dependency-version: 2.33.1-alpha
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: quotes-backend-gradle
- dependency-name: io.opentelemetry.instrumentation:opentelemetry-ktor-3.0
  dependency-version: 2.33.1-alpha
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: quotes-backend-gradle
- dependency-name: org.jetbrains.exposed:exposed-core
  dependency-version: 1.6.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: quotes-backend-gradle
- dependency-name: org.jetbrains.exposed:exposed-dao
  dependency-version: 1.6.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: quotes-backend-gradle
- dependency-name: org.jetbrains.exposed:exposed-jdbc
  dependency-version: 1.6.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: quotes-backend-gradle
- dependency-name: org.jetbrains.exposed:exposed-dao
  dependency-version: 1.6.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: quotes-backend-gradle
- dependency-name: org.jetbrains.exposed:exposed-jdbc
  dependency-version: 1.6.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: quotes-backend-gradle
- dependency-name: io.getunleash:unleash-client-java
  dependency-version: 12.3.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: quotes-backend-gradle
- dependency-name: gradle-wrapper
  dependency-version: 9.8.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: quotes-backend-gradle
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file java Pull requests that update Java code labels Nov 1, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

dependencies Pull requests that update a dependency file java Pull requests that update Java code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants