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

[greenkeeper[bot]]

Version 3.1.0 of yeoman-assert just got published.

Branch	Build failing 🚨
Dependency	yeoman-assert
Current Version	3.0.0
Type	devDependency

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

As yeoman-assert 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
• ✅ coverage/coveralls First build on greenkeeper/yeoman-assert-3.1.0 at 97.861% Details

---

Release Notes

v3.1.0

• New assertion method assert.equalsFileContent() to asserts against exact file content.

Commits

The new version differs by 3 commits.

• ae8dc73 3.1.0
• 62f3533 Adding assert.equalsFileContent (#24)
• c45d328 ES2015ify and require Node.js 4

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot :palm_tree:

[greenkeeper[bot]]

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

[greenkeeper[bot]]

Version 3.1.1 just got published.

Your tests are passing again with this version. Explicitly upgrade to this version 🚀

Commits

The new version differs by 2 commits.

• 3f207c9 3.1.1
• 5b6549c Add license file

See the full diff