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

[greenkeeper[bot]]

The devDependency gofur was updated from 1.1.0 to 1.1.1.

🚨 View failing branch.

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

gofur 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

- ❌ **ci/circleci:** Your tests failed on CircleCI ([Details](https://circleci.com/gh/redgeoff/squadron/90?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link)).

---

Commits

The new version differs by 13 commits.

• cbfd5cb chore(version): 1.1.1
• 4237151 Merge pull request #45 from redgeoff/update-packages
• 079ac71 chore(packages): update
• 6e3184d Merge pull request #44 from redgeoff/redgeoff-patch-1
• 5025bce test(circleci): latest node
• 36e4e3c Merge pull request #43 from redgeoff/greenkeeper/fs-extra-7.0.0
• 0dffe09 fix(package): update fs-extra to version 7.0.0
• 5635bba feat(packages): update mocha-headless-chrome and selenium-standalone (#42)
• 5d5e680 Merge pull request #41 from redgeoff/chrome
• 421be5f test(headless): now need to install chrome
• 103379b Merge pull request #38 from redgeoff/greenkeeper/fs-extra-6.0.0
• caf001b fix(package): update fs-extra to version 6.0.0
• 5b9ca73 fix(browser-coverage): restore grep (#36)

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

[redgeoff]

Fixed by https://github.com/redgeoff/squadron/pull/27