bunny 2.0.1 → 2.1.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: f393384482cb5e911c71c192c961adbef6c48a8b
-  data.tar.gz: 1ddb4e29292650bc3d1bff25b53b938cda35c44b
+  metadata.gz: 4c95090be1c7c3802f91e9bbde8a65145be46036
+  data.tar.gz: dba06fb978dcbdc3613e25dd6dc6d2ae6520e114
 SHA512:
-  metadata.gz: 634808e10988e3211a875a6851886b4c33a191ea81d796193eecefe1b9603cdd2996f90ea55d7e156498cca3c35077606334abc788af2b2cec03755b77fe2b41
-  data.tar.gz: 45ea52f14a6f5e1ded3418dadb897684c3052040d76ca1fed6a1680b9d5f3439cdd66063ac77e073304633ac2afb33648e00e39c0719559345b472ec685e068c
+  metadata.gz: 33990cab5ebb80edd6c95b33da3e1c1c572830acc8fa9a2d177340ca88fd9a40907c68507505736096eb8595d64ffa23fd560633d9f50edc3068e7ec55806035
+  data.tar.gz: 209a580762f599be1a69ba24c6aab533891a54f5e55f82920e258bb886205c0e96849ad165b2a4a86f9bd3aed6be71f21b9aa4ecc5e6201edfb310396bf1380e

data/ChangeLog.md

@@ -1,4 +1,24 @@
-## Changes between Bunny 2.0.0 and 2.0.1
+## Changes between Bunny 2.0.0 and 2.1.0
+
+Bunny 2.1.0 has an **important breaking change**. It is highly
+advised that 2.1.0 is not mixed with earlier versions of Bunny
+in case your applications include **integers in message headers**.
+
+### Integer Value Serialisation in Headers
+
+Integer values in headers are now serialised as signed 64-bit integers. Previously
+they were serialised as 32-bit unsigned integers, causing both underflows
+and overflows: incorrect values were observed by consumers.
+
+It is highly
+advised that 2.1.0 is not mixed with earlier versions of Bunny
+in case your applications include integers in message headers.
+
+If that's not the case, Bunny 2.1 will integeroperate with any earlier version
+starting with 0.9.0 just fine. Popular clients in other languages
+(e.g. Java and .NET) will interoperate with Bunny 2.1.0 without
+issues.
+
 
 ### Explicit Ruby 2.0 Requirement
 

data/README.md

@@ -49,7 +49,6 @@ Specific examples:
 Modern Bunny versions support
 
  * CRuby 2.2, 2.1, 2.0
- * Rubinius 2.0+
 
 Bunny works sufficiently well on JRuby but there are known
 JRuby bugs that cause high CPU burn. JRuby users should
@@ -97,7 +96,7 @@ gem install bunny
 To use Bunny in a project managed with Bundler:
 
 ``` ruby
-gem "bunny", ">= 1.7.0"
+gem "bunny", ">= 2.0.1"
 ```
 
 

data/bunny.gemspec

@@ -30,7 +30,7 @@ Gem::Specification.new do |s|
     map { |mail| Base64.decode64(mail) }
 
   # Dependencies
-  s.add_dependency "amq-protocol", ">= 1.9.2"
+  s.add_dependency "amq-protocol", ">= 2.0.0"
 
   # Files.
   s.has_rdoc = true

data/lib/bunny/version.rb

@@ -2,5 +2,5 @@
 
 module Bunny
   # @return [String] Version of the library
-  VERSION = "2.0.1"
+  VERSION = "2.1.0"
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: bunny
 version: !ruby/object:Gem::Version
-  version: 2.0.1
+  version: 2.1.0
 platform: ruby
 authors:
 - Chris Duncan
@@ -12,7 +12,7 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2015-08-07 00:00:00.000000000 Z
+date: 2015-08-16 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: amq-protocol
@@ -20,14 +20,14 @@ dependencies:
     requirements:
     - - ">="
       - !ruby/object:Gem::Version
-        version: 1.9.2
+        version: 2.0.0
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - ">="
       - !ruby/object:Gem::Version
-        version: 1.9.2
+        version: 2.0.0
 description: Easy to use, feature complete Ruby client for RabbitMQ 3.3 and later
   versions.
 email:
@@ -232,7 +232,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: '0'
 requirements: []
 rubyforge_project: 
-rubygems_version: 2.4.6
+rubygems_version: 2.4.8
 signing_key: 
 specification_version: 4
 summary: Popular easy to use Ruby client for RabbitMQ