nats-io/nats-server v2.11.4 on GitHub

Changelog

Refer to the 2.11 Upgrade Guide for backwards compatibility notes with 2.10.x.

General

Log lines for TLS handshake errors now include the subject and SHA-256 hash of the certificate if known (#6883)

JetStream

Enforcing per-subject limits on streams after a state rebuild or retention policy change is now considerably faster (#6871)
Reduced allocations when finding the next message matching a filter in the filestore, which also improves the performance of calculating interest state on streams with an interest/WQ retention policy (#6908)

General

JetStream

Stream and consumer updates are no longer possible if all peers are offline, fixing a potential avenue for data loss (#6856)
The stream first sequence is now adjusted correctly when purging over interior delete gaps (#6861)
Consumer redeliveries are no longer incorrectly reported for consumers with a max deliver of 1 (#6877)
Avoid resetting the first and last sequences of a workqueue stream to zero after a crash with unflushed data (#6882)
Access time goroutines are now reference-counted and no longer leak (#6887)
Fixed a deadlock that could occur when using multi_last direct gets or when calculating the first sequence number for a consumer with a deliver-last-per-subject deliver policy (#6899)
A spelling error in a store error was fixed (#6895) Thanks to @cjohansen for the contribution!
A rare panic in the filestore has been fixed (#6912)
Direct gets will no longer return messages incorrectly with up_to_time or start_time in some configurations (#6911)
Fixed a panic in the stree that could occur when removing subject state tracking for a short subject (#6914)