-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Test with Rails 5.2 #1146
Test with Rails 5.2 #1146
Conversation
This will reduce churn on this file as we try to keep up to date with TEENY Ruby releases. Travis installs Ruby via rvm with the --fuzzy flag. They also keep up to date with the latest releases, so --fuzzy will likely always give us the latest TEENY release.
9c6ab4f
to
171b30f
Compare
171b30f
to
c26ea27
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah! One syntax nitpick.
gem "sqlite3", "~> 1.3.10", :platforms => :ruby | ||
gem "activerecord", "~> 5.2.0" | ||
|
||
gemspec :name => "factory_bot", :path => "../" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reasonable to ask for Ruby 1.9 hash syntax here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Appraisal generates this file. I opened an issue there: thoughtbot/appraisal#140
While specifying only the minor ruby version is valid syntax on Travis, it does not in practice return the latest ruby patch version. For example, |
That's too bad. I guess I was mistaken about Travis having the latest patches pre-installed. I would rather not update |
I agree this is a bummer, it has been a problem for years, & I don't know of a solution. I found these related Travis issues, but they are unresolved: |
.travis.yml