remoting 0.2.16 → 0.3.2

data/README.md

@@ -120,7 +120,7 @@ end
 
 A complete deployment manager (like Capistrano even if probably not as good as it is) can be easily built over *remoting*. Capistrano recipes can be ordinary rake tasks packed as gems. Plus various _deployment strategies_ can be assembled as dependencies of a main `deploy` task.
 
-As from version `0.3.0` **Remoting** added support for recipes with a generator (`rails g remoting:recipe`) that basically installs recipes from [remoting/recipes](https://github.com/mcasimir/remoting/tree/master/recipes) into `lib/tasks/remote`.
+As from version `0.3.2` **Remoting** added support for recipes with a generator (`rails g remoting:recipe`) that basically installs recipes from [remoting/recipes](https://github.com/mcasimir/remoting/tree/master/recipes) into `lib/tasks/remote`.
 
 eg.
 

data/VERSION

@@ -1 +1 @@
-0.2.16
+0.3.2

data/remoting.gemspec

@@ -5,7 +5,7 @@
 
 Gem::Specification.new do |s|
   s.name = "remoting"
-  s.version = "0.2.16"
+  s.version = "0.3.2"
 
   s.required_rubygems_version = Gem::Requirement.new(">= 0") if s.respond_to? :required_rubygems_version=
   s.authors = ["mcasimir"]

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: remoting
 version: !ruby/object:Gem::Version
-  version: 0.2.16
+  version: 0.3.2
   prerelease: 
 platform: ruby
 authors:
@@ -114,7 +114,7 @@ required_ruby_version: !ruby/object:Gem::Requirement
       version: '0'
       segments:
       - 0
-      hash: 2814619444637718291
+      hash: -4021652142999167177
 required_rubygems_version: !ruby/object:Gem::Requirement
   none: false
   requirements: