Opinionated, allocation-free MQTT 5 components for embedded systems:
minimqis the async MQTT 5 client.mqtt-rpcis a minimal MQTT 5 request/reply protocol with a matching Python client.mqtt-stagingstages bounded objects into application-owned storage and includes a matching Python sender.
Minimq owns MQTT session mechanics, not the network stack or application. The protocol crates likewise leave dispatch, storage, activation, and reboot policy to their applications. Each package has an independent version and release boundary.
Packages are released independently with cargo release -p <package> <level>;
inspect the default dry run before adding --execute. Protocol-crate releases
also update the matching Python package version, which is published separately.