nats-io/nats.net v2.0.2

NATS.Net v2.0.2

on GitHub

We are happy to announce the release of NATS.Net version 2.0.2, a minor update that brings a few new features and bug fixes.

• Support no-responders
• Support for slow consumer events
• Improvements to TLS certificate options
• Support for unit testing improvements with the introduction of optional INatsMsg<T> and INatsJSMsg<T> interfaces

What's Changed

• Adding support for the no_responders feature. by @stebet in #259
• Consumer notifications by @mtmk in #265
• Watcher fix and API naming fix by @mtmk in #273
• Added info and stats to services by @mtmk in #274
• Added slow consumer events by @mtmk in #276
• Read certificates as PEM strings or from files by @caleblloyd in #283
• handle no responders in NatsSubBase by @caleblloyd in #277
• Create an INatsJSMsg interface by @mtmk in #266
• Handle JetStream publish no-responders by @mtmk in #288
• TLS Check Certificate Revocation option by @mtmk in #287

New Contributors

• @stebet made their first contribution in #259

Full Changelog: v2.0.1...v2.0.2

Big thanks to our contributors @stebet, @paulomf and @to11mtm. You all rock! 🥇

Breaking changes

• No-responders being switched on you may now see a new NATSNoRespondersException in request-reply messaging and JetStream when a request is sent to a subject that has no subscribers. See NATS documentation for more information.

• Renamed INatsObjContext CreateObjectStore() method to CreateObjectStoreAsync()

• Slow consumers now will drop messages and raises an event when that happens. You can handle these events or if you need the old behaviour you can set SubPendingChannelFullMode to BoundedChannelFullMode.Wait in NatsOpts.

Give us a shout if you have any questions either on slack.nats.io dotnet channel or here on GitHub!

Don't forget to check out the documentation for guides and examples.

Happy coding! ❤️

Nuget Packages

NATS.Net

This is the main meta package containing all other packages except serialization.

dotnet add package NATS.Net --version 2.0.2

If you are not deploying Native AOT you can also use ad-hoc JSON serialization:

dotnet add package NATS.Client.Serializers.Json --version 2.0.2

Individual Packages

dotnet add package NATS.Client.Core --version 2.0.2
dotnet add package NATS.Client.Hosting --version 2.0.2
dotnet add package NATS.Client.JetStream --version 2.0.2
dotnet add package NATS.Client.KeyValueStore --version 2.0.2
dotnet add package NATS.Client.ObjectStore --version 2.0.2
dotnet add package NATS.Client.Services --version 2.0.2
dotnet add package NATS.Client.Serializers.Json --version 2.0.2