Forced-cluster restart rejects an out-of-range commit index
--force-new-clusterPreviously, a member could be permanently bricked when its backend consistent index was ahead of the last WAL entry or snapshot index. Now, startup returns an error instead of starting with an adjusted commit index beyond the available entries, and the failed restart leaves the WAL unchanged.
Show release-note lines
- Fix [`--force-new-cluster` permanently bricking a member whose backend consistent index is ahead of its WAL](https://github.com/etcd-io/etcd/pull/22688)github.com/etcd-io/etcd/blob/main/CHANGELOG/CHANGELOG-3.5.md