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

[greenkeeper]

The dependency safe-buffer was updated from 5.1.2 to 5.2.0.

🚨 View failing branch.

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

safe-buffer 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 5 commits.

• ae53d5b 5.2.0
• a43206b Merge pull request #23 from vkarpov15/patch-1
• 4463582 add FUNDING.yml
• 9be9ce7 add tidelift link
• 4a4f75d Make SafeBuffer's prototype inherit from Buffer

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

[greenkeeper]

• The dependency safe-buffer was updated from 5.2.0 to 5.2.1.

Your tests are passing again with this update. Explicitly upgrade to this version 🚀

Commits

The new version differs by 10 commits.

• 89d3d5b package metadata
• e4d9032 5.2.1
• 1f19817 Merge pull request #28 from feross/greenkeeper/tape-5.0.0
• 09eb337 chore(package): update tape to version 5.0.0
• 7d54474 Update README.md
• 94d0401 standard *
• 4c90fcc Merge pull request #27 from feross/greenkeeper/standard-14.0.1
• ac31863 chore(package): update standard to version 14.0.1
• 2e8e6b4 Pin standard to workaround npm bug
• da591f1 Update FUNDING.yml

See the full diff