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

[greenkeeper]

Version 1.7.2 of yeoman-test was just published.

Branch	Build failing 🚨
Dependency	yeoman-test
Current Version	1.7.1
Type	devDependency

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

yeoman-test 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

---

Commits

The new version differs by 2 commits.

• 0c191c3 1.7.2
• ee3ca75 Fix #42 - broken yeoman-generator interface

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

[greenkeeper]

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

[greenkeeper]

Version 1.8.0 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Release Notes

v1.8.0

Add capacity to define namespace and resolved path to stubbed generators.

Commits

The new version differs by 2 commits.

• 9ed76d7 1.8.0
• 2609a69 Namespace and resolved path settings (#44)

See the full diff

[greenkeeper]

Version 1.9.0 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Release Notes

v1.9.0

• Fix tests silencing failure happening inside the generator under test own code.

This fix could break some users tests - but these tests should've been failing as the generator itself would be throwing an exception.

Commits

The new version differs by 3 commits.

• d4c9ef9 1.9.0
• 5cf9090 Update build process (bye gulp) and bump dependencies
• 06f2d6d Catch errors from yeoman-generator (#47)

See the full diff