An in-range update of ci-publish is breaking the build 🚨

[greenkeeper]

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

Version 1.3.1 of ci-publish was just published.

Branch	Build failing 🚨
Dependency	ci-publish
Current Version	1.3.0
Type	devDependency

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

ci-publish 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

• ❌ semaphoreci The build is pending on Semaphore. Details
• ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

---

Commits

The new version differs by 6 commits.

• 31680fe fix: version bump
• 02f2258 chore: use Node 8 on CI
• 716752d fix: newer version of dependency
• 311f36c Use fresh available-versions
• 4b3e13c added link to next-ver
• 2f0e24c chore(log): how to turn on verbose npm logging

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