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

[greenkeeper]

---

☝️ Important announcement: Greenkeeper will be saying goodbye 👋 and passing the torch to Snyk on June 3rd, 2020! Find out how to migrate to Snyk and more at greenkeeper.io

---

The devDependency in-publish was updated from 2.0.0 to 2.0.1.

🚨 View failing branch.

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

in-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

• ❌ 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.

• 4f6a055 Use process.env.npm_command if present (#14)
• 8e70b63 Update README.md
• 981ad77 Adds a link to the readme to background info (#5)
• 94054a4 2.0.1
• 982607d Merge pull request #3 from lewiscowper/patch-1
• 2cd6be3 :pencil2: Typo fix

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