Rails 3.1 and Rails 3.2 support #36

merged 1 commit into from Apr 22, 2012


None yet
libc commented Feb 9, 2012

I guess the subject is self-explanatory.

I added RAILS_VERSION environment variable to the db-charmer-sandbox, which allows to run specs for multiple rails versions:

 for i in 3.0.11 3.1.3 3.2.1 3-0-stable 3-1-stable 3-2-stable; do rm Gemfile.lock; RAILS_VERSION=$i bundle; RAILS_VERSION=$i rake; done

They all could be added to travis similar to the rspec-rails: https://github.com/rspec/rspec-rails/blob/master/.travis.yml

The master branch of rails is not support at the moment though.

mperham commented Feb 15, 2012

@kovyrin Will you have time to look at the Rails 3.2 issues anytime soon?

shaliko commented Mar 19, 2012






Bucho commented Mar 23, 2012




ai commented Mar 26, 2012




kovyrin commented Mar 28, 2012

Ok guys, I will try to look into this issue on weekend and maybe merge those commits into the master.

shellac commented Apr 4, 2012

+1 To fixing this. Working in well for me in rails 3.2.1

@libc libc Merge pull request #1 from caueguerra/master
bumping rails dependency to 3.2.3
@kovyrin kovyrin merged commit e508a4d into kovyrin:master Apr 22, 2012
kovyrin commented Apr 22, 2012

Great thanks to Eugene Pimenov (aka @libc) with his pull request, we've released new DbCharmer version 1.7.1 with Rails 3.1 and 3.2 support. Still waiting for TravisCI to clear the build, but it works locally so the gem is pushed to Rubygems already.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment