An in-range update of browserstack-runner is breaking the build 🚨

[greenkeeper[bot]]

The devDependency browserstack-runner was updated from 0.9.0 to 0.9.1.

🚨 View failing branch.

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

browserstack-runner 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](https://travis-ci.org/Tradeshift/io/builds/643756908?utm_source=github_status&utm_medium=notification)).

---

Release Notes for 0.9.1 - minor refactoring

#190

Commits

The new version differs by 9 commits.

• 1df5c7e Merge pull request #220 from yashLadha/chore/version-bump
• a11592b Version bumped up
• fb33f8e Merge pull request #190 from cwisecarver/bugfix/fix-matcher-logic
• 52b23f0 Merge pull request #210 from browserstack/issue_template
• 41986ac adding version info to issue template
• 307e064 Adding issue template
• d853d30 Merge pull request #208 from browserstack/version_bump
• c584dd5 Force patched responseData to a string
• cb34207 Use conditional tag matching logic everywhere

See the full diff

FAQ and help

There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).

---

Your Greenkeeper Bot :palm_tree:

[greenkeeper[bot]]

After pinning to 0.9.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.

[wejendorp]

Closing and crediting to build instability.