Skip to content

Commit

Permalink
Bumping ruby version to 2.1.5
Browse files Browse the repository at this point in the history
  • Loading branch information
oeoeaio authored and RohanM committed Nov 5, 2015
1 parent d731d4e commit b7d9278
Show file tree
Hide file tree
Showing 3 changed files with 4 additions and 4 deletions.
2 changes: 1 addition & 1 deletion .ruby-version
Original file line number Diff line number Diff line change
@@ -1 +1 @@
2.0.0-p481
2.1.5
2 changes: 1 addition & 1 deletion Gemfile
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
source 'https://rubygems.org'
ruby "2.0.0"
ruby "2.1.5"

gem 'rails', '3.2.21'
gem 'rails-i18n', '~> 3.0.0'
Expand Down
4 changes: 2 additions & 2 deletions Gemfile.lock
Original file line number Diff line number Diff line change
Expand Up @@ -251,7 +251,7 @@ GEM
eventmachine (>= 0.12.9)
http_parser.rb (~> 0.5.3)
erubis (2.7.0)
eventmachine (1.0.3)
eventmachine (1.0.8)
excon (0.25.3)
execjs (2.5.2)
factory_girl (3.3.0)
Expand Down Expand Up @@ -334,7 +334,7 @@ GEM
addressable (~> 2.3)
letter_opener (1.0.0)
launchy (>= 2.0.4)
libv8 (3.16.14.3)
libv8 (3.16.14.11)
listen (2.2.0)
celluloid (>= 0.15.2)
rb-fsevent (>= 0.9.3)
Expand Down

2 comments on commit b7d9278

@flov
Copy link
Contributor

@flov flov commented on b7d9278 Nov 11, 2015

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Any reason why you didn't upgrade to the latest ruby 2.2.3?

@oeoeaio
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@flov
Sorry just noticed this. Yes, the reason was because our version of Rails (3.2) was not supported by the latest Ruby at the time of upgrade. At this stage, we are stuck with Rails 3.2 because we have not upgraded Spree to version 2.1+, which is the point that Rails 4 becomes supported.

Please sign in to comment.