AMQP-CPP 4.3.26

• The connection_name is now set when a connection is established (making connections better stand out in RabbitMQ UI)
• Added support for ConnectionHandler::onBlocked() and ConnectionHandler::onUnblocked()

AMQP-CPP 4.3.25

• the connection_name property is now set during connection setup, making the connection stand out more in rabbitmq UI
• fixed iterator invalidation / crash when a user space program publishes more messages as a result of an onAck/onNack callback in AMQP::Reliable

AMQP-CPP 4.3.24

• On connection setup we now send more meta-information about the client to the RabbitMQ to make it easier to find out what sort of application is connected.

AMQP-CPP 4.3.23

• The AMQP::LibEvHandler can now be prioritized
• The AMQP::MetaData, AMQP::Envelope and AMQP::Message classes now has methods to remove AMQP headers

AMQP-CPP 4.3.22

• AMQP::Envelope constructor now also accepts std::string_view
• AMQP::Envelope constructor can now also be used to preserve meta-properties

AMQP-CPP 4.3.21

• The publish() methods in the AMQP::Reliable and AMQP::Tagger classes now take std::string_view instead of std::string
• Added extra constructor to AMQP::Envelope to also accept "const char *" parameters for null-terminated strings

AMQP-CPP 4.3.20

• The library now at least requires C++17
• Many methods in Channel now take a std::string_view instead of a std::string
• The AMQP::Tagger, AMQP::Reliable and AMQP::Throttle classes now preserve the already installed error handlers in the wrapped channel

AMQP-CPP 4.3.19

• Fixed operator == for the AMQP::Address class
• Implemented consumer cancel notifications

AMQP-CPP 4.3.18

• "make install" now creates symlink for the libamqpcpp.so file that target the libamqpcpp.so.X.Y.Z file in the same directory (instead of an symlink to an absolute path)

AMQP-CPP 4.3.17

• More efficient assignment of callbacks (using move semantics)
• Fixed handling of large messages (size is now stored in 64 bit integers instead of 32 bit integers)
• Fixed issue with message brokers without a max frame size (we incorrectly treated this as max=0, so nothing was sent)
• Fixed race condition when setting up a TCP connection
• Fixed destructor of the Tagger class (used for publish-confirms) to unregister the callbacks that were installed on the wrapped channel