protect_via_honeypots 0.1.1 → 0.1.2

data/Rakefile

@@ -10,7 +10,7 @@ begin
 protect_via_honeypots creates some hidden fields. As normal users don't mess with hidden fields we can assume that when those fields are filled with data: a bot filled it.
 So when that happens, protect_via_honeypots throws an error (as the same way protect_from_forgery does)}
     gem.email = "roy@royapps.nl"
-    gem.homepage = "http://github.com/roy/hello-gem"
+    gem.homepage = "http://github.com/roy/protect_via_honeypots"
     gem.authors = ["Roy van der Meij"]
     gem.add_development_dependency "thoughtbot-shoulda", ">= 0"
     # gem is a Gem::Specification... see http://www.rubygems.org/read/chapter/20 for additional settings

data/VERSION

@@ -1 +1 @@
-0.1.1
+0.1.2

data/protect_via_honeypots.gemspec

@@ -5,7 +5,7 @@
 
 Gem::Specification.new do |s|
   s.name = %q{protect_via_honeypots}
-  s.version = "0.1.1"
+  s.version = "0.1.2"
 
   s.required_rubygems_version = Gem::Requirement.new(">= 0") if s.respond_to? :required_rubygems_version=
   s.authors = ["Roy van der Meij"]
@@ -32,7 +32,7 @@ So when that happens, protect_via_honeypots throws an error (as the same way pro
      "protect_via_honeypots.gemspec",
      "test/helper.rb"
   ]
-  s.homepage = %q{http://github.com/roy/hello-gem}
+  s.homepage = %q{http://github.com/roy/protect_via_honeypots}
   s.rdoc_options = ["--charset=UTF-8"]
   s.require_paths = ["lib"]
   s.rubygems_version = %q{1.3.7}

metadata

@@ -1,13 +1,13 @@
 --- !ruby/object:Gem::Specification 
 name: protect_via_honeypots
 version: !ruby/object:Gem::Version 
-  hash: 25
+  hash: 31
   prerelease: false
   segments: 
   - 0
   - 1
-  - 1
-  version: 0.1.1
+  - 2
+  version: 0.1.2
 platform: ruby
 authors: 
 - Roy van der Meij
@@ -58,7 +58,7 @@ files:
 - protect_via_honeypots.gemspec
 - test/helper.rb
 has_rdoc: true
-homepage: http://github.com/roy/hello-gem
+homepage: http://github.com/roy/protect_via_honeypots
 licenses: []
 
 post_install_message: