An in-range update of power-assert is breaking the build 🚨

[greenkeeper]

Version 1.6.1 of power-assert was just published.

Branch	Build failing 🚨
Dependency	power-assert
Current Version	1.6.0
Type	devDependency

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

power-assert 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

• ❌ continuous-integration/appveyor/branch: Waiting for AppVeyor build to complete (Details).
• ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

---

Commits

The new version differs by 8 commits.

• e549955 1.6.1
• 63043bc docs: add CHANGELOG for 1.6.1
• 389e525 chore(travis): drop Node9 from CI
• 8bd962e chore: update package-lock.json
• 04ff9fd chore: update empower to ^1.3.1
• 76af2b7 chore: avoid concatenating undefined
• 170892e chore: fix failing tests due to the change in assertion message since Node v10.7.0
• 9455634 test: Object Rest/Spread in assertion expression

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

[greenkeeper]

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