ChangeLog.md in amqp-1.2.1 vs ChangeLog.md in amqp-1.3.0

@@ -1,15 +1,36 @@
-## Changes Between 1.2.0 and 1.2.1
+## Changes Between 1.2.x and 1.3.0
 
+### Exchange-to-Exchange Bindings Support
+
+amqp gem now supports [Exchange-to-Exchange Bindings](http://www.rabbitmq.com/e2e.html), a RabbitMQ
+extension.
+
+`AMQP::Exchange#bind` and `AMQP::Exchange#unbind` work very much like `AMQP::Queue#bind` and
+`AMQP::Queue#unbind`, with the argument exchange being the source one.
+
+Contributed by Stefan Kaes.
+
+### Internal Exchange Declaration
+
+amqp gem now supports declaration of internal exchanges
+(used via exchange-to-exchange bindings, cannot be published to
+by clients).
+
+To declare an exchange as internal, add `:internal => true` to
+declaration options.
+
+Contributed by Stefan Kaes.
+
+
 ### Initial Connection Failures Retries
 
 Set connection status to closed on connection failure, which
 means connection retries succeed.
 
 Contributed by Marius Hanne.
 
-
 ## Changes Between 1.1.0 and 1.2.0
 
 ### [Authentication Failure Notification](http://www.rabbitmq.com/auth-notification.html) Support
 
 amqp gem now supports [Authentication Failure
@@ -50,13 +71,9 @@
 
 ### ConnectionClosedError is Back
 
 `ConnectionClosedError` from `amq-client` is now defined again.
 
-
-### amq-protocol Update
-
-Minimum `amq-protocol` version is now `1.9.0`.
 
 ### Fixed Exceptions in AMQP::Exchange#handle_declare_ok
 
 `AMQP::Exchange#handle_declare_ok` no longer raises an exception
 about undefined methods `#anonymous?` and `#exchange`.