From de8ca34738a44be2ef0de134af135f04a407c5d4 Mon Sep 17 00:00:00 2001 From: "Dustin J. Mitchell" Date: Thu, 24 Sep 2020 18:37:11 +0000 Subject: [PATCH] Include 8.0 in the Upgrading section This is where I went looking for information about what broke in 8. @eschwartz pointed me to the Announcements, which do contain full details but were not a place I thought to look. This PR includes the most critical breaking change in the "Upgrading" section, with reference to the announcement for the details. --- content/guides/3-upgrading.md | 20 +++++++++++++++++++- 1 file changed, 19 insertions(+), 1 deletion(-) diff --git a/content/guides/3-upgrading.md b/content/guides/3-upgrading.md index 8d426c8..28e6d76 100644 --- a/content/guides/3-upgrading.md +++ b/content/guides/3-upgrading.md @@ -1,8 +1,26 @@ --- -title: Upgrading to 7.0 +title: Upgrading slug: /guides/upgrading --- +# Upgrading to 8.0 + +node-postgres at 8.0 introduces a breaking change to ssl-verified connetions. If you connect with ssl and use + +``` +const client = new Client({ ssl: true }) +``` + +and the server's SSL certificate is self-signed, connections will fail as of node-postgres 8.0. To keep the existing behavior, modify the invocation to + +``` +const client = new Client({ ssl: { rejectUnauthorized: false } }) +``` + +The rest of the changes are relatively minor and unlikely to cause issues; see [the announcement](/announcements#2020-02-25) for full details. + +# Upgrading to 7.0 + node-postgres at 7.0 introduces somewhat significant breaking changes to the public API. ## node version support