Redpanda 26.2.2
Features rpk sql debug bundle collects a diagnostic bundle from an Oxla (SQL) cluster. rpk generate grafana-dashboard gains a new operations-stretch dashboard: a Grafana dashboard for stretch clusters managed by the Redpanda Operator, covering cross-cluster raft health, StretchCluster member status, and operator reconcile health.
Also shipped Aug 22, 2026Redpanda in August 2026 →
MCP server
- Local MCP server deprecated: The local ElevenLabs MCP server and MCP player are deprecated in favor of the hosted MCP server. Both repositories are archived and will no longer receive updates.
Agents, Workers - Choose OAuth scopes for Wrangler and the Cloudflare API MCP server
Wrangler and the Cloudflare API MCP server now use optional OAuth scopes. During authorization, you can choose which optional scopes to grant instead of approving every scope requested by each client.
arize-phoenix-client: v3.3.0
3.3.0 (2026-08-22) Features pxi: enable phoenix-gql mutations by default with approval in manual mode (391d0dd)
More from RedpandaEvery Redpanda release →
Redpanda 26.1.17
Bug Fixes Fixed an issue where audit-log initialization unconditionally sent a CreateTopics request to the controller leader, causing authentication and the admin API to be rejected cluster-wide (with audit_failure_policy=reject ) for the duration of any prolonged leaderless state.
Redpanda 25.3.17
Features adds the cloud_storage_prefetch_segments_max cluster config which can be used to enable small segment prefetching in cloud storage. Bug Fixes Reverted the c-ares DNS resolver from 1.34.7 back to 1.34.6.
Redpanda 26.1.16
IMPORTANT: Do not install the 26.1.16 release. A critical bug was identified that has broad implications that can create instability for long-running clusters. This issue is fixed in 26.1.17. Please upgrade directly to 26.1.17 or 26.2.x Bug Fixes Fixed a crash that could occur when removing a partition with a very large number of log segments, e.g.
Redpanda 25.3.16
IMPORTANT: Do not install the 25.13.16 release. A critical bug was identified that has broad implications that can create instability for long-running clusters. This issue is fixed in 25.3.17.