An in-range update of ok-file is breaking the build 🚨

[greenkeeper]

Version 1.1.0 of ok-file was just published.

Branch	Build failing 🚨
Dependency	ok-file
Current Version	1.0.3
Type	devDependency

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

ok-file 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

• ✅ ci/circleci Your tests passed on CircleCI! Details
• ❌ continuous-integration/appveyor/branch AppVeyor build cancelled Details

---

Release Notes

v1.1.0

1.1.0 (2017-10-16)

Bug Fixes

• bin: bin path (effb1c2)

Features

• debug: add debug with DEBUG=ok-file variable (a479a44)

Commits

The new version differs by 2 commits.

• effb1c2 fix(bin): bin path
• a479a44 feat(debug): add debug with DEBUG=ok-file variable

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]

Version 1.3.0 just got published.

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

Release Notes

v1.3.0

1.3.0 (2017-10-16)

Features

• multiple: handle multiple files (1e31f57)

Commits

The new version differs by 3 commits.

• 1e31f57 feat(multiple): handle multiple files
• 8dd4acd add example bin commands to .travis.yml
• bf0d667 feat(wildcard): support wildcard

See the full diff