An in-range update of pg is breaking the build 🚨

[greenkeeper[bot]]

The devDependency pg was updated from 7.11.0 to 7.12.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

pg is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

- ❌ **ci/circleci: build:** Your tests failed on CircleCI ([Details](https://circleci.com/gh/cdaringe/pg-subscribe/197?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link)).

---

Commits

The new version differs by 9 commits.

• e4578d2 Bump version
• d44376a Update sponsors file
• 94ad322 Update changelog
• 3ead900 Fix eslint and add back standard (#1928)
• 0894a3c feat: Add dynamic retrieval for client password (#1926)
• 0acaf9d Fix compare (#1923)
• d8a0e1e Update CI to allow tests to pass on Node.js >= 10.16.0 (#1912)
• 2c7be86 minor text improvement in defaults (#1893)
• 8ba1d2c Enable eslint:recommended and plugin/node/recommended (#1856)

See the full diff

FAQ and help

There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).

---

Your Greenkeeper Bot :palm_tree:

[greenkeeper[bot]]

After pinning to 7.11.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.

[greenkeeper[bot]]

• The devDependency pg was updated from 7.12.0 to 7.12.1.

Your tests are still failing with this version. Compare changes

Commits

The new version differs by 2 commits.

• 60d8df6 Bump version
• 05d20a6 Update package.json (#1937)

See the full diff