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

Upgrade Smart Answers to Ruby 2.2.4 #2199

Merged
merged 1 commit into from
Feb 4, 2016
Merged

Upgrade Smart Answers to Ruby 2.2.4 #2199

merged 1 commit into from
Feb 4, 2016

Conversation

erkde
Copy link
Contributor

@erkde erkde commented Dec 17, 2015

This PR bumps the version for Ruby from 2.2.3 to 2.2.4, which fixes CVE-2015-7551 of Ruby's Fiddle and DL modules, neither which Smart Answer uses directly.

Stage

https://warm-shelf-8029.herokuapp.com/am-i-getting-minimum-wage

@erkde
Copy link
Contributor Author

erkde commented Dec 17, 2015

Looks like CI isn't setup with 2.2.4 yet

@erkde erkde force-pushed the upgrade_to_ruby_2_2_4 branch from bf072bf to cfa7be0 Compare February 3, 2016 10:07
@floehopper
Copy link
Contributor

It looks as if Ruby 2.2.4 was added to ci-puppet in alphagov/ci-puppet#375 which has been merged. I'm going to try kicking the CI build for this PR and see whether it now passes.

@floehopper
Copy link
Contributor

The CI build has now passed, so I assume that Ruby 2.2.4 is now available on production.

I've reviewed the changes and they look good to me. The branch is up-to-date with master and ready for merging.

@floehopper floehopper self-assigned this Feb 4, 2016
@erkde
Copy link
Contributor Author

erkde commented Feb 4, 2016

Ok, let's give this a try

erkde pushed a commit that referenced this pull request Feb 4, 2016
Upgrade Smart Answers to Ruby 2.2.4
@erkde erkde merged commit c607db9 into master Feb 4, 2016
@erkde erkde deleted the upgrade_to_ruby_2_2_4 branch February 4, 2016 16:35
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