Releases: dotnet/MQTTnet
v3.0.0
-
[Core] Added support for MQTTv5 packages.
-
[Core] Performance improvements.
-
[Core] Removed obsolete methods.
-
[Core] Fixed a memory leak when processing lots of messages (thanks to @tschanko)
-
[Core] Added more overloads for MQTT factory.
-
[Core] The client password is now hidden from the logs (replaced with **** if set).
-
[Core] Fixed a memory leak when using SSL connections (thanks to @biovoid).
-
[Client] Added validation of topics before publishing.
-
[Client] Added new MQTTv5 features to options builder.
-
[Client] Added uniform API across all supported MQTT versions (BREAKING CHANGE!)
-
[Client] The client will now avoid sending an ACK if an exception has been thrown in message handler (thanks to @ramonsmits).
-
[Client] Fixed issues in QoS 2 handling which leads to message loss.
-
[Client] Replaced all events with proper async compatible handlers (BREAKING CHANGE!).
-
[Client] Added more configuration values to TCP endpoint options.
-
[Client] Added used PacketIdentifier to publish result.
-
[ManagedClient] Replaced all events with proper async compatible handlers (BREAKING CHANGE!).
-
[ManagedClient] The log ID is now propagated to the internal client (thanks to @vbBerni).
-
[ManagedClient] Added validation of topics before publishing.
-
[ManagedClient] The internal MQTT client is now closed properly (thanks to @vbBerni).
-
[Server] Added support for MQTTv5 clients. The server will still return success for all cases at the moment even if more granular codes are available.
-
[Server] Fixed issues in QoS 2 handling which leads to message loss.
-
[Server] Replaced all events with proper async compatible handlers (BREAKING CHANGE!).
-
[Server] The used logger instance is now propagated to the WebSocket server adapter.
-
[Server] Added the flag "IsSecureConnection" which is set to true when the connection is encrypted.
-
[Server] Fixed wrong will message behavior when stopping server (thanks to @JohBa)
-
[Server] Added validation of topics before publishing.
-
[Server] Added more configuration values to TCP endpoint options.
-
[MQTTnet Server] Added as first Alpha version of standalone cross platform MQTT server.
-
[Note] Due to MQTTv5 a lot of new classes were introduced. This required adding new namespaces as well. Most classes are backward compatible but new namespaces must be added.
v3.0.0-rc2
-
[Core] Added support for MQTTv5 packages.
-
[Core] Performance improvements.
-
[Core] Removed obsolete methods.
-
[Core] Fixed a memory leak when processing lots of messages (thanks to @tschanko)
-
[Core] Added more overloads for MQTT factory.
-
[Core] The client password is now hidden from the logs (replaced with **** if set).
-
[Core] Fixed a memory leak when using SSL connections (thanks to @biovoid).
-
[Client] Added validation of topics before publishing.
-
[Client] Added new MQTTv5 features to options builder.
-
[Client] Added uniform API across all supported MQTT versions (BREAKING CHANGE!)
-
[Client] The client will now avoid sending an ACK if an exception has been thrown in message handler (thanks to @ramonsmits).
-
[Client] Fixed issues in QoS 2 handling which leads to message loss.
-
[Client] Replaced all events with proper async compatible handlers (BREAKING CHANGE!).
-
[Client] Added more configuration values to TCP endpoint options.
-
[Client] Added used PacketIdentifier to publish result.
-
[ManagedClient] Replaced all events with proper async compatible handlers (BREAKING CHANGE!).
-
[ManagedClient] The log ID is now propagated to the internal client (thanks to @vbBerni).
-
[ManagedClient] Added validation of topics before publishing.
-
[ManagedClient] The internal MQTT client is now closed properly (thanks to @vbBerni).
-
[Server] Added support for MQTTv5 clients. The server will still return success for all cases at the moment even if more granular codes are available.
-
[Server] Fixed issues in QoS 2 handling which leads to message loss.
-
[Server] Replaced all events with proper async compatible handlers (BREAKING CHANGE!).
-
[Server] The used logger instance is now propagated to the WebSocket server adapter.
-
[Server] Added the flag "IsSecureConnection" which is set to true when the connection is encrypted.
-
[Server] Fixed wrong will message behavior when stopping server (thanks to @JohBa)
-
[Server] Added validation of topics before publishing.
-
[Server] Added more configuration values to TCP endpoint options.
-
[MQTTnet Server] Added as first Alpha version of standalone cross platform MQTT server.
-
[Note] Due to MQTTv5 a lot of new classes were introduced. This required adding new namespaces as well. Most classes are backward compatible but new namespaces must be added.
v3.0.0-beta1
-
[Core] Added support for MQTTv5 packages.
-
[Core] Performance improvements.
-
[Core] Removed obsolete methods.
-
[Core] Fixed a memory leak when processing lots of messages (thanks to @tschanko)
-
[Core] Added more overloads for MQTT factory.
-
[Core] The client password is now hidden from the logs (replaced with **** if set).
-
[Core] Fixed a memory leak when using SSL connections (thanks to @biovoid).
-
[Client] Added validation of topics before publishing.
-
[Client] Added new MQTTv5 features to options builder.
-
[Client] Added uniform API across all supported MQTT versions (BREAKING CHANGE!)
-
[Client] The client will now avoid sending an ACK if an exception has been thrown in message handler (thanks to @ramonsmits).
-
[Client] Fixed issues in QoS 2 handling which leads to message loss.
-
[Client] Replaced all events with proper async compatible handlers (BREAKING CHANGE!).
-
[Client] Added more configuration values to TCP endpoint options.
-
[ManagedClient] Replaced all events with proper async compatible handlers (BREAKING CHANGE!).
-
[ManagedClient] The log ID is now propagated to the internal client (thanks to @vbBerni).
-
[ManagedClient] Added validation of topics before publishing.
-
[ManagedClient] The internal MQTT client is now closed properly (thanks to @vbBerni).
-
[Server] Added support for MQTTv5 clients. The server will still return success for all cases at the moment even if more granular codes are available.
-
[Server] Fixed issues in QoS 2 handling which leads to message loss.
-
[Server] Replaced all events with proper async compatible handlers (BREAKING CHANGE!).
-
[Server] The used logger instance is now propagated to the WebSocket server adapter.
-
[Server] Added the flag "IsSecureConnection" which is set to true when the connection is encrypted.
-
[Server] Fixed wrong will message behavior when stopping server (thanks to @JohBa)
-
[Server] Added validation of topics before publishing.
-
[Server] Added more configuration values to TCP endpoint options.
-
[MQTTnet Server] Added as first Alpha version of standalone cross platform MQTT server.
-
[Note] Due to MQTTv5 a lot of new classes were introduced. This required adding new namespaces as well. Most classes are backward compatible but new namespaces must be added.
v3.0.0-alpha3
-
[Core] Added support for MQTTv5 packages.
-
[Core] Performance improvements (removed several exceptions).
-
[Core] Removed obsolete methods.
-
[Core] Fixed a memory leak when processing lots of messages (thanks to @tschanko)
-
[Core] Added more overloads for MQTT factory.
-
[Core] The client password is now hidden from the logs (replaced with **** if set).
-
[Client] Added validation of topics before publishing.
-
[Client] Added new MQTTv5 features to options builder.
-
[Client] Added uniform API across all supported MQTT versions (BREAKING CHANGE!)
-
[Client] The client will now avoid sending an ACK if an exception has been thrown in message handler (thanks to @ramonsmits).
-
[Client] Fixed issues in QoS 2 handling which leads to message loss.
-
[Client] Replaced all events with proper async compatible handlers (BREAKING CHANGE!).
-
[ManagedClient] Replaced all events with proper async compatible handlers (BREAKING CHANGE!).
-
[ManagedClient] The log ID is now propagated to the internal client (thanks to @vbBerni).
-
[ManagedClient] Added validation of topics before publishing.
-
[ManagedClient] The internal MQTT client is now closed properly (thanks to @vbBerni).
-
[Server] Added support for MQTTv5 clients. The server will still return success for all cases at the moment even if more granular codes are available.
-
[Server] Fixed issues in QoS 2 handling which leads to message loss.
-
[Server] Replaced all events with proper async compatible handlers (BREAKING CHANGE!).
-
[Server] The used logger instance is now propagated to the WebSocket server adapter.
-
[Server] Added the flag "IsSecureConnection" which is set to true when the connection is encrypted.
-
[Server] Fixed wrong will message behavior when stopping server (thanks to @JohBa)
-
[Server] Added validation of topics before publishing.
-
[MQTTnet Server] Added as first Alpha version of standalone cross platform MQTT server.
-
[Note] Due to MQTTv5 a lot of new classes were introduced. This required adding new namespaces as well. Most classes are backward compatible but new namespaces must be added.
v3.0.0-alpha1
- [Core] Added support for MQTTv5 packages.
- [Client] Added new MQTTv5 features to options builder.
- [Client] Added uniform API across all supported MQTT versions (BREAKING CHANGE!)
- [Server] Added support for MQTTv5 clients. The server will still return success for all cases at the moment even if more granular codes are available.
- [Note] Due to MQTTv5 a lot of new classes were introduced. This required adding new namespaces as well. Most classes are backward compatible but new namespaces must be added.
v2.8.5
- [Core] Updated nuget packages due to security issues.
- [Client] Fixed wrong behavior of publish method when client is disconnecting (thanks to @PaulFake).
- [Client] Added readonly property for accessing options.
- [ManagedClient] Added max pending messages count option.
- [ManagedClient] Add pending messages overflow strategy option.
- [ManagedClient] Fixed an issue which deletes the wrong message from the internal queue (thanks to @PaulFake).
- [ManagedClient] Added readonly property for accessing options.
- [Server] Added new method which exposes all retained messages.
- [Server] Removed (wrong) setter from the server options interface.
- [Server] Fixed cpu spike in case a client disconnects (issue 421).
- [Server] Fixed concurrent sends with Aspnetcore.Connections.Abstractions based transport.
- [Server] Fixed wrong retain flag when distributing application messages (thanks to @trev0115).
- [Server] Fixed issue which closes a connection when reconnecting with the same client ID (thanks to @fogzot).
v2.8.4
v2.8.3
- [Core] Added all factory methods to the factory interface.
- [Core] Fixed an issue with cancellation token handling (thanks to @acrabb).
- [Server] Added a new overload for configuring the ASP.net integration (thanks to @JanEggers).
- [Server] Added a method for clearing all retained messages.
v2.8.2
- [Core] Performance optimizations.
- [Client] Added support for proxies when using web socket connections (thanks to @PitySOFT).
- [Client] Refactored TLS parameter usage and added more parameters (thanks to @PitySOFT).
- [Client] Fixed a deadlock when clients are disconnecting (thanks to @JanEggers).
- [ManagedClient] Unsubscriptions are now pushed before subscriptions to support re-subscribing (thanks to @cstichlberger).
- [Server] Fixed an issue in client keep alive checks (thanks to @jenscski).
- [Server] Changed the order of ClientConnected and ClientDisconnected events so that ClientConnected is fired at first (thanks to @jenscski).
- [Server] Fixed an iussue which lets the server stop processing messages when using the application message interceptor (thanks to @alamsor).
- [Server] Fixed a deadlock when clients are disconnecting (thanks to @JanEggers).
v2.8.1
- [Core] Performance optimizations.
- [Core] Fixed a bug which prevents receiving large packets (UWP only)
- [Client] The ManagedClient options now allow configuring the interval for connection checks.
- [Server] Added the Endpoint of the Adapter (remote IP and port) to the connection validation callback.
- [Server] The ipv4 and ipv6 endpoint can be disabled now by setting the bound IP address to None.
- [Server] Fix a bug in the keep alive monitor which caused high CPU load (thanks to @GarageGadget).