Update pg-promise to the latest version 🚀 #3883
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
![greenkeeper[bot]](https://avatars.githubusercontent.com/in/505?s=60&v=4){kind=small}
Codecov Report
@@ Coverage Diff @@
## master #3883 +/- ##
=======================================
Coverage 90.27% 90.27%
=======================================
Files 114 114
Lines 7578 7578
=======================================
Hits 6841 6841
Misses 737 737Continue to review full report at Codecov.
|
koolamusic
pushed a commit
to koolamusic/parse-server
that referenced
this pull request
Jan 30, 2018
fix(package): update pg-promise to version 5.8.1 (parse-community#3883)
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.
Version 5.8.1 of pg-promise just got published.
The version 5.8.1 is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of pg-promise.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Commits
The new version differs by 28 commits.
1af6810improving coverage.fd387b2cleaning up tests.9d0b4cdrestoring pg dependency.259aaf1restoring the branch.7e1e2dbmerging7e058dcresetting changes.6392865updateb887705restoring the branch.c32a9bbMerge branch '6.x' into master6af656brefactoring for ES6 syntax.54f51d9fixing the test.144daadtrying to fix the test.062825btrying to fix the test.7811766diagnosing tests.72668f8fixing the test.There are 28 commits in total.
See the full diff
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴