Update pg to version 4.5.6 🚀 #81
Closed
Conversation
This file contains hidden or 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
Contributor
|
a newer PR exists |
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.
Hello 👋
🚀🚀🚀
pg just published its new version 4.5.6, which is not covered by your current version range.
If this pull request passes your tests you can publish your software with the latest version of pg – otherwise use this branch to work on adaptions and fixes.
Happy fixing and merging 🌴
The new version differs by 4 commits .
6cc1b2cBump versiond7307b1use latest generic-pool (#1031)55abbaadon't mutate params when preparing statement (#992)5d3b506Change test matrix in .travis.yml (#1002)See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? Upgrade to the supporter plan! You'll also get your pull requests faster ⚡It keeps your software up to date, all the time.