Repository navigation
An in-range update of @feathersjs/express is breaking the build 🚨 #178
Description
The devDependency @feathersjs/express was updated from 1.2.7 to 1.3.0.
This version is covered by your current version range and after updating it in your project the build failed.
@feathersjs/express 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.
3bbba49Publish17b3dc8feat: Common database adapter utilities and test suite (#1130)c73d322feat: Allow registering a service at the root level (#1115)c9f4b42fix(package): update config to version 3.0.0 (#1100)afa1cb4fix: Added path and method in to express request for passport (#1112)9f1200fchore: Only run Saucelabs tests once in CI (#1122)57e7140chore(package): Update superagent in group default to the latest version 🚀 (#1095)0feb20dVerify that the error handler works on nested routes (#1096) (#1106)d568627chore(test): Update assertion format to always use strict equality (#1105)fd3fc34fix(chore): Properly configure and run code linter (#1092)e894ac8fix(chore): Remove CLI and generators that belong in their own repositories (#1091)0a2ce87fix: make codeclimate conform to rule of three (#1076)1c74a14Publish9da26adfix: support a secretProvider (#1063)55de15ePublish
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 🌴
Activity
greenkeeper commentedon Dec 16, 2018
After pinning to 1.2.7 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.