rails_exception_handler 2.0.0 → 2.0.1

data/.travis.yml

@@ -1,9 +1,12 @@
+
 before_script:
-  - "spec/dummy_30/script/setup"
+  - ./spec/dummy_32/script/setup
 
 notifications:
   disable: true
 
+language: ruby
+
 rvm:
   - 1.9.3
   - 1.9.2

data/Gemfile

@@ -1,15 +1,14 @@
-# A sample Gemfile
 source "http://rubygems.org"
 
 group :test, :development do
 
-  gem "rails", '3.0.12'
-    gem "rack-test", '0.5.7'
-    gem "mysql2", '0.2.6'
+  #gem "rails", '3.0.12'
+    #gem "rack-test", '0.5.7'
+    #gem "mysql2", '0.2.6'
 
-  #gem "rails", '3.2.2'
-    #gem "rack-test", '0.6.1'
-    #gem 'mysql2', '0.3.11'
+  gem "rails", '3.2.3'
+    gem "rack-test", '0.6.1'
+    gem 'mysql2', '0.3.11'
 
   gem 'pry'
   gem "rspec-rails"

data/Gemfile.lock

@@ -1,84 +1,88 @@
 PATH
   remote: .
   specs:
-    rails_exception_handler (1.4.0)
+    rails_exception_handler (2.0.0)
 
 GEM
   remote: http://rubygems.org/
   specs:
-    abstract (1.0.0)
-    actionmailer (3.0.12)
-      actionpack (= 3.0.12)
-      mail (~> 2.2.19)
-    actionpack (3.0.12)
-      activemodel (= 3.0.12)
-      activesupport (= 3.0.12)
-      builder (~> 2.1.2)
-      erubis (~> 2.6.6)
-      i18n (~> 0.5.0)
-      rack (~> 1.2.5)
-      rack-mount (~> 0.6.14)
-      rack-test (~> 0.5.7)
-      tzinfo (~> 0.3.23)
-    activemodel (3.0.12)
-      activesupport (= 3.0.12)
-      builder (~> 2.1.2)
-      i18n (~> 0.5.0)
-    activerecord (3.0.12)
-      activemodel (= 3.0.12)
-      activesupport (= 3.0.12)
-      arel (~> 2.0.10)
-      tzinfo (~> 0.3.23)
-    activeresource (3.0.12)
-      activemodel (= 3.0.12)
-      activesupport (= 3.0.12)
-    activesupport (3.0.12)
-    arel (2.0.10)
-    builder (2.1.2)
+    actionmailer (3.2.3)
+      actionpack (= 3.2.3)
+      mail (~> 2.4.4)
+    actionpack (3.2.3)
+      activemodel (= 3.2.3)
+      activesupport (= 3.2.3)
+      builder (~> 3.0.0)
+      erubis (~> 2.7.0)
+      journey (~> 1.0.1)
+      rack (~> 1.4.0)
+      rack-cache (~> 1.2)
+      rack-test (~> 0.6.1)
+      sprockets (~> 2.1.2)
+    activemodel (3.2.3)
+      activesupport (= 3.2.3)
+      builder (~> 3.0.0)
+    activerecord (3.2.3)
+      activemodel (= 3.2.3)
+      activesupport (= 3.2.3)
+      arel (~> 3.0.2)
+      tzinfo (~> 0.3.29)
+    activeresource (3.2.3)
+      activemodel (= 3.2.3)
+      activesupport (= 3.2.3)
+    activesupport (3.2.3)
+      i18n (~> 0.6)
+      multi_json (~> 1.0)
+    arel (3.0.2)
+    builder (3.0.0)
     coderay (1.0.6)
     diff-lcs (1.1.3)
-    erubis (2.6.6)
-      abstract (>= 1.0.0)
+    erubis (2.7.0)
     git (1.2.5)
-    i18n (0.5.0)
+    hike (1.2.1)
+    i18n (0.6.0)
     jeweler (1.8.3)
       bundler (~> 1.0)
       git (>= 1.2.5)
       rake
       rdoc
+    journey (1.0.3)
     json (1.7.3)
-    mail (2.2.19)
-      activesupport (>= 2.3.6)
+    mail (2.4.4)
       i18n (>= 0.4.0)
       mime-types (~> 1.16)
       treetop (~> 1.4.8)
     method_source (0.7.1)
     mime-types (1.18)
-    mysql2 (0.2.6)
+    multi_json (1.3.5)
+    mysql2 (0.3.11)
     polyglot (0.3.3)
     pry (0.9.9.6)
       coderay (~> 1.0.5)
       method_source (~> 0.7.1)
       slop (>= 2.4.4, < 3)
-    rack (1.2.5)
-    rack-mount (0.6.14)
-      rack (>= 1.0.0)
-    rack-test (0.5.7)
+    rack (1.4.1)
+    rack-cache (1.2)
+      rack (>= 0.4)
+    rack-ssl (1.3.2)
+      rack
+    rack-test (0.6.1)
       rack (>= 1.0)
-    rails (3.0.12)
-      actionmailer (= 3.0.12)
-      actionpack (= 3.0.12)
-      activerecord (= 3.0.12)
-      activeresource (= 3.0.12)
-      activesupport (= 3.0.12)
+    rails (3.2.3)
+      actionmailer (= 3.2.3)
+      actionpack (= 3.2.3)
+      activerecord (= 3.2.3)
+      activeresource (= 3.2.3)
+      activesupport (= 3.2.3)
       bundler (~> 1.0)
-      railties (= 3.0.12)
-    railties (3.0.12)
-      actionpack (= 3.0.12)
-      activesupport (= 3.0.12)
+      railties (= 3.2.3)
+    railties (3.2.3)
+      actionpack (= 3.2.3)
+      activesupport (= 3.2.3)
+      rack-ssl (~> 1.3.2)
       rake (>= 0.8.7)
       rdoc (~> 3.4)
-      thor (~> 0.14.4)
+      thor (~> 0.14.6)
     rake (0.9.2.2)
     rdoc (3.12)
       json (~> 1.4)
@@ -96,7 +100,12 @@ GEM
       railties (>= 3.0)
       rspec (~> 2.10.0)
     slop (2.4.4)
+    sprockets (2.1.3)
+      hike (~> 1.2)
+      rack (~> 1.0)
+      tilt (~> 1.1, != 1.3.0)
     thor (0.14.6)
+    tilt (1.3.3)
     treetop (1.4.10)
       polyglot
       polyglot (>= 0.3.1)
@@ -107,9 +116,9 @@ PLATFORMS
 
 DEPENDENCIES
   jeweler
-  mysql2 (= 0.2.6)
+  mysql2 (= 0.3.11)
   pry
-  rack-test (= 0.5.7)
-  rails (= 3.0.12)
+  rack-test (= 0.6.1)
+  rails (= 3.2.3)
   rails_exception_handler!
   rspec-rails

data/HISTORY

@@ -1,5 +1,12 @@
 CHANGELOG
 
+v2.0.1 - May 2u7th 2012
+ - Fix ruby187 issue and a typo in the generator
+
+v2.0.0 - May 15th 2012
+ - New API for specifying what information to store about the request, exception and environment
+ - Added a generator that creates an initializer
+
 v1.4.0 - March 10th 2012
  - Rails 3.2.2 fixes
  - Added after_initialize callback

data/README.markdown

@@ -2,7 +2,9 @@
 
 Upgrading from version 1? [See wiki](https://github.com/Sharagoz/rails_exception_handler/wiki/Version-2.0-upgrade-instructions)
 
-This is a flexible exception handler for Rails 3 built as Rack middleware. It enables you to save the key information from the error message in a database somewhere and display a customized error message to the user within the applications layout file. You can hook this gem into all your rails apps and gather the exception reports in one place. This gem just contains the back end, you will have to create your own front end to view and manage the error reports.
+This is a flexible exception handler for Rails 3 built as Rack middleware. It is aimed at experienced Rails developers who are administrating more than just a couple of rails applications. Dont be intimidated if you're new to rails though, it's not that hard to set up.
+
+The exception handler enables you to save the key information from the error message in a database somewhere and display a customized error message to the user within the applications layout file. You can hook this exception handler into all your rails apps and gather the exception reports in one place. The exception handler just contains the back end, you will have to create your own front end to view and manage the error reports.
 
 Does your app have an authorization mechanism? [See wiki](https://github.com/Sharagoz/rails_exception_handler/wiki/Interaction-with-authorization-mechanisms)
 
@@ -11,6 +13,7 @@ Do you need to catch ruby errors outside of Rack? [See wiki](https://github.com/
 ## Compatiblity
 
 The gem should work with all versions of Rails 3. It does not work with Rails 2.
+
 See Travis-CI for info on which rubies it is tested against:
 http://travis-ci.org/#!/Sharagoz/rails_exception_handler
 
@@ -21,10 +24,15 @@ Add the line below to your gemfile and run bundler
 gem 'rails_exception_handler', "~> 2"
 ```
 
-Now run "rails g rails_exception_handler:install" to create an initializer in config/initializers/rails_exception_handler.rb
+Generate an initializer:
+
+```
+"rails g rails_exception_handler:install
+```
 
+Open config/initializers/rails_exception_handler.rb, have a quick look and read on.
 
-## Configuration options
+## Configuring the basics
 
 ### environments
 An array of symbols that says which Rails environments you want the exception handler to run in.
@@ -35,16 +43,6 @@ config.environments = [:production, :test, :development]
 
 Default value: [:production]
 
-### storage_strategies
-An array of zero or more symbols that says which storage strategies you want to use. Each are explained in detail in separate sections at the end of this document.
-
-```ruby
-config.storage_strategies = [:active_record, :rails_log, :remote_url => {:target => 'http://example.com'}]
-```
-
-Default value: []
-
-
 ### fallback_layout
 
 ```ruby
@@ -55,23 +53,15 @@ Default value: 'application'
 
 The exception handler will always use the layout file of the controller action that was accessed when the error occured. However, when routing errors occures there are no controller action to get this layout from, so it falls back to the default 'application' layout that most apps have. If your application does not have a layout file called 'application', then you need to override this, otherwise a "missing layout" exception will occur.
 
-### store_user_info
-
-Having some way of identifying the user can be very useful at times, so I always store information on who generated the exception in applications that have a log in feature.
-To enable this you need to specify the name of the controller method that provides the user object and the name of the field which contains the info you want to save.
-
-```ruby
-config.store_user_info = {:method => :current_user, :field => :login}
-```
+### after_initialize
 
-Default value: false (no info will be stored)
-If you turn this on and the error is generated by a client that is not logged in, then "Anonymous" will be used.
+This is a callback that exists in case you need to do something right after the initializer has been run, for instance [interact with an authorization mechanism](https://github.com/Sharagoz/rails_exception_handler/wiki/Interaction-with-authorization-mechanisms)
 
 ### responses and response_mapping
 
 Note: public/500.html and public/400.html will be used if these exists. Remove these files before applying the configuration below.
 
-Create a set of responses and then map specific exceptions to these responses. There needs to be a response called :default which is used for the exceptions that are not explicity mapped to a response.
+Create a set of responses and then map specific exceptions to these responses. There needs to be a response called :default which is used for the exceptions that are not explicitly mapped to a response.
 
 ```ruby
 config.responses = {
@@ -89,60 +79,9 @@ config.response_mapping = {
 }
 ```
 
-### after_initialize
-
-This callback exists in case you need to do something right after the initializer has been run, for instance [interact with an authorization mechanism](https://github.com/Sharagoz/rails_exception_handler/wiki/Interaction-with-authorization-mechanisms)
+# Gathering exception information
 
-### filters
-
-All filters are disabled by default. I recommend you deploy your application this way, and then add filters as they become necessary.
-The only reason I've ever wanted filtering have been due to what seem like poorly programmed web crawlers and black bots probing for security holes. If legitimate web crawlers are a problem for you, look into tweaking your robots.txt file before enabling exception filters.
-
-**:all_404s**
-
-```ruby
-config.filters = [:all_404s]
-```
-
-When turned on the following exceptions will no longer be stored: ActionController::RoutingError, AbstractController::ActionNotFound, ActiveRecord::RecordNotFound
-Consider this a last resort. You will miss all "real" 404s when this is turned on, like broken redirections.
-
-**:anon_404s**
-
-```ruby
-config.filters = [:anon_404s]
-```
-
-When turned on the following exceptions will no longer be stored unless a user is logged in: ActionController::RoutingError, AbstractController::ActionNotFound, ActiveRecord::RecordNotFound
-
-**:no_referer_404s**
-
-```ruby
-config.filters = [:no_referer_404s]
-```
-
-ActionController::RoutingError, AbstractController::ActionNotFound, ActiveRecord::RecordNotFound will be ignored if it was caused by a request without a referer.
-This is very effective against bots. 99.9% of the time a routing error with no referer will be caused by a bot, and then once in a while it will be caused by a real user that happened to generate an error on the first page he opened (like a broken bookmark). You will get a lot less false positives with this filter than :all_404s.
-
-**:user_agent_regxp**
-
-Legit software will usually add something to the user agent string to let you know who they are. You can use this to filter out the errors they generate, and be pretty sure you are not going to get any false positives.
-
-```ruby
-config.filters = [:user_agent_regxp => /\b(ZyBorg|Yandex|Jyxobot)\b/i]
-```
-
-If you (like me) dont know regular expressions by heart, then http://www.rubular.com/ is great tool to use when creating a regxp.
-
-**:target_url_regxp**
-
-Sometimes black bots add a common user agent string and a referer to their requests to cloak themselfs, which makes it hard to filter them without filtering all routing errors. What you can often do is to filter on what they target, which is usually security holes in some well known library/plugin (usually in php). The example below will filter out all URLs containing ".php". This is the filter I most commonly use myself. Without it, it is only a matter of time before I'll one day get 200 exceptions in 10mins caused by a bot looking for security holes in myPhpAdmin or some other PHP plugin.
-
-```ruby
-config.filters = [:target_url_regxp => /\.php/i]
-```
-
-## Gathering exception information
+Gathering and storing exception information is optional, but still the main purpose of this exception handler.
 
 The following for methods exists for extracting the information you need. You are given direct access to the relevant objects, which means full flexibility, but also more work on your part.
 The initializers contains a basic suggestion, you can check out [the wiki](https://github.com/Sharagoz/rails_exception_handler/wiki/Extracting-exception-info)
@@ -161,14 +100,31 @@ config.store_global_info do |storage|
 end
 ```
 
-## Storage strategy - active record
+### store_user_info
+
+Having some way of identifying the user can be very useful at times, so I always store information on who generated the exception in applications that have a log in feature.
+Since extracting current_user from the environment variable takes a little bit of work, this helper method exists to make it easier. The user info are stored in a field called "user_info".
+
+```ruby
+config.store_user_info = {:method => :current_user, :field => :login}
+```
+
+Default value: false (no info will be stored)
+If you turn this on and the error is generated by a client that is not logged in, then "Anonymous" will be used.
+
+# Storing the exception
+
+No storage strategies are enabled by default. You can enable more than one storage strategy.
+
+### Through active_record
+
 ```ruby
 config.storage_strategies = [:active_record]
 ```
-This means that the error reports will be stored through active record directly to a database, which is pretty much the whole reason why I created this library in the first place. A new entry called **exception_database** is needed in **database.yml**:
+This means that the error reports will be stored through active record directly to a database. A new entry called **exception_database** is needed in **database.yml**:
+For mysql the entry would look something like this:
 
 ```
-# for mysql the entry would look something like this:
 exception_database:
   adapter: mysql2
   encoding: utf8
@@ -180,7 +136,7 @@ exception_database:
   host: 127.0.0.1
 ```
 
-You could of course store the error messages in the same database as the application uses, but one of the main purposes of this library is to enable you to easily store error reports from many applications in the same database, so I recommend you set up a separate dedicated database for this.
+You could of course store the error messages in the same database as the application uses, but one of the main purposes of this exception handler is to enable you to easily store error reports from many applications in the same database, so I recommend you set up a separate dedicated database for this.
 
 The exception database needs a table called **error_messages**. Here's a migration script that you can use to create the table with the necessary fields required for the default configuration:
 
@@ -209,7 +165,7 @@ class CreateErrorMessages < ActiveRecord::Migration
 end
 ```
 
-## Storage strategy - rails log
+### Saving to the rails log
 
 ```ruby
 config.storage_strategies = [:rails_log]
@@ -231,22 +187,73 @@ activesupport (3.0.7) lib/active_support/notifications.rb:54:in `instrument'
 (the rest of the stack trace has been omitted from the example)
 ```
 
-## Storage strategy - remote url
+### Sending the error report as an HTTP POST request to another application
+
 ```ruby
 config.storage_strategies = [:remote_url => {:target => 'http://example.com/error_messages'}]
 ```
+
 This option is meant for those who want to store the exception in a database table, but does not have direct access to the database itself, making active record store unsuitable. You need a web app on a server that has access to the database. An HTTP POST request will be sent to the specified URL with the error message as data.
 If you use a Rails app at the other end you should simply be able to do _ErrorMessage.create(params[:error_message])_ to save the report.
 
-## Contributors
+# Exception filters
+
+Sometimes it is necessary to filter errors. All filters are disabled by default and I recommend you deploy your application this way initially, and then add filters as they become necessary.
+The only reason I've ever wanted filtering have been due to what seem like poorly programmed web crawlers and black bots probing for security holes. If legitimate web crawlers are a problem for you, look into tweaking your robots.txt file before enabling exception filters.
+
+### :all_404s
+
+```ruby
+config.filters = [:all_404s]
+```
+
+When turned on the following exceptions will no longer be stored: ActionController::RoutingError, AbstractController::ActionNotFound, ActiveRecord::RecordNotFound
+Consider this a last resort. You will miss all "real" 404s when this is turned on, like broken redirections.
+
+### :anon_404s
+
+```ruby
+config.filters = [:anon_404s]
+```
+
+When turned on the following exceptions will no longer be stored unless a user is logged in: ActionController::RoutingError, AbstractController::ActionNotFound, ActiveRecord::RecordNotFound
+
+### :no_referer_404s
+
+```ruby
+config.filters = [:no_referer_404s]
+```
+
+ActionController::RoutingError, AbstractController::ActionNotFound, ActiveRecord::RecordNotFound will be ignored if it was caused by a request without a referer.
+This is very effective against bots. 99.9% of the time a routing error with no referer will be caused by a bot, and then once in a while it will be caused by a real user that happened to generate an error on the first page he opened (like a broken bookmark). You will get a lot less false positives with this filter than :all_404s.
+
+### :user_agent_regxp
+
+Legit software will usually add something to the user agent string to let you know who they are. You can use this to filter out the errors they generate, and be pretty sure you are not going to get any false positives.
+
+```ruby
+config.filters = [:user_agent_regxp => /\b(ZyBorg|Yandex|Jyxobot)\b/i]
+```
+
+If you (like me) dont know regular expressions by heart, then http://www.rubular.com/ is great tool to use when creating a regxp.
+
+### :target_url_regxp
+
+Sometimes black bots add a common user agent string and a referer to their requests to cloak themselfs, which makes it hard to filter them without filtering all routing errors. What you can often do is to filter on what they target, which is usually security holes in some widely used library/plugin. The example below will filter out all URLs containing ".php". This is the filter I most commonly use myself. Without it, it is only a matter of time before I'll one day get 200 exceptions in 10mins caused by a bot looking for security holes in myPhpAdmin or some other PHP library.
+
+```ruby
+config.filters = [:target_url_regxp => /\.php/i]
+```
+
+# Contributors
 
-David Rice
+David Rice and James Harrison
 
 Would you like to contribute? Here are some things on the todo list:
 
 * A mongoid storage strategy for those that wish to use MongoDB
 * An email storage strategy for those that wish to be notified of the exceptions through email
 
-## Licence
+# Licence
 
-Copyright © 2011 Bjørn Trondsen, released under the MIT license
+Copyright © 2012 Bjørn Trondsen, released under the MIT license

data/VERSION

@@ -1 +1 @@
-2.0.0
+2.0.1

data/lib/generators/rails_exception_handler/templates/rails_exception_handler.rb

@@ -32,7 +32,7 @@ RailsExceptionHandler.configure do |config|
     storage[:user_agent] =    request.user_agent
   end
 
-  config.store_exception_info do |storage,exeception|
+  config.store_exception_info do |storage,exception|
     storage[:class_name] =   exception.class.to_s
     storage[:message] =      exception.to_s
     storage[:trace] =        exception.backtrace.join("\n")

data/lib/rails_exception_handler/storage.rb

@@ -6,7 +6,7 @@ class RailsExceptionHandler::Storage
   def self.rails_log(info)
     message = ""
     info.each do |key,val|
-      message += "#{key.upcase}: #{val.to_s}\n"
+      message += "#{key.to_s.upcase}: #{val.to_s}\n"
     end
     Rails.logger.fatal(message)
   end

data/rails_exception_handler.gemspec

@@ -5,11 +5,11 @@
 
 Gem::Specification.new do |s|
   s.name = "rails_exception_handler"
-  s.version = "2.0.0"
+  s.version = "2.0.1"
 
   s.required_rubygems_version = Gem::Requirement.new(">= 0") if s.respond_to? :required_rubygems_version=
   s.authors = ["Sharagoz"]
-  s.date = "2012-05-14"
+  s.date = "2012-05-27"
   s.description = ""
   s.email = "contact@sharagoz.com"
   s.extra_rdoc_files = [
@@ -59,26 +59,26 @@ Gem::Specification.new do |s|
     s.specification_version = 3
 
     if Gem::Version.new(Gem::VERSION) >= Gem::Version.new('1.2.0') then
-      s.add_development_dependency(%q<rails>, ["= 3.0.12"])
-      s.add_development_dependency(%q<rack-test>, ["= 0.5.7"])
-      s.add_development_dependency(%q<mysql2>, ["= 0.2.6"])
+      s.add_development_dependency(%q<rails>, ["= 3.2.3"])
+      s.add_development_dependency(%q<rack-test>, ["= 0.6.1"])
+      s.add_development_dependency(%q<mysql2>, ["= 0.3.11"])
       s.add_development_dependency(%q<pry>, [">= 0"])
       s.add_development_dependency(%q<rspec-rails>, [">= 0"])
       s.add_development_dependency(%q<jeweler>, [">= 0"])
       s.add_development_dependency(%q<rails_exception_handler>, [">= 0"])
     else
-      s.add_dependency(%q<rails>, ["= 3.0.12"])
-      s.add_dependency(%q<rack-test>, ["= 0.5.7"])
-      s.add_dependency(%q<mysql2>, ["= 0.2.6"])
+      s.add_dependency(%q<rails>, ["= 3.2.3"])
+      s.add_dependency(%q<rack-test>, ["= 0.6.1"])
+      s.add_dependency(%q<mysql2>, ["= 0.3.11"])
       s.add_dependency(%q<pry>, [">= 0"])
       s.add_dependency(%q<rspec-rails>, [">= 0"])
       s.add_dependency(%q<jeweler>, [">= 0"])
       s.add_dependency(%q<rails_exception_handler>, [">= 0"])
     end
   else
-    s.add_dependency(%q<rails>, ["= 3.0.12"])
-    s.add_dependency(%q<rack-test>, ["= 0.5.7"])
-    s.add_dependency(%q<mysql2>, ["= 0.2.6"])
+    s.add_dependency(%q<rails>, ["= 3.2.3"])
+    s.add_dependency(%q<rack-test>, ["= 0.6.1"])
+    s.add_dependency(%q<mysql2>, ["= 0.3.11"])
     s.add_dependency(%q<pry>, [">= 0"])
     s.add_dependency(%q<rspec-rails>, [">= 0"])
     s.add_dependency(%q<jeweler>, [">= 0"])

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: rails_exception_handler
 version: !ruby/object:Gem::Version
-  version: 2.0.0
+  version: 2.0.1
   prerelease: 
 platform: ruby
 authors:
@@ -9,7 +9,7 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2012-05-14 00:00:00.000000000 Z
+date: 2012-05-27 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rails
@@ -18,7 +18,7 @@ dependencies:
     requirements:
     - - '='
       - !ruby/object:Gem::Version
-        version: 3.0.12
+        version: 3.2.3
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
@@ -26,7 +26,7 @@ dependencies:
     requirements:
     - - '='
       - !ruby/object:Gem::Version
-        version: 3.0.12
+        version: 3.2.3
 - !ruby/object:Gem::Dependency
   name: rack-test
   requirement: !ruby/object:Gem::Requirement
@@ -34,7 +34,7 @@ dependencies:
     requirements:
     - - '='
       - !ruby/object:Gem::Version
-        version: 0.5.7
+        version: 0.6.1
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
@@ -42,7 +42,7 @@ dependencies:
     requirements:
     - - '='
       - !ruby/object:Gem::Version
-        version: 0.5.7
+        version: 0.6.1
 - !ruby/object:Gem::Dependency
   name: mysql2
   requirement: !ruby/object:Gem::Requirement
@@ -50,7 +50,7 @@ dependencies:
     requirements:
     - - '='
       - !ruby/object:Gem::Version
-        version: 0.2.6
+        version: 0.3.11
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
@@ -58,7 +58,7 @@ dependencies:
     requirements:
     - - '='
       - !ruby/object:Gem::Version
-        version: 0.2.6
+        version: 0.3.11
 - !ruby/object:Gem::Dependency
   name: pry
   requirement: !ruby/object:Gem::Requirement