Skip to content
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

Issue #4941 , handle error 'Please specify the Rails release the migr… #4942

Merged
merged 1 commit into from
Oct 3, 2018

Conversation

oystersauce8
Copy link
Contributor

Issue #4941 , handle error 'Please specify the Rails release the migration was written for'

def rails5?
Rails.version.start_with? '5'
def rails5_and_up?
Rails::VERSION::MAJOR >= 5
Copy link
Collaborator

Choose a reason for hiding this comment

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

This constant is private. Maybe Rails.gem_version >= Gem::Version('5.0.0')?

Copy link
Collaborator

@rafaelfranca rafaelfranca Sep 25, 2018

Choose a reason for hiding this comment

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

Ah, it is public, so this is fine.

@rafaelfranca
Copy link
Collaborator

Can you also test devise with Rails 6. Right now it is not tested so I don't want to recommend people to use it.

@oystersauce8
Copy link
Contributor Author

My new app worked ok I guess, basic tests passed and running on heroku at https://untitled-d68f47d.herokuapp.com/

The only caveat was the responders gem still didn't "recognize" rails 6 - I sent a PR

@tegon tegon merged commit 94adec3 into heartcombo:master Oct 3, 2018
@jcoyne
Copy link
Contributor

jcoyne commented Jan 19, 2019

This is great. Any chance we'll see it in a release soon?

@tegon
Copy link
Member

tegon commented Jan 21, 2019

@jcoyne Yep, there are still some issues to solve with Rails 6, so when we manage to do it a new version is going to be released.

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

Successfully merging this pull request may close these issues.

4 participants