An in-range update of trooba is breaking the build 🚨

[greenkeeper]

Version 2.1.0 of trooba just got published.

Branch	Build failing 🚨
Dependency	trooba
Current Version	2.0.2
Type	devDependency

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

As trooba is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

---

Commits

The new version differs by 19 commits.

• ea63936 2.1.0
• b35ccb1 Merge pull request #16 from trooba/greenkeeper/initial
• f6ca97c docs(readme): add Greenkeeper badge
• 4443ad3 Support for nested pipes/handlers retuned by a pipe point (#15)
• 54399c3 added a link to trooba web site
• 6411842 updated npmingnore
• 2d54fec Merge pull request #14 from dimichgh/master
• 96f293a added documentation
• d7c5a1d Merge pull request #13 from trooba/dimichgh-readme-1
• c87717b Update .travis.yml
• 92b60d7 Update README.md
• d422232 removing node 0.10
• e82c88b Update .travis.yml
• e0ecac2 Merge pull request #12 from patrick-steele-idem/patch-1
• 3c7318b Improved code formatting

There are 19 commits in total.

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

[greenkeeper]

After pinning to 2.0.2 your tests are passing again. Downgrade this dependency 📌.

[greenkeeper]

Version 2.1.1 just got published.

Your tests are passing again with this version. Explicitly upgrade to this version 🚀

[greenkeeper]

Version 2.1.2 just got published.

Your tests are passing again with this version. Explicitly upgrade to this version 🚀

Commits

The new version differs by 5 commits.

• fdfd1e0 2.1.2
• db39dc8 Fix: Should keep the order in stream response when pipe.throw is activated (#18)
• 9341e7c 2.1.1
• bd849f4 clean up & fixes (#17)
• 5ab4041 changelog update

See the full diff