What's Changed
- Rust rewrite 🦀 by @mxmxchere in #82
or should that be unmentioned? After all the goal with the rewrite is that things do not change (too drastically). With that being said I am especially interested to hear of any problems that arose due to the change from v2 to v3, but I am also happy to hear when stuff did not change. Some minor changes I am aware of that I think are acceptable:
- the log format is slightly different, in the conversion log message the CAN frame is only displayed with the bytes that actually contain data (before it always contained 8 bytes)
- With an unreachable MQTT server can2mqtt now does not exit but tries to connect infinetely (this is also true for the startup)
- An error in the config file or an inaccessible config file now also does not lead to an exit of can2mqtt but the program retries until there is a valid version
- automatic builds for amd64 and armv7 and musl (brought down binary size by a few megabytes)
- automatic config file reloads with inotify
- convert modes all have tests and fuzz tests, GitHub action still missing for the latter #83
- the MQTT client id reports can2mqtt and version now
- support for macOS and windows is pretty safely out of the window now (socket-can and inotify are linux-only features I think)
- releases are also pushed to crates.io
Full Changelog: v2.3.2...v3.0.1