An in-range update of @feathersjs/errors is breaking the build π¨
Closed this issue Β· 1 comments
The devDependency @feathersjs/errors was updated from 4.3.4
to 4.3.7
.
π¨ View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
@feathersjs/errors 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 failed (Details).
Commits
The new version differs by 16 commits.
be129c7
v4.3.7
1a624ef
chore: Update all dependencies (#1618)
38cf8c9
fix: Typings for express request and response properties (#1609)
baad6a2
fix: improve Service and AdapterService types (#1567)
d7f5107
fix: Improve authentication client default storage initialization (#1613)
1c6c374
fix: make __hooks writable and configurable (#1520)
6a56056
chore: Update version and changelog
f67294b
v4.3.6
f1a781f
fix: Check query for NaN (#1607)
4bbc0d7
chore: Update version and changelog
1738fa4
v4.3.5
d6fdb6b
chore: Update Changelog commit message to conventional commit
19854d3
fix: Authentication type improvements and timeout fix (#1605)
4e4d10a
fix: Change this reference in client libraries to explicitly passed app (#1597)
317a312
fix: Improve error message when authentication strategy is not allowed (#1600)
There are 16 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 π΄
After pinning to 4.3.4 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.