An in-range update of greenkeeper-lockfile is breaking the build 🚨

[greenkeeper]

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 1.13.3 of greenkeeper-lockfile was just published.

Branch	Build failing 🚨
Dependency	greenkeeper-lockfile
Current Version	1.13.2
Type	devDependency

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

greenkeeper-lockfile 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

---

Release Notes

v1.13.3

1.13.3 (2018-02-28)

Bug Fixes

• Use build number from env on Jenkins (d2b51fb)

Commits

The new version differs by 3 commits.

• d2b51fb fix: Use build number from env on Jenkins
• 3af5bf9 chore(package): update lockfile
• 0371975 chore(package): update standard to version 11.0.0

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.13.2 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.

[greenkeeper]

Version 1.14.0 just got published.

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

Release Notes

v1.14.0

1.14.0 (2018-03-01)

Features

• add Semaphore as a service (1cdc187)

Commits

The new version differs by 1 commits.

• 1cdc187 feat: add Semaphore as a service

See the full diff