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

Updating ruby version and gem versions #383

Merged

Conversation

tmobaird
Copy link
Contributor

@tmobaird tmobaird commented Apr 6, 2017

References #382.

@justin808 here's the PR for updating the ruby version and gem versions. I chose to split the dependency updates up into two different PRs (one for each Ruby and JS) to help minimize any problems that are encountered.

The important stuff: I updated the ruby version to 2.4.1 and updated the gem versions.

The app is running just fine for me locally, and all the specs are passing as well. It should build just fine on travis, as long as ruby 2.4.1 is available on Travis's rvm (I believe it should be).

Feel free to let me know if there are any other changes you want me to make.


This change is Reviewable

@tmobaird
Copy link
Contributor Author

tmobaird commented Apr 6, 2017

Looks like the build failed because of the style checks from Rubocop. It appears the upgraded ruby version/rubocop version triggered new style check offenses. @justin808 thoughts?

@justin808
Copy link
Member

Please try to address the rubocop issues.

rubocop -a FTW --> autofix

@tmobaird tmobaird force-pushed the maintenance/upgrade_dependency_versions branch from 2022e16 to 838bdac Compare April 7, 2017 06:01
@tmobaird
Copy link
Contributor Author

tmobaird commented Apr 7, 2017

@justin808 this should be good to go now. Besides updating the ruby version and gems, I had to update some of the source files, as well as the rubocop config, to fix new rubocop warnings that occurred after the version update.

Let me know if there's anything else you'd like me to change!

@justin808 justin808 merged commit 87188be into shakacode:master Apr 7, 2017
@justin808
Copy link
Member

Let's update the npm libraries now! Thanks @tmobaird!

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

Successfully merging this pull request may close these issues.

2 participants