Skip to content

Commit fbc004d

Browse files
authored
Include 8.0 in the Upgrading section (#103)
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.
1 parent 87ca1bd commit fbc004d

File tree

1 file changed

+19
-1
lines changed

1 file changed

+19
-1
lines changed

Diff for: content/guides/3-upgrading.md

+19-1
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,26 @@
11
---
2-
title: Upgrading to 7.0
2+
title: Upgrading
33
slug: /guides/upgrading
44
---
55

6+
# Upgrading to 8.0
7+
8+
node-postgres at 8.0 introduces a breaking change to ssl-verified connetions. If you connect with ssl and use
9+
10+
```
11+
const client = new Client({ ssl: true })
12+
```
13+
14+
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
15+
16+
```
17+
const client = new Client({ ssl: { rejectUnauthorized: false } })
18+
```
19+
20+
The rest of the changes are relatively minor and unlikely to cause issues; see [the announcement](/announcements#2020-02-25) for full details.
21+
22+
# Upgrading to 7.0
23+
624
node-postgres at 7.0 introduces somewhat significant breaking changes to the public API.
725

826
## node version support

0 commit comments

Comments
 (0)