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

Version 14.4.0 of browserify just got published.

Branch	Build failing 🚨
Dependency	browserify
Current Version	14.3.0
Type	devDependency

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

As browserify is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this :muscle:

Status Details

- ❌ **continuous-integration/travis-ci/push** The Travis CI build could not complete due to an error [Details](https://travis-ci.org/ljharb/object.assign/builds/236813900?utm_source=github_status&utm_medium=notification)

Commits

The new version differs by 11 commits.

21af338 14.4.0
4fc4b3c changelog: remove trailing whitespace
94a5c03 changelog
f6feab7 Merge pull request #1714 from mcollina/patch-1
89809c3 Merge pull request #1722 from blahah/patch-1
80df2ec Document ignoreMissing option for browserify() (closes #1595)
107d9bb Updated string_decoder to v1.0.0
91ed9c8 Merge pull request #1713 from substack/feross-patch-1
d247a52 Use SVG Travis badge
d461420 Merge pull request #1712 from substack/feross/tests
de4147c test: fix tests on node 0.10 that require ArrayBuffer

See the full diff

Not sure how things should work exactly?

There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).

Your Greenkeeper Bot :palm_tree:

ljharb / object.assign

An in-range update of browserify is breaking the build 🚨 #44

Version 14.4.0 of browserify just got published.