An in-range update of browserify is breaking the build 🚨
greenkeeper opened this issue · comments
The dependency browserify was updated from 16.3.0 to 16.4.0.
This version is covered by your current version range and after updating it in your project the build failed.
browserify 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 could not complete due to an error (Details).
Commits
The new version differs by 5 commits.
898067016.4.0f871a85Update changelog.markdown52de2c4Merge pull request #1916 from browserify/stream-http5dc1bf2Upgrade stream-http to v34a5ea7eAdd funding.yml
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 🌴
After pinning to 16.3.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.
- The
dependencybrowserify was updated from16.4.0to16.5.0.
Your tests are still failing with this version. Compare changes
- The
dependencybrowserify was updated from16.5.0to16.5.1.
Your tests are still failing with this version. Compare changes
Release Notes for v16.5.1
Remove deprecated mkdirp version in favour of mkdirp-classic.
Pin dependencies for Node.js 0.8 support.
Commits
The new version differs by 8 commits.
da0f1e116.5.1dc71ea0Use non-deprecated mkdirp package.c53f841gitignore - add node_modules2b50632Update package.json249f54bUpdate package.json985dad9deps - pin deps for node v0.8 support86c3a00fixes swapped changelog PR references in 10.2.0a245fe6Add security.md
See the full diff