# Redpanda v26.1.14

- Product: Redpanda (https://whatsnew.fyi/product/redpanda)
- Vendor: Redpanda Data
- Date: 2026-07-24
- Version: v26.1.14
- Original notes: https://github.com/redpanda-data/redpanda/releases/tag/v26.1.14
- Permalink: https://whatsnew.fyi/product/redpanda/releases/v26.1.14

What's New is an index, not a publisher: every entry below links to the vendor's own release notes, which are the authoritative source. Entries are labelled where they are hand-curated sample data, pre-releases, or drawn from a secondary source such as a developer blog.

Reuse: the summaries, labels and curation here are © What's New. Quote freely with attribution and a link back; wholesale republication of the corpus is not permitted — terms: https://whatsnew.fyi/terms. The vendors' own release notes remain their publishers'.

---

- **fixed** — Fixed a cloud-topics epoch fencing race where an epoch bump whose replication failed could later admit a stale-epoch write, poisoning the partition log and crashing all replicas of the partition
- **fixed** — Fixed a bug in OffsetForLeaderEpoch handling with tiered topics which could cause consumers to reset their fetch position to the beginning of the log held in cloud storage
- **fixed** — Fixed a potential crash in DescribeLogDirs
- **fixed** — HTTP Proxy: Consumer group fetches no longer fail indefinitely with offset_out_of_range after retention moves a topic's log start offset past 0; the consumer now recovers to the earliest available offset
- **fixed** — Fixed a raft pre-vote livelock where a follower recovering behind a live leader could repeatedly start elections, leaving partitions under-replicated and stalling acks=all produce with request timeouts
- **fixed** — Fixed a bug in which internal topics could be auto-created with the wrong topic properties
- **fixed** — Fixed allocation double free on no-op replication factor changes
- **added** — Added a schema_registry_replay_on_startup cluster property (default off) that hydrates the Schema Registry store at broker start-up rather than lazily on the first request
- **changed** — Avoid oversized allocations for some of the schema_registry and pandaproxy handler interfaces
- **changed** — HTTP Proxy: a consumer group now resumes from its committed offset on a fresh consumer instance instead of re-reading from the earliest available offset
- **changed** — Optimize the schema_registry recovery path by caching references when canonicalizing schemas
- **changed** — Schema Registry now replays the internal _schemas topic exactly once when recovering on startup, instead of running redundant concurrent replays; cold start of a large registry is significantly faster

##### Bug Fixes
* Fixed a cloud-topics epoch fencing race where an epoch bump whose replication failed could later admit a stale-epoch write, poisoning the partition log and crashing all replicas of the partition. by @Lazin in [#31140](https://github.com/redpanda-data/redpanda/pull/31140)
* Fixes a bug in `OffsetForLeaderEpoch` handling with `tiered` topics which could cause consumers to reset their fetch position to the beginning of the log held in cloud storage. by @WillemKauf in [#31074](https://github.com/redpanda-data/redpanda/pull/31074)
* Fixes a potential crash in `DescribeLogDirs` by @WillemKauf in [#31196](https://github.com/redpanda-data/redpanda/pull/31196)
* HTTP Proxy: Consumer group fetches no longer fail indefinitely with offset_out_of_range after retention moves a topic's log start offset past 0; the consumer now recovers to the earliest available offset (auto.offset.reset=earliest). by @bartoszpiekny-redpanda in [#31207](https://github.com/redpanda-data/redpanda/pull/31207)
* Lifecycle fix on groups by @joe-redpanda in [#31182](https://github.com/redpanda-data/redpanda/pull/31182)
* [#30885](https://github.com/redpanda-data/redpanda/issues/30885) Fixed a raft pre-vote livelock where a follower recovering behind a live leader could repeatedly start elections, leaving partitions under-replicated and stalling `acks=all` produce with request timeouts. by @stevenpall in [#30886](https://github.com/redpanda-data/redpanda/pull/30886)
* [#31238](https://github.com/redpanda-data/redpanda/issues/31238) Fixes a bug in which internal topics could be auto-created with the wrong topic properties by @WillemKauf in [#31239](https://github.com/redpanda-data/redpanda/pull/31239)
* fix allocation double free on no-op rf changes by @joe-redpanda in [#31116](https://github.com/redpanda-data/redpanda/pull/31116)

##### Improvements
* Added a \`schema_registry_replay_on_startup\` cluster property (default off) that hydrates the Schema Registry store at broker start-up rather than lazily on the first request. by @sjust-redpanda in [#31174](https://github.com/redpanda-data/redpanda/pull/31174)
* Avoid oversized allocations for some of the \`schema_registry\` and \`pandaproxy\` handler interfaces. by @WillemKauf in [#31200](https://github.com/redpanda-data/redpanda/pull/31200)
* HTTP Proxy: a consumer group now resumes from its committed offset on a fresh consumer instance instead of re-reading from the earliest available offset. by @bartoszpiekny-redpanda in [#31225](https://github.com/redpanda-data/redpanda/pull/31225)
* Optimize the \`schema_registry\` recovery path by caching references when canonicalizing schemas by @WillemKauf in [#31193](https://github.com/redpanda-data/redpanda/pull/31193)
* Schema Registry now replays the internal \`_schemas\` topic exactly once when recovering on startup, instead of running redundant concurrent replays; cold start of a large registry is significantly faster. by @sjust-redpanda in [#31174](https://github.com/redpanda-data/redpanda/pull/31174)

**Full Changelog**: https://github.com/redpanda-data/redpanda/compare/v26.1.13...v26.1.14