-
-
Notifications
You must be signed in to change notification settings - Fork 4
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
Update pg to the latest version 🚀 #323
Conversation
Codecov Report
@@ Coverage Diff @@
## master #323 +/- ##
=======================================
Coverage 74.88% 74.88%
=======================================
Files 73 73
Lines 1342 1342
Branches 76 76
=======================================
Hits 1005 1005
Misses 336 336
Partials 1 1 Continue to review full report at Codecov.
|
Version 7.0.1 just got published. |
Sequelize + pg 7.0.1 のIssueが上がってきてるので、現状気軽にマージできない状態。 はやくPostgresのテストができるようにしておきたい。(#294) |
Version 7.0.2 just got published. |
Version 7.1.1 just got published. |
Version 7.1.2 just got published. |
Version 7.2.0 just got published.Update to this version instead 🚀 CommitsThe new version differs by 11 commits.
See the full diff |
Version 7.3.0 just got published.Update to this version instead 🚀 CommitsThe new version differs by 25 commits.
There are 25 commits in total. See the full diff |
Version 7.4.0 just got published.Update to this version instead 🚀 CommitsThe new version differs by 8 commits.
See the full diff |
Version 7.4.1 just got published.Update to this version instead 🚀 CommitsThe new version differs by 10 commits.
See the full diff |
Version 7.4.2 just got published.Update to this version instead 🚀 CommitsThe new version differs by 19 commits.
There are 19 commits in total. See the full diff |
Update to this version instead 🚀 CommitsThe new version differs by 16 commits.
There are 16 commits in total. See the full diff |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Version 7.0.0 of pg just got published.
The version 7.0.0 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.
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 64 commits.
cbbd8d4
Bump version
8a1da11
Update changelog
8cc7308
Merge pull request #1369 from brianc/7.0
ca4ac99
Re-implement other patch
f9390da
Re-implement changes from conflict
8bfdd39
Merge remote-tracking branch 'origin/master' into 7.0
f37acc4
Use valid semver in package.json
111e08d
Cleanup
ac3102e
Add support for pg-native multi-row result
28b330c
Add JS driver support for multiple results
8798e50
Re-enable eslint with standard format (#1367)
f7de9ce
Non-array query values cause query to end with an error.
27450d0
Throw on reconnect attempt
a83655a
Remove console.log statement
da71ea5
Add query validity check
There are 64 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 🌴