-
Notifications
You must be signed in to change notification settings - Fork 49
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
Update rubocop #250
Update rubocop #250
Conversation
Reason: CVE-2017-8418 Low severity
One rspec test fails, but it fails on master too for me.
|
PR checker fails on
|
@askreet Can we get your review on this please and a new release :) |
@askreet Reviews please ;) |
Now travis is happy, but I would consider removing ruby 2.1 from the supported list instead. https://www.ruby-lang.org/en/news/2017/04/01/support-of-ruby-2-1-has-ended/ There is no reason to keep 2.1 on this list. Such a good tool like Moonshot and would be a shame to drop off from projects because it can't follow ruby. If I start a new project with CLoudFormation, most likely I'll pick Moonshot because it's easy to use and so powerful. If Moonshot wants to stick with 2.1 (and any so old and not officially supported versions) just because we are afraid of cutting a version that will not working with older versions then I think Moonshot will start be a risk factor and will get a huge "consider the usage" on new projects which would be painful for everyone. |
* Update rubocop from 0.38.x to 0.49.x Reason: CVE-2017-8418 Low severity * make rubocop happy again * try to fix travis * revert travisfile changes, originall at least 2.2 worked * pin bundler in travisfile? * drop ruby 2.1
* Update rubocop from 0.38.x to 0.49.x Reason: CVE-2017-8418 Low severity * make rubocop happy again * try to fix travis * revert travisfile changes, originall at least 2.2 worked * pin bundler in travisfile? * drop ruby 2.1
Reason: CVE-2017-8418 Low severity