update gems to most recent version

[RaimundSchramm]

• bcrypt-ruby (3.1.5 > 3.1.2)
• capistrano (3.1.0 > 2.15.5)
• capybara (2.2.1 > 1.1.4) Gemfile specifies "~> 1.1.0"
• childprocess (0.5.1 > 0.4.2)
• debugger (1.6.6 > 1.6.5)
• factory_girl_rails (4.4.1 > 4.4.0)
• guard-rspec (4.2.7 > 4.2.6)
• poltergeist (1.5.0 > 1.0.3)
• sqlite3 (1.3.9 > 1.3.8)
• arel (5.0.0 > 4.0.2)
• builder (3.2.2 > 3.1.4)
• debugger-ruby_core_source (1.3.2 > 1.3.1)
• faye-websocket (0.7.2 > 0.4.7)
• guard (2.5.1 > 2.4.0)
• highline (1.6.21 > 1.6.20)
• http_parser.rb (0.6.0 > 0.5.3)
• listen (2.6.2 > 2.5.0)
• mime-types (2.1 > 1.25.1)
• minitest (5.3.0 > 4.7.5)
• rspec-core (2.14.8 > 2.14.7)
• rspec-mocks (2.14.6 > 2.14.5)
• selenium-webdriver (2.40.0 > 2.39.0)
• tilt (2.0.0 > 1.4.1)
• timers (2.0.0 > 1.1.0)
• tzinfo (1.1.0 > 0.3.38)
• websocket (1.1.2 > 1.0.7)
• xpath (2.0.0 > 0.1.4)

[RaimundSchramm]

except capistrano every other gem seems to be a dependency of some dependency

wait until dependency is updated

[RaimundSchramm]

recent gem outdated

global gemset:

• bigdecimal (1.2.4 < 1.2.7)
• bundler (1.7.6 < 1.11.2)
• io-console (0.4.2 < 0.4.5)
• psych (2.0.5 < 2.0.17)
• test-unit (2.1.5.0 < 3.1.8)

bundle sub-dependencies:

• arel (6.0.3 < 7.0.0) # used by activerecord
• hike (1.2.3 < 2.1.3) # used by sprockets
• mini_portile2 (2.0.0 < 2.1.0) # used by nokogiri
• slop (3.6.0 < 4.3.0) # used by pry
• factory_girl (4.5.0 < 4.7.0) # used by factory_girl_rails

bundle dependencies:

• capistrano (2.15.7 < 3.4.0)

recent bundler outdated

Outdated gems included in the bundle:

• capistrano (3.4.0 > 2.15.7) Gemfile specifies "= 2.15.7"
• arel (7.0.0 > 6.0.3)
• factory_girl (4.7.0 > 4.5.0)
• mini_portile2 (2.1.0 > 2.0.0)
• slop (4.3.0 > 3.6.0)

[RaimundSchramm]

open questions:

• how to handle global gemset
• how to handle sub-dependencies (I assume the 'correct' way is to wait until parent-dependency is upgraded.)