Sourced from github.com/nats-io/nats.go's releases.
Release v1.44.0
Changelog
Overview
This PR adds a
PushConsumer
implementation tojetstream
, allowing easier migration to new API while maintaining usage of push consumers. For now it only supports the callback-basedConsume()
, more consuming options will be added in future releases.ADDED
- Core NATS:
UserCredentialBytes()
Conn
option (#1877)- JetStream:
PushConsumer
implementation injetstream
package- Expose
ClientTrace
inJetStreamOptions
(#1886)- Service API:
- Expose
WithEndpointPendingLimits
option (#1899)- Legacy KeyValue:
Error()
method toKeyLister
andKeyWatcher
interfaces (#1889)FIXED
- Core NATS:
- Fix timeoutWriter not recovering after first error (#1896)
- JetStream:
Consumer.Next()
hangs after connection is closed (#1883)- Fixed stream info request for strict mode (#1887)
- Ordered consumer not closing on connection close (#1885)
- Return a more appropriate error when Subject Transform is not supported (#1416)
- Fix subject transform comparison. Thanks
@erikmansson
for the contribution (#1907)- Legacy JetStream:
- Use timeout from
JetStreamContext
if no deadline is set on ctx (#1909)- KeyValue:
Keys()
andListKeys()
returning duplicates (#1884)- Fix subject prefix for the Create/Update operation in KV store. Thanks
@SalvaChiLlo
for the contribution (#1903)CHANGED
- Change
DefaultSubPendingMsgsLimit
(#998)Complete Changes
https://github.com/nats-io/nats.go/compare/v1.43.0...v1.44.0
Release v1.43.0
Changelog
ADDED
- Core NATS:
- Add
nc.LocalAddr
, similar tonc.ConnectedAddr
(#1877)FIXED
- Service API:
- Fix stopping service not unsubscribing from all endpoints. Thanks
@arunsworld
for the contribution (#1872)
... (truncated)
7a260b8
Release v1.44.0 (#1910)dfcb02d
[FIXED] Use mirror-aware prefix when updating KV key (#1903)0bba2a9
[ADDED] PushConsumer implementation in jetstream package (#1785)627a9f6
[FIXED] KeyValue Keys() and ListKeys() returning duplicates (#1884)9743171
Merge pull request #1909
from nats-io/fix-watcher-timeout3bd15a8
[FIXED] Use timeout from JetStreamContext if no deadline is set on
ctx0fc96b1
[FIXED] Fix subject transform comparison (#1907)ea3ef92
[IMPROVED] Change DefaultSubPendingMsgsLimit comment to reflect actual
value ...f038fb4
[FIXED] Return a more appropriate error when subject transforms are not
suppo...ad6e34e
[FIXED] Ordered consumer not closing on connection close (#1885)Sourced from github.com/nats-io/nats-server/v2's releases.
Release v2.11.7
Changelog
Refer to the 2.11 Upgrade Guide for backwards compatibility notes with 2.10.x.
Go Version
- 1.24.5 (#7047)
Dependencies
Added
General
- The
SubjectMatchesFilter
function is now available as an exported function for embedded use (#7051)- The
leafz
monitoring endpoint now includes the connection ID (#7063)- The monitoring endpoint index page now includes the endpoint names on hover (#7066, #7087)
Improved
JetStream
- Consumers with inactivity thresholds should no longer age out before processing acks (#7107)
- The Raft layer will no longer request store state on each apply (#7109)
- Tombstones in Raft log compactions will now be written asynchronously, similar to purges (#7109)
- When enabling per-message TTLs on a stream, existing messages with the
Nats-TTL
header are now scanned and processed (#7117)Fixed
General
- Message header lookups with common prefixes will now return correctly in all cases, fixing a problem where the headers could be sensitive to ordering (#7065)
- Validate that the
default_sentinel
JWT is a bearer token for auth callout (7074)- The
$SYS.REQ.USER.INFO
endpoint should now only be answered by the local server, fixing cases where the endpoint may sometimes return without full connection details (#7089)JetStream
- The Raft layer will require recovery and snapshot handling at startup before campaigning for a leadership election, fixing a situation where a node could continue with an outdated stream (#7040)
- The Raft log will no longer be compacted until after a snapshot is written, improving crash resilience (#7043)
- A race condition when shutting down Raft nodes which could result in no snapshot being written has been fixed (#7045)
- Consumer pull requests that use
no_wait
orexpires
behaviour has been fixed with replicated consumers (#7046)- Pull consumers with an inactive threshold will now consider pending acks when determining inactivity, preventing the consumer from being deleted while messages are being processed (#7052)
- Push consumers will now correctly error when trying to configure priority groups (#7053)
- Committed entry objects will now be correctly returned to the pool on error, reducing allocations (#7064)
- The time hash wheel used for per-message TTLs now correctly detects and expires messages with TTLs over an hour, previously it could take double the expected time (#7070)
- A potential panic when selecting message blocks during TTL recovery has been fixed (#7072)
... (truncated)
df44964
Release v2.11.7b76090a
Cherry-picks for 2.11.7 (#7132)2e4c373
[FIXED] MaxBytes reservations underflow42af9b5
Release v2.11.7-RC.3da4971c
Cherry-picks for 2.11.7-RC.3 (#7127)abac833
[FIXED] Detect removed blocks with stale index.db29e0ee6
[IMPROVED] Recover TTL when enabled6bebdc0
Release v2.11.7-RC.2b3220a6
Cherry-picks for 2.11.7-RC.2 (#7115)6014f41
Fix typos in doc comments