-
Notifications
You must be signed in to change notification settings - Fork 438
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
[src/api] Update database_consistency 1.7.11 → 1.7.12 (patch) #14615
[src/api] Update database_consistency 1.7.11 → 1.7.12 (patch) #14615
Conversation
Please see the links listed bellow to review the changes applied to the gems: |
1 similar comment
Please see the links listed bellow to review the changes applied to the gems: |
@depfu rebase |
4fedaef
to
c951df3
Compare
Please see the links listed bellow to review the changes applied to the gems: |
@depfu rebase |
c951df3
to
69b1c78
Compare
Please see the links listed bellow to review the changes applied to the gems: |
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## master #14615 +/- ##
==========================================
+ Coverage 87.17% 87.19% +0.02%
==========================================
Files 744 744
Lines 25016 25016
==========================================
+ Hits 21807 21813 +6
+ Misses 3209 3203 -6 |
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ database_consistency (1.7.11 → 1.7.12) · Repo · Changelog
Release Notes
1.7.12 (from changelog)
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 3 commits:
Release 1.7.12
Add support of disabling per database connection (#204)
Improve configurations message (#203)
Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase
.All Depfu comment commands