An in-range update of @asset-pipe/sink-mem is breaking the build 🚨

[greenkeeper]

The dependency @asset-pipe/sink-mem was updated from 1.1.2 to 1.1.3.

🚨 View failing branch.

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

@asset-pipe/sink-mem is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

• ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

---

Release Notes for v1.1.3

1.1.3 (2018-12-20)

Bug Fixes

• update deps to fix vulnerabilities (20c27d2)

Commits

The new version differs by 10 commits.

• 20c27d2 fix: update deps to fix vulnerabilities
• e550514 chore(package): update eslint to version 5.0.1 (#63)
• 08f232d chore(package): update travis-deploy-once to version 5.0.1 (#62)
• c4e4f87 chore(package): update semantic-release to version 15.1.4
• 9855e66 chore(package): update lint-staged to version 7.0.0
• fa4c36b chore: update semantic release usage
• b70fe9f chore: update lock file post greenkeeper
• 692067d chore(package): update semantic-release to version 12.2.2
• 85d6d3a chore(package): remove tap
• ddb592b chore(package): update jest

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