yllibed / Zigbee2MqttAssistant

GUI for Zigbee2Mqtt running in docker and HASS.IO
447 stars 43 forks source link

Bump MQTTnet from 3.0.11 to 4.1.3.436 #455

Closed dependabot[bot] closed 1 year ago

dependabot[bot] commented 1 year ago

Bumps MQTTnet from 3.0.11 to 4.1.3.436.

Release notes

Sourced from MQTTnet's releases.

v4.1.3.436

  • [Core] Fixed several dead locks by implementing a new async signal (#1552)
  • [Client] All waiting tasks will now fail when the client connection gets closed. This fixes several freezes (#1561)
  • [ManagedClient] The topic is no longer declared as invalid if a topic alias is used (#1395)
  • [Server] Fixed duplicated invocation of the event ClientAcknowledgedPublishPacketAsync for QoS level 2 (#1550)
  • [Server] Fixed issue in upgrading and downgrading of QoS levels for subscriptions and retained messages (#1560)
  • [Server] Fixed memory leak when old sessions are discarded (#1553)
  • [Server] When using MQTTv5 the reason code NoMatchingSubscribers is returned when no client is subscribed to a published topic (#802)
  • [Server] Fix sending of duplicate messages with QoS > 0 when session is recovered, and session is reused (#1546)

v4.1.2.350

  • [Core] Fixed dead lock and race conditions in new AsyncLock implementation (#1542).
  • [Client] Fixed connection freeze when using Xamarin etc.

v4.1.1.318

  • [Core] MQTT Packets being sent over web socket transport are now setting the web socket frame boundaries correctly (#1499).
  • [Core] Add support for attaching and detaching events from different threads.
  • [Core] Fixed a deadlock in AsyncLock implementation (#1520).
  • [Client] Keep alive mechanism now uses the configured timeout value from the options (thanks to @​Stannieman, #1495).
  • [Client] The PingAsync will fallback to the timeout specified in the client options when the cancellation token cannot be cancelled.
  • [Server] A DISCONNECT packet is no longer sent to MQTT clients < 5.0.0 (thanks to @​logicaloud, #1506).
  • [Server] Improved "take over" process handling.

v4.1.0.247

  • [Core] Fixed not working removal of event handlers from async events (#1479).
  • [Client] Added support for passing the local endpoint (network card) which should be used (#1311).
  • [Client] Exposed PackageIdentifier in MqttApplicationMessageReceivedEventArgs (thanks to @​koepalex, #1466).
  • [Server] Added a new event (ClientAcknowledgedPublishPacketAsync) which is fired whenever a client acknowledges a PUBLISH packet (QoS 1 and 2, #487).
  • [Server] Exposed channel adapter (HTTP context etc.) in connection validation (#1125).
  • [Server] The event InterceptingPublishAsync is now also called for injected application messages (#1470).
  • [Server] Exposed session items in multiple events (#1291).

v4.0.2.221

  • [Core] Updated nuget packages.
  • [Core] The option IgnoreCertificateChainErrors is now respected (thanks to @​GodVenn, #1447).
  • [ManagedClient] The managed client now sends the entire topic filter including new MQTTv5 properties when subscribing.
  • [ManagedClient] Fixed wrong firing of ApplicationMessageSkippedAsync event (thanks to @​quackgizmo, #1460).
  • [Server] Fixed reporting of MaximumQoS in ConnAck packet (MQTTv5 only) (#1442).
  • [Server] Fix cross thread issue in session message storage for QoS 1 and 2.
  • [Server] The event ClientSubscribedTopicAsync is now fired after the subscription is completely processed internally (#1435).
  • [Server] Improved CPU usage on lower end machines (#788).

v4.0.1.184

  • [Client] Added the flag try_private (MQTT 3.1.1 Bridge) to client options (#1413).
  • [Client] Fixed MQTTv5 protocol violation in PUBLISH packets (#1423).
  • [Client] Added missing "WithWill..." methods in MqttClientOptionsBuilder.
  • [ManagedClient] Fixed wrong event args type for connected and disconnected events (#1432).
  • [Server] Fixed wrong handling of retained messages with QoS > 0 (#1434).
  • [Server] Connections with try_private flag (MQTT 3.1.1 Bridge) are now accepted (#1413).

... (truncated)

Commits
  • e4b07f2 Fix build errors
  • 4eb6e77 Fix build errors due to merge conflicts
  • db1fc76 1546 possible bug in server repeatedly sending the same message to client sub...
  • bfec9dc 802 client isnt being notified if message is not delivered (#1568)
  • 56f0a2c Fix validation of topic in managed client (#1567)
  • 5ee0bb4 1565 high cpu load from asyncsignal (#1566)
  • 5c74728 Fix client session takeover
  • 97c46be Update ReleaseNotes.md
  • e6c1ab4 Fail all waiting tasks when the client connection gets closed (#1563)
  • 6e1ec26 Update ReleaseNotes.md
  • Additional commits viewable in compare view


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
dependabot[bot] commented 1 year ago

Superseded by #460.