v0.45.1

[mqtt5 0.45.1] - 2026-10-01

Fixed

• max_queued_bytes_per_client now limits the memory a queue actually uses (#160). A queued message was counted by its payload length alone, so its topic, client id, user properties, content type, response topic, correlation data and the queue entry itself went uncounted, and a queue of small messages could occupy well over its configured byte limit. Each entry is now counted by QueuedMessage::footprint plus the queue's per-entry overhead, both when pushed and when reloaded from disk at startup. Queues of small messages now reach the byte limit, and start dropping their oldest entries, sooner than before.

Added

• QueuedMessage::footprint.