identifies_as 1.0.8 → 1.0.9

data/CHANGELOG.rdoc

@@ -14,3 +14,7 @@ Fix for Module (now Module includes IdentifiesAs::ClassInstance).
 == 6/13/2012
 
 Fix for ClassInstance - now defined directly in Module since it seems Module methods are defined in the class not in a module interface, which means we can't insert methods before and call super.
+
+== 7/04/2012
+
+Removed module-cluster dependency, which was already irrelevant.

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: identifies_as
 version: !ruby/object:Gem::Version
-  version: 1.0.8
+  version: 1.0.9
   prerelease: 
 platform: ruby
 authors:
@@ -9,24 +9,8 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2012-06-26 00:00:00.000000000 Z
-dependencies:
-- !ruby/object:Gem::Dependency
-  name: module-cluster
-  requirement: !ruby/object:Gem::Requirement
-    none: false
-    requirements:
-    - - ! '>='
-      - !ruby/object:Gem::Version
-        version: '0'
-  type: :runtime
-  prerelease: false
-  version_requirements: !ruby/object:Gem::Requirement
-    none: false
-    requirements:
-    - - ! '>='
-      - !ruby/object:Gem::Version
-        version: '0'
+date: 2012-07-05 00:00:00.000000000 Z
+dependencies: []
 description: Identities are interfaces. Sometimes it makes more sense to test an identity
   than a method- but then you don't want to limit flexibility. So why not let objects
   that claim to implement your interface identify as your object? IdentifiesAs permits