...
The current version of RMR is 1.0.43 which 44 which was pushed on July 31 August 6, 2019; it is recommended that Dockerfiles etc. be adjusted to pick this version up. The change affects the API by adding a single message type to the list of message type constants.
There were no API changes to this release; the last API changes (additional message type constants) were added to 1.0.38 (12 July, 2019). For a detailed description of API changes, and their related commits, please consult the CHANGES file at the top level of the RMR repo:
...
A transport mechanism is a "mid-layer" protocol which makes use of TCP/UDP and provides features such as automatic connection reestablishment and connection acceptance. RMR was originally built using the Nanomsg transport library, and was extended to use NNG (Nanomsg next generation) as NNG provides several enhancements, and Nanomsg has been all but abandoned from a maintenance perspective. While the underlying "wire" protocol of both NNG and Nanomsg are the same, the APIs are different; RMR has supported both mechanisms by supplying two sets of libraries (librmr and librmr_nng). At this point in time, NNG is stable, and as the support for Nanomsg is reduced, thus RMR will drop support for Nanomsg. In other words, beginning with version 1.0.44 only 45 (initally announced as happening in 1.0.44, but has been pushed by one) only librmr_nng will be included. This change should not have any impact on applications using RMR as the RMR API is not changing. The only change would be that applications using librmr will need to alter their build process to change the underlying RMR library to librmr_nng.
Developer Information
The following links are generally useful for developers writing applications (xAPPs) which make use of RMR.
...