Updated all gems to fix security issues #103
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
vkoves
force-pushed
the
update-insecure-gems
branch
from
a022b4f
to
a1cf102
Compare
Rails did this automatically upon running migrations
|
@AcademyInPeril - can you review this PR? A quick test should suffice |
SorenSpicknall
approved these changes
Aug 29, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of Changes:
Updated gems to fix security issues pointed out by GitHub. We should test this to make sure everything still works fine.
Here are the gems GitHub pointed out issues with:
Tests Added:
None.
Reference Related Issue(s) or Spec Requirement:
N/A
Checklist:
Questions / Additional Notes: