Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion local-antora-playbook.yml
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ content:
- url: .
branches: HEAD
- url: https://github.com/redpanda-data/docs
branches: [main, v/*, shared, site-search]
branches: [DOC-2312-2311-2290-26.2-single-source, v/*, shared, site-search]
- url: https://github.com/redpanda-data/docs-site
branches: [main]
start_paths: [home, data-platform, self-managed]
Expand Down
12 changes: 12 additions & 0 deletions modules/get-started/pages/whats-new-cloud.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -19,6 +19,18 @@ Redpanda SQL is now available on GCP, for both BYOC and BYOVPC clusters. Run rea

Redpanda SQL is now available on BYOVPC clusters on AWS. Provision the required SQL-specific AWS resources using the Redpanda BYOVPC Terraform module, then supply them as customer-managed resources when enabling the SQL engine via the Cloud Console, Cloud API, or Terraform provider. See xref:sql:get-started/enable-sql-byovpc-aws.adoc[Enable Redpanda SQL on a BYOVPC Cluster on AWS].

=== Decode Iceberg keys, values, and headers independently

On BYOC clusters with Iceberg-enabled topics, the `redpanda.iceberg.mode` topic property now accepts a section-based syntax that lets you independently control how Redpanda translates the record key, value, and headers into the Iceberg table. You can decode keys and header values using a schema or store them as UTF-8 strings, instead of the default raw bytes. See xref:manage:iceberg/specify-iceberg-schema.adoc#configure-key-value-and-header-translation[Configure key, value, and header translation].

=== Resolve Iceberg topic schemas within a Schema Registry context

On BYOC clusters, you can now set the `redpanda.schema.registry.context` topic property on an Iceberg-enabled topic to resolve its schemas within a specific xref:manage:schema-reg/schema-reg-contexts.adoc[Schema Registry context] instead of the default context. See xref:manage:iceberg/specify-iceberg-schema.adoc#resolve-schemas-within-a-context[Resolve schemas within a Schema Registry context].

=== Expanded Kafka client validation

Redpanda now validates additional non-Java Kafka clients at their current versions, aligned with Kafka 4.x: confluent-kafka-go, Sarama, and confluent-kafka-python. See xref:develop:kafka-clients.adoc[Kafka Compatibility].
Comment on lines +30 to +32

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -e
printf '%s\n' '--- candidate files ---'
fd -i 'kafka|whats-new-cloud' . | head -80
printf '%s\n' '--- relevant references ---'
rg -n -i -C 3 'confluent-kafka-go|Sarama|confluent-kafka-python|current versions|Kafka Compatibility|Kafka 4\.x' . --glob '*.adoc' --glob '*.md' --glob '*.yaml' --glob '*.yml' | head -240

Repository: redpanda-data/cloud-docs

Length of output: 1649


🏁 Script executed:

#!/bin/bash
set -e
printf '%s\n' '--- Kafka compatibility outline ---'
ast-grep outline modules/develop/pages/kafka-clients.adoc
printf '%s\n' '--- Kafka compatibility contents ---'
cat -n modules/develop/pages/kafka-clients.adoc
printf '%s\n' '--- release-note context ---'
sed -n '1,45p' modules/get-started/pages/whats-new-cloud.adoc

Repository: redpanda-data/cloud-docs

Length of output: 4421


🏁 Script executed:

#!/bin/bash
set -e
printf '%s\n' '--- source include and repository configuration ---'
rg -n -C 4 'streaming:develop:kafka-clients|single-source|streaming' . --hidden -g '!*.lock' -g '!node_modules' | head -240
printf '%s\n' '--- git submodules and tracked references ---'
if test -f .gitmodules; then cat .gitmodules; else echo 'no .gitmodules'; fi
git ls-files | rg -i 'kafka-clients|antora|playbook|site\.yml|\.yml$|\.yaml$' | head -160
printf '%s\n' '--- all client-name occurrences in tracked content ---'
git grep -n -i -E 'confluent-kafka-go|Sarama|confluent-kafka-python|Kafka 4\.x|current versions' -- ':!modules/get-started/pages/whats-new-cloud.adoc' || true

Repository: redpanda-data/cloud-docs

Length of output: 24063


🏁 Script executed:

#!/bin/bash
set -e
repo='https://api.github.com/repos/redpanda-data/docs/contents/modules/develop/pages/kafka-clients.adoc'
for ref in main shared 'DOC-2312-2311-2290-cloud-26.2-single-source'; do
  printf '\n--- ref: %s ---\n' "$ref"
  url="${repo}?ref=$(printf '%s' "$ref" | sed 's/ /%20/g')"
  curl -fsSL "$url" | jq -r '.download_url // .message'
done
printf '\n--- matching remote branches ---\n'
git ls-remote --heads https://github.com/redpanda-data/docs.git \
  | grep -E 'DOC-2312-2311-2290-cloud-26\.2-single-source|refs/heads/(main|shared)$' || true

Repository: redpanda-data/cloud-docs

Length of output: 557


🏁 Script executed:

#!/bin/bash
set -e
for ref in main shared; do
  printf '\n--- docs/modules/develop/pages/kafka-clients.adoc @ %s ---\n' "$ref"
  curl -fsSL "https://raw.githubusercontent.com/redpanda-data/docs/$ref/modules/develop/pages/kafka-clients.adoc" \
    | tee "/tmp/kafka-clients-$ref.adoc" \
    | grep -in -E -C 5 'confluent-kafka-go|Sarama|confluent-kafka-python|version|Kafka 4' || true
done

Repository: redpanda-data/cloud-docs

Length of output: 484


🏁 Script executed:

#!/bin/bash
set -e
for ref in main shared; do
  out="/tmp/kafka-clients-$ref.adoc"
  printf '\n--- docs/modules/develop/pages/kafka-clients.adoc @ %s ---\n' "$ref"
  if curl -fsSL "https://raw.githubusercontent.com/redpanda-data/docs/$ref/modules/develop/pages/kafka-clients.adoc" > "$out"; then
    wc -c "$out"
    grep -in -E -C 6 'confluent-kafka-go|Sarama|confluent-kafka-python|version|Kafka 4' "$out" || true
  else
    echo 'not available'
  fi
done

Repository: redpanda-data/cloud-docs

Length of output: 4652


🏁 Script executed:

#!/bin/bash
set -e
src=/tmp/kafka-clients-main.adoc
test -s "$src"
python3 - "$src" <<'PY'
import re, sys
from pathlib import Path

source = Path(sys.argv[1]).read_text()
cloud = re.search(r'ifdef::env-cloud\[\]\n(.*?)endif::\[\]', source, re.S)
if not cloud:
    raise SystemExit("cloud conditional block not found")
cloud_text = cloud.group(1)
for name in ("confluent-kafka-go", "Sarama", "confluent-kafka-python"):
    print(f"{name}: {'present' if name in cloud_text else 'absent'}")
print("cloud block has explicit client version:", bool(re.search(r'\b(?:v|version\s*)\d+\.\d+', cloud_text, re.I)))
print("cloud block uses current-version wording:", bool(re.search(r'current versions?', cloud_text, re.I)))
release = Path("modules/get-started/pages/whats-new-cloud.adoc").read_text()
line = next(line for line in release.splitlines() if "Expanded Kafka client validation" in line or "current versions" in line)
print("release-note:", line)
PY

Repository: redpanda-data/cloud-docs

Length of output: 381


Document the validated client versions and expose them in the linked compatibility page.

The cloud-rendered page omits these three clients and lists no explicit versions, so this release note’s claim cannot be substantiated.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@modules/get-started/pages/whats-new-cloud.adoc` around lines 19 - 21, Update
the “Expanded Kafka client validation” release-note section to state the
validated versions for confluent-kafka-go, Sarama, and confluent-kafka-python,
and update the linked Kafka Compatibility page to include matching entries for
all three clients. Ensure the release note and compatibility table use the same
explicit version details.


== July 2026

=== Schema Registry contexts enabled by default
Expand Down
Loading