An in-range update of safe-buffer is breaking the build 🚨
greenkeeper opened this issue · comments
Version 5.1.0 of safe-buffer just got published.
Branch | Build failing 🚨 |
---|---|
Dependency | safe-buffer |
Current Version | 5.0.1 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As safe-buffer 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 💪
Status Details
Commits
The new version differs by 10 commits.
9d841b6
5.1.0
458d362
package-lock.json
ba6ab91
ignore buffer constructor usage
52f9b74
use Buffer from required buffer package
9ed934b
Merge pull request #12 from calvinmetcalf/no-browser
01898ef
fix tests
94c8316
remove browser version
6ed8017
standard
99be471
Update README.md
7159794
standard
See the full diff
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
This was bumped