v1.27.0

What's Changed

Small fixes to NATS core functionality and JetStream

• [FIX] [CORE] fixed an issue where permission errors related queue subscriptions was not properly notified to the client by @aricart in #701
• [FIX] [CORE] account expired protocol message was not notified properly by @aricart in #702
• [FEAT] [CORE] added connect option resolve, which allows a client to opt out of hostname resolution by @aricart in #704
• [FIX] [KV] fixed an issue where maxBucketSize (deprecated option) overrode max_bytes by @aricart in #707
• [FIX] [JS] honor JS timeout in ackAck() and also allow to override by @aricart in #708
• [FEAT] [KV] added support for listing keys with multiple filters by @aricart in #710
• [BUMP] ci dependencies and client version by @aricart in #711

Full Changelog: v1.26.0...v1.27.0

v1.26.0

What's Changed

• [FIX] [JS] [CONSUMERS] improved ordered pull consumer - api calls on the consumer no longer re-create the consumer - this reduces the number of consumer resets to only cases where there are errors or delivery sequence mismatches by @aricart in #699
• [BUMP] deno and client version by @aricart in #700

Full Changelog: v1.25.0...v1.26.0

v1.25.0

What's Changed

• [FEAT] [JS] [CONSUMERS] added name_prefix option to ordered consumer that specifies an user-provided prefix to add to generated consumer names by @aricart in #697

Full Changelog: v1.24.0...v1.25.0

v1.24.0

What's Changed

The following fixes are related to ordered push consumers and watchers for KV and ObjectStore.

• [FIX] more robust watcher in case consumer is recreated while the cluster is flapping by @aricart in #693
• [FIX] legacy order consumer subscription leak by @aricart in #694
• [BUMP] deno to 1.43.1 and client version by @aricart in #695

Full Changelog: v1.23.0...v1.24.0

v1.23.0

What's Changed

This release has some small set of important enhancements and fixes for the Nats-Base-Library:

• Kv watcher reliability is improved in cases where the server may restart.
• Kv watchers/history support multiple filters

In more detail:

• [FIX] [JETSTREAM] [KV] Kv Watcher reliability during server restarts by @aricart in #689
• [FEAT] [JETSTREAM] [KV] support multiple key filters on watchers/history by @aricart in #681
• [INTERNAL] mechanism to retrieve connection info by @aricart in #684
• [FIX] exposed Publisher type for downstream consumption by @aricart in #685
• [FEAT] [CORE] added the ability to publish by providing a Msg argument by @aricart in #686
• [CHANGE] moved nanos() and millis() to nats-base-client as they are referenced by the base library by @aricart in #687

Full Changelog: v1.22.0...v1.23.0

v1.22.0

What's Changed

This release adds the connection option handshakeFirst which enables the client to connect with a nats-server that has been configured with a handshake_first tis option set to true. And has one important fix to JetStream ackAck().

• [FIX] [JS] fix incorrect type in implementation of jetstream() api - it is correct in the interface. by @aricart in #675
• [FIX] [JS] ackAck() always not always waiting for proper response and could return false by @aricart in #676
• [BUMP] deno to 1.42.1, and std to 0.221.0 by @mtmk in #678
• [DOC] updated docs by @aricart in #677
• [TEST] cleanup of test data and configurations by @aricart in #679
• [CI] cleanup of test data and configurations by @aricart in #680
• [FEAT] [CORE] handshake_first support by @aricart in #682
• [DOC] added handshakeFirst tls option by @aricart in #683

New Contributors

• @mtmk made their first contribution in #678

Full Changelog: v1.21.0...v1.22.0

v1.21.0

What's Changed

This release slightly changes the behavior of consumers under the new consumer API for fetch() and next(). These operations are now succeptible to consumer deleted type errors. Since these operations are expected to finish at some point (when the number of requested messages is retrieved or when the operation expires) it seems appropriate to telegraph these errors. If your service expects to recover, it can re-issue the next() or fetch request again. For consume(), a new option was added abort_on_missing_resource which instructs the client to cancel if it detects that the stream or the consumer are gone. By default the client will attempt to consumer again.. These options are rejected for order consumer. For more information see #667

Also notable is the addition of a bind option for consume(), fetch(), and next(). This option will NOT check the status of the consumer or if there's an error during a request for messages. Note that in most cases if the consumer is deleted these will surface as heartbeats missed on the consumer status. For fetch() and next() these will result on no messages. Note that when this option is issued the client cannot provide a more precise status. Note that this option is not applicable to ordered consumers. For more information see #668

• [FEAT] [JS] [KV] allow internal kv watch consumer to use filtered consumer api by @aricart in #662
• [CHANGE] [JS] [CONSUMERS] fetch()/next() can fail on consumer/stream errors by @aricart in #667
• [FEAT] [JS] [CONSUMERS] added a bind option to the consume(), fetch(), next() - note this option is not supported in ordered consumers. by @aricart in #668
• [FEAT] [JS] jetstream options also support jsm options by @ramonberrutti in #666 and #669
• [FIX] [JS] jetstreamManager(checkAPI) overrode the checkAPI option incorrectly by @aricart in #672
• [TEST] fix timer leak detected by tests on consumer reset by @aricart in #664
• [FEAT] [CORE] enhancements to downstream iterator use to determine if the iterator failed by @aricart in #665

New Contributors

• @ramonberrutti made their first contribution in #666

Full Changelog: v1.20.1...v1.21.0

v1.20.1

What's Changed

• [FIX] [BUILD] tsc issue affecting downstream clients that rely on tsc for building. by @aricart in #659
• [FEAT] [KV] delete and purge at seq by @aricart in #656
• [LINTER] fixed linter and deprecation warnings by @aricart in #660
• [FIX] [KV] bind doesn't auto-initiate stream info by @aricart in #661

Full Changelog: v1.20.0...v1.20.1

v1.20.0

What's Changed

• [FEAT] [KV] Start a watcher at a specific revision, added KvWatchOptions.resumeFromRevision by @aricart in #651
• [FIX] [KV] KvWatchInclude was exported as a typescript type, but it shouldn't have been - it is an enum. by @aricart in #658
• [FIX] [JS] [ORDERED CONSUMER] Replay policy not re-set when recreating by @aricart in #655
• [FEAT] [JS] Create a paused consumer and JSM APIs to pause and resume a consumer - this feature requires nats-server 2.11.0 or better by @aricart in #653
• [FEAT] [JS] [INTERNAL] Direct batch by @aricart in #654
• [FIX] Remove initialization from nuid module creation until invoked. by @aricart in #649

Full Changelog: v1.19.0...v1.20.0

v1.19.0

What's Changed

• [DOC] Add nats by example link by @Jarema in #635
• [FIX] [JETSTREAM] stream names lister streams fails with NPE when no streams are defined by @aricart in #636
• [DEBUG] close trace by @aricart in #640
• [FIX] [JETSTREAM] prevent consumer deleted from stopping iterator by @aricart in #641
• [FIX] [JETSTREAM] added a status notification if the stream is deleted while a consumer in a disconnect cycle by @aricart in #638
• [FIX] Allow downstream implementations of url parse to know whether we are connected securely or not by @aricart in #642
• [FEAT] cluster tool enhancements and features by @aricart in #643, #639 and #644
• [BUMP] client version by @aricart in #645

Full Changelog: v1.18.0...v1.19.0