Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

An in-range update of webpack-stream is breaking the build 🚨 #26

Open
greenkeeper bot opened this issue Dec 2, 2018 · 2 comments
Open

An in-range update of webpack-stream is breaking the build 🚨 #26

greenkeeper bot opened this issue Dec 2, 2018 · 2 comments

Comments

@greenkeeper
Copy link
Contributor

greenkeeper bot commented Dec 2, 2018

The devDependency webpack-stream was updated from 5.1.1 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.

webpack-stream is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

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 9 commits.

  • 3215030 v5.2.0
  • a9d3880 Add Node 10 to travis
  • 249b38c Updating webpack, supports-color and fancy-log
  • dc02c56 Merge pull request #209 from ChrisGalliano/master
  • 912590b Merge pull request #210 from zbron99/master
  • b217f4a ➕ Added support for Webpack 4's quiet log options in order to properly check if suppressing any unwanted logs based on a Webpack 4 config is necessary
  • 2797873 watchOptions support
  • 49d2ed1 Merge pull request #205 from Chalarangelo/patch-1
  • e5004f5 Update index.js

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
Copy link
Contributor Author

greenkeeper bot commented Dec 2, 2018

After pinning to 5.1.1 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Dec 3, 2018

Your tests are still failing with this version. Compare changes

Commits

The new version differs by 2 commits.

  • fa9a5b2 v5.2.1
  • f29df3a Check if options.stats is a string before calling match. Fixes GH-211

See the full diff

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

0 participants