-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rails 3.0.x #3
Comments
I guess not super intentional. I can make it more liberal. ~> 3.0 would work, but ~> 3.0.0 wouldn't work with 3.1, I believe. On Friday, September 23, 2011 at 3:33 PM, Mike Auclair wrote:
|
What about '>= 3.0.0', '< 3.2.0' to prevent it from working with a hypothetical 3.2.0 without verification? |
That should work. Feel free to try it out and send pull. If not I'll look into it eventually. On Friday, September 23, 2011 at 7:30 PM, Mike Auclair wrote:
|
Was the removal of Rails 3.0.x support intentional with bin 0.7.0? All appears to work when the active_support dependency in the gemspec is rolled back to ~> 3.0.0
The text was updated successfully, but these errors were encountered: