An in-range update of yeoman-test is breaking the build 🚨

## Version **1.7.0** of [yeoman-test](https://github.com/yeoman/yeoman-test) just got published.

Branch


Build failing 🚨




Dependency


yeoman-test




Current Version


1.6.0




Type


devDependency

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

As yeoman-test 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/donejs/donejs-nw/builds/251669069?utm_source=github_status&utm_medium=notification)

---

Release Notes
v1.7.0

• Update to yeoman-generator 1.x


• Update to yeoman-environment 2.x

Commits

The new version differs by 3 commits.

• 3c83d8f 1.7.0


• 71ca3b3 Bump dependencies


• ccbf848 Update dependencies to enable Greenkeeper 🌴 (#28)

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](https://greenkeeper.io) Bot :palm_tree:

Start with the linked Travis CI failure and compare the greenkeeper/yeoman-test-1.7.0 branch against the current project state. Determine why yeoman-test 1.7.0 breaks the build, then verify that the project build and tests pass with the dependency handled appropriately.

Written by the indexing model from the issue text.