What's Changed
This new release of introduces a fix to cope with a change on nats-server v2.10.26. A change in nats-server now makes it possible for some API calls to result in a no responders
error., which on previous clients could manifest itself as JetStream not being enabled. This release ensures that the client will behave in an expected way. For consumers doing next()
and fetch()
the operation can fail. For consume()
the client will notify and start a backoff.
- [FIX] [JS] change: nats-server 2.10.26 emits no responder if stream/consumer are not found by @aricart in #750
Full Changelog: v1.29.2...v1.29.3