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

[greenkeeper[bot]]

Version 3.2.0 of testdouble just got published.

Branch	Build failing 🚨
Dependency	testdouble
Current Version	3.1.1
Type	devDependency

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

As testdouble 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 :muscle:

Status Details

- ❌ **continuous-integration/travis-ci/push** The Travis CI build failed [Details](https://travis-ci.org/blinkmobile/blob-uploader/builds/246546350?utm_source=github_status&utm_medium=notification)

---

Commits

The new version differs by 39 commits.

• 79cecd3 Changelog for 3.2.0
• 6797f84 3.2.0
• 2fce02b Test the primitive-checker
• 76093c1 Clear out needless indirection
• 9d7fb8d standard --fix
• 754fd79 Add a silly deeply nested example
• 92f1354 standard fix
• a353f1d Pushed down 4 things in overwrite children
• f3145e5 Test the thing that creates the root fakes
• 37ccdc8 Drive out a fresh impl of initialize-names
• c0e8b21 Pair with @andrewvida to refactor imitate()
• dc2a4d5 Start detangling imitiate as prefactoring
• 9aded7b Fix test for Node 4 (requires strict mode)
• 1b2c936 Use test/safe instead for call-through test
• fbb1fbf Move imitate fun

There are 39 commits in total.

See the full diff

Not sure how things should work exactly?

There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).

---

Your Greenkeeper Bot :palm_tree:

[greenkeeper[bot]]

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

[kizaonline]

Raised issue https://github.com/testdouble/testdouble.js/issues/270