Update Gems #712
Merged
Update Gems #712
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
During this, I updated the Gems again
That is correct, we do not use this. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## dev #712 +/- ##
======================================
Coverage ? 54.30%
======================================
Files ? 170
Lines ? 7348
Branches ? 0
======================================
Hits ? 3990
Misses ? 3358
Partials ? 0 ☔ View full report in Codecov by Sentry. |
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.
As usual, update Ruby Gems. Since I pinned all versions in #680, I don't expect any breaking changes here (we only do a minor update with this PR).
Warning
Warning: Mobility v1.3.x includes potentially backwards-incompatible changes
for jsonb/hstore backends.
We don't use this backend, right? At least a search for
hstoreorjsonbdoesn't reveal anything in the MaMpf codebase.