An in-range update of has-symbols is breaking the build 🚨

[greenkeeper]

The dependency has-symbols was updated from 1.0.0 to 1.0.1.

🚨 View failing branch.

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

has-symbols is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

• ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

---

Commits

The new version differs by 12 commits.

• 132fe9c v1.0.1
• 1dd42cd [Dev Deps] update eslint, @ljharb/eslint-config, safe-publish-latest, core-js, get-own-property-symbols, tape
• b09cdb7 [actions] add automatic rebasing / merge commit blocking
• 2163d0b [meta] add auto-changelog
• a0b32cf [meta] add funding field
• ce396c9 [Tests] use shared travis-ci configs
• aa57a17 [meta] create FUNDING.yml
• 0690732 [Tests] up to node v12.4, v11.15, v10.15, v9.11, v8.15, v7.10, v6.17, v4.9; use nvm install-latest-npm
• a2d8bea Only apps should have lockfiles
• 8e0951f [Dev Deps] update eslint, @ljharb/eslint-config, core-js, safe-publish-latest, tape
• 9e96cb7 [Tests] use npx aud instead of nsp or npm audit with hoops
• cb9f0a5 [Dev Deps] update safe-publish-latest

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.0.0 your tests are passing again. Downgrade this dependency 📌.