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

[greenkeeper]

Version 1.2.0 of defaultenv just got published.

Branch	Build failing 🚨
Dependency	defaultenv
Current Version	1.1.0
Type	devDependency

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

As defaultenv 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

• ❌ coverage/coveralls First build on greenkeeper/defaultenv-1.2.0 at 84.456% Details
• ✅ continuous-integration/travis-ci/push The Travis CI build passed Details

---

Release Notes

v1.2.0

<a name"1.2.0">

1.2.0 (2017-06-28)

Features

• defaultenv: tolerate non-existent files, like an optional gitignored .env (aed60c3c)

Commits

The new version differs by 2 commits.

• aed60c3 feat(defaultenv): tolerate non-existent files, like an optional gitignored .env
• aa3ca1e fix(lib/index.js): fix typo

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]

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