An in-range update of @feathersjs/feathers is breaking the build 🚨

[greenkeeper]

The devDependency @feathersjs/feathers was updated from 3.2.3 to 3.3.0.

🚨 View failing branch.

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

@feathersjs/feathers 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/travis-ci/push: The Travis CI build could not complete due to an error (Details).

---

Commits

The new version differs by 29 commits.

• 3bbba49 Publish
• 17b3dc8 feat: Common database adapter utilities and test suite (#1130)
• c73d322 feat: Allow registering a service at the root level (#1115)
• c9f4b42 fix(package): update config to version 3.0.0 (#1100)
• afa1cb4 fix: Added path and method in to express request for passport (#1112)
• 9f1200f chore: Only run Saucelabs tests once in CI (#1122)
• 57e7140 chore(package): Update superagent in group default to the latest version 🚀 (#1095)
• 0feb20d Verify that the error handler works on nested routes (#1096) (#1106)
• d568627 chore(test): Update assertion format to always use strict equality (#1105)
• fd3fc34 fix(chore): Properly configure and run code linter (#1092)
• e894ac8 fix(chore): Remove CLI and generators that belong in their own repositories (#1091)
• 0a2ce87 fix: make codeclimate conform to rule of three (#1076)
• 1c74a14 Publish
• 9da26ad fix: support a secretProvider (#1063)
• 55de15e Publish

There are 29 commits in total.

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 3.2.3 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.