v26.1.15

[tyson-redpanda]

Bug Fixes

• Fix the registered config name for leader_balancer_node_mute_timeout. by @WillemKauf in #31360
• Fixes a bug in which L0 batches in a cloud topic forgot to preserve last_offset_delta in their header, leading to an under-declared last offset which can stall consumers, skip records, or halt exact-offset replication. by @WillemKauf in #31363
• Fixes a bug in which topics with min.compaction.lag.ms left unconfigured with produced batches holding timestamps in the future would be considered ineligible for compaction by @WillemKauf in #31459
• Fixes a bug in which transient TOPIC_AUTHORIZATION_FAILED errors and SASL authentication failures were possible during application of a controller snapshot. by @WillemKauf in #31437
• Fixes a bug where corrupted storage would not yield a bad CRC in returned record batches. by @andrwng in #31388
• Fixes a bug where having a cloud topic read replica on a given cluster would prevent L0 objects on that cluster from being garbage collected. by @andrwng in #31391
• Updating a Shadow Link that uses PLAIN authentication no longer fails when the password is omitted; the stored password is preserved. by @r-vasquez in #31421
• #31448 rpk connect install --connect-version no longer rejects versions with a
  segment of three or more digits, which had blocked pinning any Redpanda Connect
  release since 4.100.0. Malformed versions with trailing characters are now
  rejected during validation rather than failing at download. by @prakhargarg105 in #31449
• rpk security secrets list no longer truncates its output at 100 secrets. by @simon0191 in #31436
• rpk shadow create no longer fails secret-reference validation on clusters
  with more than one page of REDPANDA_CLUSTER-scoped secrets. by @simon0191 in #31436
• rpk shadow update in editor mode now replaces the entire Shadow Link configuration instead of merging changed fields, so list-valued fields (e.g. topic filters) can shrink or be cleared. by @r-vasquez in #31421

Improvements

• #31335 Fixes an issue where /v1/usage responses could cause oversized allocations for clusters with a large number of Iceberg-enabled topics. by @WillemKauf in #31337
• rpk cluster health will now display any nodes that may be in maintenance mode. by @alextreichler in #31352

Full Changelog: v26.1.14...v26.1.15

---

This discussion was created from the release v26.1.15.