This repository has been archived by the owner on Jul 6, 2021. It is now read-only.
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.
This PR contains the following updates:
7.18.2
->8.6.0
Release Notes
brianc/node-postgres
v8.6.0
Compare Source
--isolatedModules
.v8.5.1
Compare Source
v8.5.0
Compare Source
v8.4.2
Compare Source
v8.4.1
Compare Source
v8.4.0
Compare Source
DatabaseError
from pg-protocol.sslmode
in the connection string.v8.3.3
Compare Source
v8.3.2
Compare Source
v8.3.0
Compare Source
{ options: string }
field on client/pool config.v8.2.2
Compare Source
v8.2.1
Compare Source
v8.2.0
Compare Source
v8.1.0
Compare Source
pg-connection-string
. This includes better support for SSL argument parsing from connection strings and ensures continuity of support.&ssl=no-verify
option to connection string andPGSSLMODE=no-verify
environment variable support for the pure JS driver. This is equivalent of passing{ ssl: { rejectUnauthorized: false } }
to the client/pool constructor. The advantage of having support in connection strings and environment variables is it can be "externally" configured via environment variables and CLI arguments much more easily, and should remove the need to directly edit any application code for the SSL default changes in 8.0. This should make using[email protected]
significantly less difficult on environments like Heroku for example.v8.0.3
Compare Source
v8.0.2
Compare Source
v8.0.1
Compare Source
v8.0.0
Compare Source
note: for detailed release notes please check here
6 lts
from the test matrix.pg>=8.0
may still work on older versions but it is no longer officially supported.rejectUnauthorized
with the SSL connection parameters. Previously we defaulted torejectUnauthorized: false
when it was not specifically included. We now default torejectUnauthorized: true.
Manually specify{ ssl: { rejectUnauthorized: false } }
for old behavior.user
config option if available. Previouslyprocess.env.USER
was used.pg.Pool
andpg.Query
to be an es6 class.pg.native
non enumerable.notice
messages are no longer instances ofError
.Configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻️ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by WhiteSource Renovate. View repository job log here.