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

[greenkeeper]

Version 0.11.1 of nodeunit just got published.

Branch	Build failing 🚨
Dependency	nodeunit
Current Version	0.11.0
Type	devDependency

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

As nodeunit 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 💪

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

---

Commits

The new version differs by 3 commits.

• 62388a3 0.11.1
• 81c097f Merge pull request #339 from aeisenberg/reference-error-fix
• ce9cfe8 Fixes junit reporter throws ReferenceError

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 🌴

[greenkeeper]

Version 0.11.2 just got published.

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

Release Notes

0.11.2

minor change to junit tests

Commits

The new version differs by 4 commits.

• 1cfd2a5 0.11.2
• 72e6563 Merge pull request #283 from hugosenari/junit-report-time
• 39f493d Add time attribute in Junit Reporter #275
• fc3a271 Add time attribute in Junit Reporter #275

See the full diff