v2.14.2-RC.1Pre-release
Release v2.14.2-RC.1
Fixed 10
- Fix a race condition when handling subscription interest over routes
- Fix potential protocol-level corruption from rewriting $JS.ACK subjects
- Fix potential protocol-level corruption from buffer misuse in compressed WebSocket clients
- Fix a case where Raft peers were not correctly tracked after an inactivity stall during catchup
- Fix quorum calculation when bootstrapping the metalayer when gateway URLs resolve to multiple IP addresses
- Remove block skip check on streams with extremely high subject counts in filestore to prevent runaway CPU usage
- Fix a case where the filestore would not release a lock after handling a write error
- Make purge operations on both file and memory stores more consistent with each other
- Fix a case where the consumer lock would not release a lock after handling a start sequence error
- Apply configuration constraints to counter streams and message schedules to prevent incorrect usage patterns
Changelog
Refer to the 2.14 Upgrade Guide for backwards compatibility notes with 2.12.x. Please note that the 2.13.x version was skipped.
Go Version
- 1.26.3
Dependencies
- golang.org/x/crypto v0.52.0
- golang.org/x/sys v0.45.0
Fixed
General
- A race condition when handling subscription interest over routes has been fixed (#8235)
- Potential protocol-level corruption from rewriting
$JS.ACKsubjects has been fixed (#8242) - Potential protocol-level corruption from buffer misuse in compressed WebSocket clients has been fixed (#8244)
JetStream
- Fixed a case where Raft peers were not correctly tracked after an inactivity stall during catchup (#8226)
- Quorum needed is now calculated correctly when bootstrapping the metalayer when gateway URLs resolve to multiple IP addresses (#8238)
- The filestore no longer performs a block skip check on streams with extremely high subject counts, as it could result in runaway CPU usage (#8227)
- Fixed a case where the filestore would not release a lock after handling a write error (#8232)
- Purge operations on both file and memory stores are now more consistent with each other (#8241)
- Fixed a case where the consumer lock would not release a lock after handling a start sequence error (#8230)
- Counter streams and message schedules now have configuration constraints applied to prevent incorrect usage patterns (#8240)
Complete Changes
https://github.com/nats-io/nats-server/compare/v2.14.1...v2.14.2-RC.1