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

[greenkeeper[bot]]

The devDependency safe-publish-latest was updated from 1.1.2 to 1.1.3.

🚨 View failing branch.

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

safe-publish-latest 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](https://travis-ci.org/ljharb/es-abstract/builds/571100112?utm_source=github_status&utm_medium=notification)).

---

Commits

The new version differs by 12 commits.

• 811dc22 v1.1.3
• b1c8cdf [Tests] use npx aud instead of nsp or npm audit with hoops
• 4fcd571 [Tests] up to node v12.8, v11.15, v10.16, v6.17
• ef3a572 [Dev Deps] update eslint, @ljharb/eslint-config, tape
• 67df923 [Tests] use eclint instead of editorconfig-tools
• a264743 [Deps] update semver
• b457194 [Fix] peg hosted-git-info to ~2.7 due to breaking change in 2.8
• a065e65 [meta] create FUNDING.yml
• a982ba6 [Tests] use npm audit instead of nsp
• 93a7e97 [Deps] update semver
• 8765efb [Tests] up to node v11.7, v10.15, v8.15, v6.16
• 06982ab [Dev Deps] update eslint, @ljharb/eslint-config, tape

See the full diff

FAQ and help

There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).

---

Your Greenkeeper Bot :palm_tree:

[greenkeeper[bot]]

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

[ljharb]

Fluke.