adds explanation about getting stuck on Version 3.1.1.0
@bokmann — I would recommend you yank 3.1.1.0 to fix this problem.
if you strongly want to support Rails 3.1 with changes in that gem release, you can make a 3.1.1.0b, with fixed gemspec that has upward bounds.
the reason it's a problem is that everytime someone creates a new Rails app (using rails new) bundler picks 3.1.1.0 because it thinks it is compatible with every Rails version, so this pitfall will happen on all new Rails apps.
my explanation is a stop-gap and can be removed if/when you yank the un-bounded gem version from Rubygems.
adds explanation about getting stuck on Version 3.1.1.0
@bokmann — I would recommend you yank 3.1.1.0 to fix this problem.
if you strongly want to support Rails 3.1 with changes in that gem release, you can make a 3.1.1.0b, with fixed gemspec that has upward bounds.
the reason it's a problem is that everytime someone creates a new Rails app (using
rails new) bundler picks 3.1.1.0 because it thinks it is compatible with every Rails version, so this pitfall will happen on all new Rails apps.my explanation is a stop-gap and can be removed if/when you yank the un-bounded gem version from Rubygems.