From d52f3bd2b07c31006b5d185f09ad735520caaa28 Mon Sep 17 00:00:00 2001 From: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com> Date: Thu, 19 Mar 2026 12:49:52 +0000 Subject: [PATCH 1/2] fix(changelog): split Java SDK 4.0.0 entry to avoid MDX parsing error MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The first changelog entry for v4.0.0 contained both a fenced code block and later inline backtick spans with angle brackets (Consumer). The changelog sanitizer's backtick-parity tracking gets confused by code fences, causing it to double-wrap the angle-bracket type — which breaks MDX parsing in the docs repo ( is interpreted as a JSX tag). Fix: split the single large summary into two separate feat entries so the code fence and the Consumer text are in different entries. Co-Authored-By: unknown <> --- generators/java/sdk/versions.yml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/generators/java/sdk/versions.yml b/generators/java/sdk/versions.yml index e1e585593def..44c2bcdab523 100644 --- a/generators/java/sdk/versions.yml +++ b/generators/java/sdk/versions.yml @@ -43,7 +43,8 @@ **Configurable reconnection** — `reconnectOptions(ReconnectOptions)` lets callers tune max retries, backoff delay, and queue size before calling `connect()`. - + type: feat + - summary: | **Generic `onMessage(Consumer)` handler** — fires for every incoming text frame with the raw JSON string, before type-specific dispatch. Useful for logging or custom routing. From da978b8f5d59d82d666eb5a2132119bcfce5bc64 Mon Sep 17 00:00:00 2001 From: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com> Date: Thu, 19 Mar 2026 13:08:43 +0000 Subject: [PATCH 2/2] fix(changelog): split entries with code fences and angle-bracket types Entries that combine fenced code blocks with inline backtick spans containing angle brackets (e.g. Consumer, OptionalNullable, SyncPagingIterable) get double-wrapped by sanitizeChangelogEntry, breaking MDX parsing in the docs repo. Fix: split affected entries so code fences and angle-bracket types are in separate summary blocks. This affects: - Java SDK v4.0.0: Consumer after code fence - Java SDK v3.11.0: OptionalNullable before code fences - Java SDK v0.10.1: SyncPagingIterable between code fences Co-Authored-By: unknown <> --- generators/java/sdk/versions.yml | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/generators/java/sdk/versions.yml b/generators/java/sdk/versions.yml index e1e585593def..cffb49fb5151 100644 --- a/generators/java/sdk/versions.yml +++ b/generators/java/sdk/versions.yml @@ -43,7 +43,8 @@ **Configurable reconnection** — `reconnectOptions(ReconnectOptions)` lets callers tune max retries, backoff delay, and queue size before calling `connect()`. - + type: feat + - summary: | **Generic `onMessage(Consumer)` handler** — fires for every incoming text frame with the raw JSON string, before type-specific dispatch. Useful for logging or custom routing. @@ -1684,6 +1685,9 @@ When enabled, optional nullable fields use `OptionalNullable` to distinguish between omitted fields, explicit null values, and actual values. This enables proper PATCH request semantics for APIs that need to differentiate between "not specified" and "set to null". + type: feat + - summary: | + Example `collapse-optional-nullable` configuration and usage: ```yaml customConfig: @@ -3204,7 +3208,7 @@ starting_after: optional response: ListUsersResponse ``` - + - | The generated `SyncPagingIterable` can then be used to traverse through the `User` objects: ```java