This patch release includes the following changes:

Bug Fixes

• Fixed a bug in the subscription data encoding format that could cause the topic matching process to get stuck in rare cases. Thanks, @844028312, for reporting the issue (#87) and sharing the test data.
• Fixed an issue where a node may fail to start after a force kill during a splitting operation (a97adfc2a3f10639726f089ccf0678f82e225db5).
• Fixed an issue where the persistent session remains active even when the client is disconnected (d17eb3a466fc0514e838eab94a639aa392b05fce).
• Set the reason field of the DistError event.
• Corrected two scheduler names used in the inbox service to ensure the related metrics are distinguished.

Improvements

• Ensured the thread context classloader is set to PluginClassLoader during plugin instance creation to reduce potential ClassNotFoundException errors from the plugin's constructor.
• Set up pipeline handlers only after the connection is accepted by the rate limiter, improving memory usage when the connection rate exceeds the allowed rate.
• Added a withoutDisconnect field to the ByClient event to distinguish between two client-initiated disconnection situations.
• Reported ChannelError event with detailed reasons when a connection is rejected due to exceeding the configured rate.
• Ensured pipeline resources are closed properly during graceful shutdown (bc329a7b6d0d45ff1e54d07c7b230a03c9d19d9a).
• Improved the time spent loading tenant states during startup (55661964adfb1eabc9ae372c8a1922a056779b73).
• Stopped range splitting when the local store hits the maximum range limit (9c62c5e13ffaf824edb4c57f4c9781964f95e0d9).

Full Changelog: https://github.com/bifromqio/bifromq/compare/v3.1.0...v3.1.1